Re: non-utf8 po files breaking the build



Yanko Kaneti <yaneti@declera.com> writes:

> Currently my preference is for one-encoding-only working tools over
> constantly breaking multiple-encodings-aware tools.

Sure, but it won't hurd to check for proper input first -- maybe one
can setup CVS to do the conversion at checkin time...

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]