Re: lynx-dev How to maintain sources with gettext() ?

[dickey]

> But then who *does* update the other language files? 
>  
> I know what SCO does: if a message is updated, the person doing the 
> update changes it in all the message catalogues, replacing the foreign 
> language messages with "STILL_ENGLISH rest of English message". 

I haven't experimented with this, but (reading the GNU gettext documentation),
it indicates there's a way to automatically (with tupdate) mark the
messages that have become orphaned or obsolete as comments.  Probably
we can reduce this to a less-manual procedure - something that reads the
message catalogs and lists the messages that have to be updated.

> Translation teams dig out those "STILL_ENGLISH" tags and correct the 
> messages.  The rule is to change it to "STILL_ENGLISH rest of message" 
> even if you *think* you know the right translation, because all too 
> often people who think that are wrong.  Lynx, having a much more 
> international development team, would probably have people doing updates 
> who would know the correct messages in 2, 3, maybe even more languages, 
> but still not all of them.  So I think a good rule is: 

> >Bela< 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey