Menu
▾
▴
[xine-bugs] [ xine-Bugs-1095451 ] Gxine no longer support translation
|
From: SourceForge.net <no...@so...> - 2005-01-09 18:30:27
|
Bugs item #1095451, was opened at 2005-01-04 04:06 Message generated for change (Comment added) made by mroi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109655&aid=1095451&group_id=9655 Category: gxine Group: current cvs version Status: Closed Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Darren Salt (dsalt) Summary: Gxine no longer support translation Initial Comment: Hi After close Bug 1094792 gxine no longer use german translation. If i start gxine and have german environment (LC_ALL=de_DE@euro) gxine start but it only support english language. Output is: (process:22730): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Best regards ---------------------------------------------------------------------- >Comment By: Michael Roitzsch (mroi) Date: 2005-01-09 19:30 Message: Logged In: YES user_id=552060 This should even be possible with pure glibc functions, although a bit more difficult. Converting a UTF-8 string to a widechar string involves only some byteshifting. Then, wcstombs() can be used to convert the widechar string to a multibyte string of the current encoding. FLTK contains such code: http://cvs.sourceforge.net/viewcvs.py/fltk/fltk/src/utf.c?view=markup (search for utf8tomb) Michael ---------------------------------------------------------------------- Comment By: Frantisek Dvorak (valtri) Date: 2005-01-09 11:14 Message: Logged In: YES user_id=543511 When GTK requires UTF-8, hasen't GTK some functions for output to console? But don't waste the time, if it would be difficult. :-) Frantisek ---------------------------------------------------------------------- Comment By: Darren Salt (dsalt) Date: 2005-01-04 20:04 Message: Logged In: YES user_id=294680 You're missing the "de_DE.UTF-8@euro" locale. That said, I've now implemented a (hopefully) better fix for the original problem - gxine should now work regardless of the presence or absence of that locale. This fix has a side effect: messages which are output to the console will always be encoded using UTF-8. I'm not considering that to be important. ---------------------------------------------------------------------- Comment By: Darren Salt (dsalt) Date: 2005-01-04 20:04 Message: Logged In: YES user_id=294680 This bug entry is believed to be fixed in cvs. Please reopen it as needed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109655&aid=1095451&group_id=9655 |