I just finished the .po file for “WordPress for Android” in Gaelic. Is there something I need to do to bring this to release or is the process automatic?
Incidentally, has there been any news on some feature that allows users to set the UI language on their mobile system? There are still loads of languages that WordPress supports which mobile OS don’t support :/
Updates from Akerbeltz Toggle Comment Threads | Keyboard Shortcuts
-
Akerbeltz
-
Akerbeltz
Last year was a bit busy and I kinda missed the train on going from 3.4 to 3.5. I’ve just had a shufty in the 3.5 branch and it looks like none of the translations from 3.4 in Scottish Gaelic (gd) got ported from .4 to .5 (for anything, from the main file to the themes and Continents and Cities) – could someone kick that into shape? I assume it’s not ALL new!
Or do I need to work on the Development bit and it’ll then end up in 3.5? -
Akerbeltz
I was going to ask for some pointers on how to update the Gaelic build from 3.3 to 3.3.1 and noticed that we’re at 0% (http://translate.wordpress.org/projects/wp/3.3.x) – seems I’ve been keeping the future 3.4 (http://translate.wordpress.org/projects/wp/dev/gd/default) up to date instead. Now I fervently hope I don’t have to redo that all – could someone let me know what I need to do to get those into 3.3.x? Cheers
-
Jenia
You should be able to import your existing translations. Ask about the best way to do so on wppolyglots.
-
Akerbeltz
Yargh, caught out again… thanks. You know, from a common-mortal POV, WordPress is really confusing, not only does it use the same name for two very different products but also splits and straddles l10n over so many places I feel a bit like Alice in Wonderland sometimes
-
Jenia
Yep, it can be pretty confusing when you are getting started, sorry! But you get used to it quickly. And if you have suggestions about improving/simplifying, they are very welcome!
-
-
-
Akerbeltz
Yes I do. Put them all together in the same place. From an l10n point of view, there’s no need to spread support across Glotpress and Polyglotts and whatever and to have the translations sites across a zillion pages. Create one central hub for support and another central hub where all the translation projects for .com and .org can be centrally accessed on a locale by locale basis. I have so many bookmarks for .org current, future, Continents and Cities, Multisite, Rosetta, 2010, 2011, .com – it’s a total mess. I bet I’m not the only one who gets confused – and you’re probably turning potential l10n volunteers away because it’s so confusing.
-
Andrew Nacin
We use the polyglots blog to coordinate translation efforts. A lot of those translation efforts are centered around translate.wordpress.org, which is a GlotPress install. GlotPress is an open source project.
So, blog.glotpress.org is a place where we can talk about the code that powers translate.wordpress.org, and wppolyglots.wordpress.com is a place where we talk about translation efforts that occur on translate.wordpress.org.
There is a pretty strict separation of translation efforts on .com and .org so you will not see those merging.
-
Akerbeltz
That might as well have been in ancient Sumerian as far as your average willing translator is concerned. I don’t doubt there are reasons for separating stuff at the back end but in terms of the front end, that’s really contortionist to people who don’t eat foobars for snacks…
Anyway, I shan’t carp on about it. Thanks for your help, the setup may be spaghetti, but the support rocks
-
Andrew Nacin
Well, let me try again:
GlotPress is like WordPress. It’s a piece of software you can run. WordPress has its own blog at http://wordpress.org/news/. This blog here is the same thing, but for GlotPress.
translate.wordpress.org is like your personal blog. It’s where the software runs. If your personal blog had a contact form, you could think of that as being wppolyglots.wordpress.com.
-
-
-
Akerbeltz
Thanks. You know, I’m not dense and I localize a lot. The fact you had to try so hard to finally get me to just about understand the difference should tell you something :/
-
Jenia
There’s a bit of a learning curve in the beginning, especially for people who come from the localization background but don’t have lots of developing background. It does start make sense pretty quickly though, please don’t despair!
For the translation of WordPress.com specifically, there is this FAQ: http://en.support.wordpress.com/translation-faq/
And there is an overview of GlotPress: http://en.support.wordpress.com/glotpress/
-
-
(note: this more of a polyglots thing). Yes, branching in Translate WordPress is a bit clunky. Export all .po’s from 3.4 and import those into 3.5, most strings should be covered, but keep in mind that there have been many changes from 3.4 to 3.5, especially help screens and the welcome page.