> Where are we supposed to put our comments (not developer comments,
> translator comments to each other)?
I never really try to check whether po-debconf discard existing
comments or not.
Denis?
(CC'ed to get attention on the thread in case you read -i18n a bit quickly)
--
To UNSUBSCRIBE, e
On 16/06/2005, at 2:56 PM, Christian Perrier wrote:
Confused. We edit the POT file to create a .po file (only changes are
headers). Then we input translations. Normally, in a gettext .po
file, you input translator comments as well, in the .po file. Are you
saying not to do that?
Yes. For debc
> Confused. We edit the POT file to create a .po file (only changes are
> headers). Then we input translations. Normally, in a gettext .po
> file, you input translator comments as well, in the .po file. Are you
> saying not to do that?
Yes. For debconf stuff, this is not the way to proceed,
On 15/06/2005, at 7:54 PM, Luk Claes wrote:
Actually all we want as translators is clearly stated in the gettext
manual [1].
* Decent English style
* Entire sentences
* Split at paragraphs
* Use format strings instead of string concatenation
These are explained in the link.
Cheers
Luk
Als
On 15/06/2005, at 7:02 PM, Eddy Petrisor wrote:
Anyway, no need to argue here; I will try to modify the dpkg source
and add automatic comments, so the quality of the messages in dpkg
improves.
Much appreciated: thankyou. :)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm
On 15/06/2005, at 3:19 PM, Christian Perrier wrote:
Christian, read the quote above: "In the case of the translator..."
Surely we can still input comments?
Yes, sure. But don't tell them to put them in the POT files. They have
to put them in the "templates" file, commented by a "#"
Confused
On Wed, 15 Jun 2005, Bartosz Fenski aka fEnIo wrote:
> On Mon, Jun 13, 2005 at 08:40:38PM +0300, Konstantinos Margaritis wrote:
> > gobble replaced file `%.255s'
>
> I had problem with this string too.
>
> [...]
>
> One more thing about dpkg templates. Is it possible to split some BIIIG
> messages
On Mon, Jun 13, 2005 at 08:40:38PM +0300, Konstantinos Margaritis wrote:
> gobble replaced file `%.255s'
I had problem with this string too.
[...]
One more thing about dpkg templates. Is it possible to split some BIIIG
messages to several smaller onces?
Now I got fuzzy in message which is ~70
> My point is: the messages can be rephrased so that they express the
> same thing, but the message is clearer, more correct from an English
> grammar POV and easier to translate.
apparently I need a grammar checker, too :D
--
Regards,
EddyP
=
"Imagin
> > > Correct, it's a syscall. This error is reporting the
> > > failure of a syscall, so has to use the name of the
> > > syscall that failed, obviously.
> >
> > In the version whoever will try to fix the error gets, yes.
> > In the version the user gets, no. System calls don't mean
>
> I guess
> I agree with you on that, but I would like to remind you
> that the message-ids technically are POSIX/C and not
> English.
That is a wrong assumption; the template could be in Spanish,
Romanian, or Dutch, it does not matter
OTOH, POSIX/C is _not_ a language, but a standard. And we are talking
h
* Clytie Siddall <[EMAIL PROTECTED]> [050615 05:55]:
> Double spaces are not valid in English. I have no idea why they are
> used in some .po files. I always remove them.
Some people use them, to render texts more readable. I find it easier
to read, too, if the space after a full stop is bigge
Scott James Remnant wrote:
> I think it's important that the English messages in dpkg
> be good, clear English.
I agree with you on that, but I would like to remind you
that the message-ids technically are POSIX/C and not
English.
> I do not believe that this should be sacrificed for the
> sake
13 matches
Mail list logo
