Re: Re: [MrProject] MrProject 0.8 - the Cheeky Release (touch my calendar)
Christian Rose <[email protected]> 22 Jan 2003 15:53:37 +0100
| Newsgroups | gmane.comp.gnome.apps.mr-project.devel |
|---|---|
| Message-ID | <[email protected]> |
ons 2003-01-22 klockan 12.38 skrev Keld Jørn Simonsen: > > > > > > Also, the file wasn't committed as UTF-8. *Please* use UTF-8 for your > > > > > > GTK2/GNOME2 translations. > > > > > > > > > > My files is in UTF-8 - so somewhere on its way someone must have changed > > > > > the charset... > > > > > > > > Yes. Also, the file header was changed to say iso-8859-1, so it doesn't > > > > look like an accidental conversion. > > > > > > Yes, I did that on purpose. I would like you to extend your > > > character handling to also cover iso-8859-1, I know this is possible in > > > other translation projects. > > > > Abusing CVS is *NOT* the way to somehow get your will through. > > The purpose was not to abuse the CVS, but to do edits in the > character set I use here. And then do spell check. > I got the source in a problematic state, > it was in 8859-1 encoding but labelled utf-8. > I was not aware that not using utf-8 was considered subversive. > There are a number of sources in the gnome cvs that comes in > 8859-1 for the sources I maintain. Only a small number, mostly GNOME/GTK 1.4.x software. MrProject HEAD is certainly GNOME2/GTK2 software and hence uses UTF-8 po files. If you have trouble finding out if you should store your da.po update as iso-8859-1 or UTF-8, you can always check the encoding of the existing da.po, or check the encodings of the other po files. That should give a hint. If you had done that in this case, you would have found out that not only was the existing da.po in UTF-8, but so were all other po files as well. And if you are still uncertain, ask the maintainers before committing. Please be more careful in the future, Christian