[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: calligra 2.5.0
From: Marek Laane <bald () smail ! ee>
Date: 2012-08-06 23:41:49
Message-ID: CAC0LJT-aP04khWB2rDudExbiqe2z7OaoZJqiFjmg6jgMCDD99g () mail ! gmail ! com
[Download RAW message or body]
2012/8/7 Freek de Kruijf <f.de.kruijf@gmail.com>
> Op maandag 6 augustus 2012 23:52:28 schreef Albert Astals Cid:
> > El Dilluns, 6 d'agost de 2012, a les 18:49:24, Freek de Kruijf va
> escriure:
> > > Op maandag 6 augustus 2012 20:52:13 schreef Albert Astals Cid:
> > > > > Hi,
> > > > >
> > > > > It is better to avoid using entities for extragear (it has
> different
> > > > > release cycle) [1].
> > > >
> > > > There's no need to avoid entities, just do not use entities
> introduced
> > > > in
> > > > a
> > > > kdelibs version bigger than the minimum kdelibs required by software
> X.
> > >
> > > Where does one find such information?
> >
> > Nowhere that i know. You ask the maintainer of the program, or you ask
> me,
> > or you don't use entities.
>
> Entities are very useful to enter the credentials of a translator /
> developer
> / documentor in just one place. So if something changes in these
> credentials
> one has to change it in just one place.
>
> I would recommend to have a rule that entities are only added to or
> changed in
> kdelibs, never removed, and are backported to previous living releases, and
> have a release cycle more or less like extragear packages. This would make
> it
> possible to enter new entities and not breaking anything.
>
> --
> fr.gr.
>
> Freek de Kruijf
>
> Just a thought, not specially connected to the theme :-) As representative
of an agglunative language with many cases I can only partially agree. Yes,
entities are quite useful if used to denote names (in broader sense) which
occur independently, i.e. not in sentence. But as entities are also used
extensively in sentences - as in documentation - I always have to think
should I use them or not. E.g. essentially I can't use entity for System
Settings, at least not in translatable form - for that I'd need at least
three separate entities for different cases in my language. And I remember
a real entities' nightmare - was it Kleopatra's handbook which had entities
for every UI element?
Marek Laane
Estonian translator
[Attachment #3 (text/html)]
<br><br><div class="gmail_quote">2012/8/7 Freek de Kruijf <span dir="ltr"><<a \
href="mailto:f.de.kruijf@gmail.com" \
target="_blank">f.de.kruijf@gmail.com</a>></span><br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> Op maandag 6 augustus 2012 23:52:28 schreef Albert Astals \
Cid:<br> > El Dilluns, 6 d'agost de 2012, a les 18:49:24, Freek de Kruijf va \
escriure:<br> > > Op maandag 6 augustus 2012 20:52:13 schreef Albert Astals \
Cid:<br> > > > > Hi,<br>
> > > ><br>
> > > > It is better to avoid using entities for extragear (it has \
different<br> > > > > release cycle) [1].<br>
> > ><br>
> > > There's no need to avoid entities, just do not use entities \
introduced<br> > > > in<br>
> > > a<br>
> > > kdelibs version bigger than the minimum kdelibs required by software \
X.<br> > ><br>
> > Where does one find such information?<br>
><br>
> Nowhere that i know. You ask the maintainer of the program, or you ask me,<br>
> or you don't use entities.<br>
<br>
Entities are very useful to enter the credentials of a translator / developer<br>
/ documentor in just one place. So if something changes in these credentials<br>
one has to change it in just one place.<br>
<br>
I would recommend to have a rule that entities are only added to or changed in<br>
kdelibs, never removed, and are backported to previous living releases, and<br>
have a release cycle more or less like extragear packages. This would make it<br>
possible to enter new entities and not breaking anything.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
<a href="http://fr.gr" target="_blank">fr.gr</a>.<br>
<br>
Freek de Kruijf<br>
<br>
</font></span></blockquote></div>Just a thought, not specially connected to the theme \
:-) As representative of an agglunative language with many cases I can only partially \
agree. Yes, entities are quite useful if used to denote names (in broader sense) \
which occur independently, i.e. not in sentence. But as entities are also used \
extensively in sentences - as in documentation - I always have to think should I use \
them or not. E.g. essentially I can't use entity for System Settings, at least \
not in translatable form - for that I'd need at least three separate entities for \
different cases in my language. And I remember a real entities' nightmare - was \
it Kleopatra's handbook which had entities for every UI element?<div> \
<br></div><div>Marek Laane</div><div>Estonian translator</div><div><br></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic