Special characters (german) and menu entries missing in ardour2-beta10

Hi,

I installed ardour2beta10 and get a lot of warnings when starting it (see below) and while loading a session.

Within ardour, special german characters aren’t shown. A lot of menu entries are missing, and I think all the missing entries have special german characters in them (can’t say for sure because I can’t see them).

Is this a bug in ardour2-beta10 or could it be something with my systen?

In ardour 0.99.3, the language of the menus is mixed (english+german), so I’m not sure if everything’s well set up in my debian system.

Thanks for help,
Benjamin

sound@sound:~$ set_rlimits ardour2
Ardour/GTK 2.0beta10
(built using 1266 and GCC version 4.1.2 20061115 (prerelease) (Debian 4.1.1-2
1))
Copyright © 1999-2006 Paul Davis
Some portions Copyright © Steve Harris, Ari Johnson, Brett Viren, Joel Baker

Achtung: Es gibt zu Ardour KEINERLEI Gewährleistung!
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Dies ist freie Software und Sie dürfen sie gerne weiterverbreiten,
under certain conditions; see the source for copying conditions.
Loading ui configuration file /usr/local/etc/ardour2/ardour2_ui.rc
theme_init() called from internal clearlooks engine!
loading system configuration file /usr/local/etc/ardour2/ardour_system.rc
loading user configuration file /home/sound/.ardour2/ardour.rc
OSC @ osc.udp://localhost.localdomain:3819/
ardour: [INFO]: No H/W specific optimizations in use
ardour: [INFO]: looking for control protocols in /home/sound/.ardour2/surfaces/:
/usr/local/lib/ardour2/surfaces/
ardour: [INFO]: Control surface protocol discovered: “Generic MIDI”

(ardour.bin:1444): Gtk-WARNING **: Failed to set label from markup due to error
parsing markup: Error on line 1 char 9: Invalid UTF-8 encoded text

(ardour.bin:1444): Gtk-WARNING **: Failed to set label from markup due to error
parsing markup: Error on line 1 char 9: Invalid UTF-8 encoded text
ardour: [WARNING]: Ihr System generiert “Mod2” wenn NumLock gedrückt wird. Dies
kann zu Problemen führen. Ardour wird deshalb als Meta-Taste Mod3 an Stelle von
Mod2 benutzen.

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout
_set_text()

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout
_set_text()

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout
_set_text()

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout
_set_text()

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string
loading bindings from /usr/local/etc/ardour2/ardour.bindings

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

[NOTE: this line repeats itself much more, Benjamin]

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout
_set_text()

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout
_set_text()

Gtk-Message: /usr/local/etc/ardour2/ardour2_ui.rc:88: failed to retrieve property GtkWidget::cursor-color' of typeGdkColor’ from rc file value “((GString*) 0x8a13460)” of type `GString’

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string
Loading session /home/sound/projects/intervire using snapshot intervire (1)

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string
Loading history from ‘/home/sound/projects/intervire/intervire.history’.

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Gtk-WARNING **: Invalid input string

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

(ardour.bin:1444): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

i can confirm that in the german version the menues are not complete at all, also i found out that ardour crashes even if i try to import existing audio.
thats why i always start ardour with:

LANG=en_US.UTF-8 /usr/bin/ardourvst

also ardour 99.3 is having a strange behaviour (window size etc.) if i start without that prefix.

dont know if it is worth trying to repair the locale thing, since we all can speak english (more or less) and there are still much more important things to fix, untill ardour2 will be solid enough for a real production.

cheers,
doc

Hi,

i wrote a mail do the ardour-dev list about this topic last week, but it got lost somewhere…

I made two screenshots:

  1. http://www.flickr.com/photos/71007780@N00/345857514/

  2. http://www.flickr.com/photos/71007780@N00/345878818/

As you can see in picture 2, the “new session” dialog contains some
tags wich should not be there…

The Screenshots are exactly what I’m getting.

It’s definitly worth repairing the locales, because otherwise ardour2 should be made only available in english. You can’t ever distribute a so called “stable” ardour2 if german users aren’t able to locate the “open” button… And getting the locales to work shouldn’t be a too hard challenge (though I’m not a programmer).

Is there a bugreport for this? I didn’t find one. If you don’t find one, either, we should do one.

Benjamin

I filled a bug report using a picture of yours, mauser, I hope you don’t mind :wink: I saved it and submitted it, so it’s no link.

I marked it as major because you can’t really use the program in german language (except you know the menus by heart). I hope nobody takes this “major” to offensive, it wasn’t meant…

Bugreport ID: 0001429

Benjamin

Hi Benjamin,

some weeks ago I started translating most of the messages into German and I am still working on it, so this is the current status of my German translation in beta10.
I had the same error when translating the messages, a hint at the developer mailing list solved this problem by switching to a UTF8 locale (de_DE.UFT-8).

[ edit: see http://lists.ardour.org/pipermail/ardour-dev-ardour.org/2006-November/003833.html ]

I didn’t realize that all users also have to switch in order to get all characters working. Can someone please help out? What about the other languages?

Best regards, Sebastian

Looks like you did it Sebastian, taybin marked my bugreport as solved and noted:
“Fixed in the latest SVN. Thanks Sebastian!”

So much thanks to you!

Benjamin

I had the same problems as you Benjamin (Ardour 2 beta 10 before build 1266 and de_DE.utf8 locale settings) but now it works great -

thanks to all developers and translators

gerald