> I think Sandra is interested in improving the experience of
> translators and some of the remaining alerts seem in phase with that,
> so I am holding back from them :)
That's correct. I have used Weblate to translate our interface to my
native language (Dutch) and, even though I consider myself a seasoned
power user with a lot of tolerance for complex interfaces... I find
Weblate's end-user interface and guidelines complex, confusing / not
inviting. I think it's a big hurdle to get more people to actively
translate our UI.
So (actually before we received the alerts below) I wrote down a project
proposal to do some dedicated work to improve this situation. You can
find the proposal here, and comment on it:
I could do this myself, but I'm not sure I'll have the time. I will take
a look in the upcoming weeks if it can be done as an Outreachy
internship (although it asks for very specific skills, more
community/linguistics than development focused). I'm also not sure if
I'll have the time/energy to be an Outreachy mentor in the next round.
If I follow up on this, I'll do it on the general user mailing list (as
I think this really concerns our end users at large). If someone here
wants to help, let me know, I'd be grateful :-)
FWIW: End user experience-wise, I hear much better things about
TranslateWiki. My (limited) personal experience as a translator there is
also better. And some of our most active user communities (Wikimedians)
are already there, which would really help in getting OR's interface
translated to more languages. I understand that we have not chosen
TranslateWiki but have preferred Weblate for technical reasons (better
integration with our code repository and processes??) but I'd be happy
if we can keep an open eye looking at other solutions. Having our
interface translated well and completely to as many key languages as
possible is the thing that really matters for our end users, and in the
current situation we're not really there at all.
>> * Define translation instructions to give translators a guideline.
>> * Fix this component to clear its alerts.
>> * Add screenshots to show where strings are being used.
>> * Use flags to indicate special strings in your translation.
>> * Enable add-on: Add missing languages
>> Ensures a consistent set of languages is used for all components
>> within a project.
>> * Enable add-on: Cleanup translation files
>> Update all translation files to match the monolingual base file. For
>> most file formats, this means removing stale translation keys no
>> longer present in the base file.
Sandra Fauconnier (she/her)
Project Director, OpenRefine
Subscribe to OpenRefine's user mailing list: https://groups.google.com/g/openrefine