Re: Pattern for spell-checking in po-files.

[Karl Eichwalder <keichwa@gmx.net>]

"Göran Uddeborg" <goeran@uddeborg.se> writes:

> Dwayne Bailey writes:
>> It does make sense to check the msgid if you want to spell check the 
>> original untranslated English.  The corrections in the PO would be 
>> useless but finding the errors and correcting them via a jump to source 
>> or by sending info to MSGID_BUG_ADDRESS is very usefull.

Yes, or just enter the correction into the msgstr field and let
somebody else sort out what is the best to do with your correction :)
Either use it as an .en_US.po file or put the correction back into the
source files; ycp_puttext exists to perform such a job for ycp, the
YaST extension language.

> I probably consider it better to create ispell patterns for the source
> language for that purpose.  And it could be a bit error prone; if the
> functionality is there, it might confuse somebody into thinking the
> original message could actually be FIXED in the po file.

Yes, but often there a (native) language experts who don't want to
delve into source code.  They are happily spell checking .po files.

> But if someone bothers to implement this anyway, just make sure you
> check EITHER the msgid OR the msgstr in a particular run, not both.
> They should obviously be checked with different dictionaries.

These are important points.

-- 
                                                         |      ,__o
http://www.gnu.franken.de/ke/                            |    _-\_<,
ke@suse.de (work) / keichwa@gmx.net (home)               |   (*)/'(*)