[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: proofreading the installation-guide

Christian PERRIER wrote:
> Quoting Samuel Thibault (sthibault@debian.org):
> There is ("msgattrib --clear-fuzzy") but this will un fuzzy also what
> was fuzzy before, which is not intended.
> The real safe way is the first method:
>> - fix the english text
>> - fix the english version in the corresponding .po files *exactly* the
>> same way, so that po update will be a no-op
> That may be painful to do if the changes in English text are
> complicated and end up being splitted on more than one line in the PO
> files (which will make a very painful "sed" operation to do)

They're frequently going to be that sort of complicated reshuffle, and
a long way beyond anything I'd trust to sed.

It's looking as though the only way this is going to be doable is if
I split it up into multiple runs with different methodologies:
 1) things like converting <classname> → <package> and dhcp → DHCP
	which ought to be introduced across the whole manual in one go
	but are relatively easy to apply to the translations;
 2) semantics-preserving grammar-fixes etc. that I can introduce in
	stages, chapter by chapter;
 3) other things, if I live long enough.
But I'm rather confused by the way instead of per-chapter .po files
(like "trunk/manual/po/fr/post-install.po") some languages have
complete translated copies of the individual .xml files (such as
"trunk/manual/de/post-install/post-install.xml").  What's the
procedure for those?

>> In that case, it may be hard to fix the translations. For those where it
>> is easy (fixing numbers, which AIUI are in all languages written with
>> arabic numbers), this is the same as b) and c). For other cases, you can
>> commit your change.  Christian, do you think he should update po files
>> and commit the fuzzied result, so that further po updating will be
>> no-ops?
> Yes, that's the better way, imho.

Just to be sure: when people talk about "updating" a .po file, they
don't mean the stage of manually editing it to be up-to-date, they
mean running a particular .po-update script that handles the
importing of new strings, right?
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package

Reply to: