Re: lynx-dev protection 444 for fr.po

[dickey]

> > > > checked-in -- I expect there'll be more than one patch to fr.po, and  
> > >   
> > > I should certainly hope not to the one in the Lynx distribution.  
> >  
> > actually yes.  There shouldn't be any html in the msgid's.  It'll just 
> > create a lot of maintenance problems.  I reorganized a fair number of 
> > the strings in the C code to work around this, but there's more.  It 
>  
> I still don't understand why you feel the need to maintain fr.po unless 
> you just enjoy doing it.  Anyway, I assume you know about the -j option 

I just want to have an example for testing (english/english doesn't help
me much).  I'm not planning to _maintain_ fr.po so much as to resync so
that we don't lose Jim's changes.

> to xgettext.  It would also make the file a bit smaller if you'd use 
> the --no-location option.  Since you plan on supporting the build in 
> /po, you might consider adding the --no-location option as a default. 
on my list...
  
> I did find that I lost about half of the 400+ translated strings I had 
> done on Jim's code set when I updated to dev2.  I hope to be able to 
> salvage them, but it might mean hand editing.  (Moan.)  If I figure out 
> what triggered the loss, I'll let you know.  I hadn't worked on any 
> strings with html tags in them, so that wasn't it.  Did you switch 
> locations of "%s" or "%d" in places?  There were a few strings with 

I don't recall switching the %s and %d - just split up the strings
that had html in them.  (The %s and %d tokens are less of a problem
for maintenance than the html, and far more difficult to adjust).
But that's just my opinion.

> trailing white space.  Are these all going to be revised to strip it 
> off?  (If so, I'll put off translating those, too.) 

I believe LP recommended stripping the trailing blanks.  I hadn't really
thought about it.
  
> __Henry 


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