This string comes from an internal copy of glib. The internal copy is only used if Cogl is configured with --disable-glib. That means it effectively won't be used in a Gnome system. It is only likely to be used on a limited embedded system and I wonder if in that case it doesn't really make sense to translate the strings anyway. Maybe we should just remove the internal copy of glib from the list of translated files?

The string has been fixed in glib itself via bug 687698

Created attachment 229728 [details] [review]
l10n: Remove the internal copy of glib from the list of gettext files

We probably don't want to include the internal copy of glib in the
list of files to scan for translatable strings because these strings
already exist in glib itself and it is a waste of translator's time to
translate them again.

If we wanted to make this work properly, maybe we could adopt a system
where we also copy the translated strings from glib into cogl and then
merge them into the message catalog during the build. However it
doesn't seem like translated strings would be that useful in
situations where --disable-glib is used, so maybe it's not worth
bothering with.

this looks good to land to me

Ok, I've pushed it to master. I have a feeling there is some sort of automatic process that it will add it back again, but I don't know how it works. It was originally added in this commit:

http://git.gnome.org/browse/cogl/commit/?id=aa5f8e9b9396

I'm very much non-automatic process. :)

I added it to POTFILES.in in order to make intltool happy, but from what I see above I should've put it in POTFILES.skip instead. Now I have pushed a commit to master and cogl-1.14 fixing this. Sorry for the mess I made!

http://git.gnome.org/browse/cogl/commit/?id=bdf88473149e7b7d10bd955e109557ed0231c791

Oh, that makes more sense. Thank you!