Re: RE: Translations strings in CVS

[<ldu...@uf...>]

> I was just reviewing the msg catalog translation strings, and I had
> some questions.
> 
> There seems to be different methods used for encoding the files.
> The Spanish msgs use the \u00xx for extended chars, whereas the
> German msgs avoid them by using the lower ascii expansion
> (&uumlaut; == ue).  Hellenic (el.msg) comes across in something
> that I can't view correctly on Windows or Unix (I do have
> bitstream cyberbit on Windows, but no specific Greek font).
> 

I think it because not everyone used the same tools to create the
message catalogue. I used MSGEdit, I think a few others did too (most
likely, the ones that came out with \u00xx). Some used standard editors
which did the output however they felt was best.

> I know this was somewhat discussed, but it looks like no certain
> resolution was imposed.
> 

Uhm... imposed, no. Suggested, yes. I think George had said that the
files he had couldn't be read by the msgcat utility. So he did it how
best he could.

Jan sent us a note today saying he has a little utility that possibly
fixes the problem with George's file. If it does, George will hopefully
be able to send you another version of his translations.

L