[i18n] internationalization can't be used in C++

[Michał Sawicz]

I would expect to be able to use the same i18n setup in both C++ and QML.

[Tim Peeters (tpeeters)]

What does this mean? None of our components are available in C++.

We use gettext, so that's what you use in C++.
The gettext that we use is exactly the same as the one you can use in C++, so it will have the same settings/libs/dictionaries.

[Michał Sawicz (saviq)]

Of course, but using tools provided by Ubuntu Components would be convenient. If you guys decide that's not what they are supposed to provide, that's fine with me, only I was surprised not to be able to use them in C++. Gettext is probably a special enough case to warrant providing that convenience.

[Tim Peeters (tpeeters)]

We could provide a header file with #defines that makes the tr() functions available by mapping them to gettext() calls, in the same way as we did for the QML binding. That makes things more consistent.

[Tim Peeters (tpeeters)]

actually it is there already, but we need to make i18n.h available as an "official" API.

[Albert Astals Cid (aacid)]

Opinion? Really? sad