[Gstreamer-bugs] [Bug 114216] Changed - Gstreamer needs localization (l10n) support

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=114216

Changed by in7y118 at public.uni-hamburg.de.

--- shadow/114216	Mon Jun  2 18:08:33 2003
+++ shadow/114216.tmp.540	Tue Jun 17 09:58:38 2003
@@ -81,6 +81,32 @@
 Of course, g_warning() should be translated.
 
 GStreamer has more of a problem with not having _good_ messages,
 compared with actually i18ning them.  There's a discussion on the
 gstreamer-devel mailing list currently about error reporting.
 
+
+------- Additional Comments From in7y118 at public.uni-hamburg.de  2003-06-17 09:58 -------
+What should not be translated:
+- Debugging messages (GST_DEBUG and GST_INFO)
+- Warnings and error messages (g_warning and stuff)
+
+What needs to be translated are:
+- The popt stuff for command line arguments
+- Description fields (for elements, plugins, signals, ...). These need
+to be made user-understandable, too. (I'm thinking about a user of
+gst-editor, not my grandma)
+
+This is consistent with glib and gtk.
+
+Where I'm not sure if it should be translated are gst_element_error
+messages.
+After discussing error messages at GUADEC we decided to change this to
+use a GError instead of a string. We only need to define the
+categories. Gst-Player should then construct its error messages
+depending on the categories and the elements that emitted them (if a
+source can't open something it's probably "file not found", if a sink
+can't open it, it's "soundcard in use").
+The message in gst_element_error should still be a message directed at
+the developer, so it doesn't make sense for me to translate it.
+However glib and gtk do translate them, so I have no idea what
+solution would be right.