Showing 1-4 of 4 unresolved posts
4
GlotPress Trac Core i18n Tickets
Hey everyone, we made a few tweaks to the upcoming WordPress for iOS that Isaac wrote about here. We decided to add several detailed error messages to our new create account flow(about 25 of them) to better help users as they encounter different errors. Would you mind jumping in and helping translate at http://translate.wordpress.org/projects/ios/dev when you can? I know some of you have already jumped in and helped with this release and your help is much appreciated!
Thank you!
We have a new release of WordPress for iOS nearly ready and have finalized the strings, so please jump in and translate at http://translate.wordpress.org/projects/ios/dev when you can! This update adds a much improved welcome guide and login/sign up that should be much more pleasant for new as well as returning users.
Can you add the catalan language?
Can i add Vietnamese?
Hungarian became 100%
Swedish is 100%
There is no Greek language.
Not sure which one you meant, created both Greek and Greek (Polytonic).
May I be validator or is someone else? Also in Greek for WordPress and buddypress
German completed!
There were some last minute strings added (9 of them). Could you guys take a second look please?
Swedish is back at 100%
I translated French, but strings are still waiting for validation. Unless someone can validate them, can I be made a validator? /cc @vanillalounge
I’ve translated the danish strings, but lack the authorisation to approve them. Could someone approve them for me (or promote me?)
German was at 100%. Now 5 Pages untranslated!? What happened?
Sorry about that, there was a mess-up with the original english strings and their fall backs. We’ve had to re-add all those strings. The translations are still there though, so the plan is to have a script run through and add the translated strings back in for all of these so you don’t have to redo it, worst case scenario we’ll do it manually.
There has also been some additions and typos fixed in the english strings (gah!) so those we’ll ask you to take a look at again. So sorry about this, hopefully we’ll get it back to close to completion very soon.
Thanks for the reply!
Should we wait for your fixes or should we re-translate all the strings now?
Wait for now and we’ll see what we can do. Thanks!
Hey everyone, sorry about the confusion with the strings. Isaac mentioned briefly what happened, but I’ll go into more detail.
What happened was that I was encoding a couple of the New User Experience related strings with more developer sounding keys rather than the full english translation and we realized a few days ago that on incomplete translations rather than falling back to the English, the key would be used. I.e., on our New User Experience instead of seeing “Welcome to WordPress” you’d see “NUX_First_Walkthrough_Page1_Title”. Here’s an example:
http://cl.ly/image/3v1S0b0u2F3W
As this was highly undesirable, I went in and updated the string keys to match their english translation. The problem was that if I uploaded this new strings file, all the hard work you and everyone else did would be lost and I didn’t want you all to waste your time because of my mistake. So what I did was before the new strings file was uploaded I downloaded all of the strings files where you had made translations to the strings that were about to be lost. I then uploaded the new file and by hand went in and copied and pasted in your old strings. So almost all of your old work should be retained.
That being said, during that process we also realized that when a user created an account through the new user experience, we weren’t giving the most descriptive of error messages. To fix this, we decided to add in about 25 new error messages so that way if a user encounters an error during the new user creation flow they’ll be able to better understand what exactly went wrong. This is why there are about 2 pages of untranslated strings left on each of the translations you all did, none of those strings existed on GlotPress a few days ago.
Again, I’m sincerely sorry about any confusion I might have caused.
Hi! So we are in the progress of updating the WordPress for iOS app and have some new strings that need translated. Jorge usually updates the translation strings on http://translate.wordpress.org/projects/ios/dev but he’s out of town this week so I need to update it. Can you grant me (irbrad) whatever access he has? Thanks!
Could a da_DK locale be created for WordPress for iPhone? Username: culturemark.
Added
Heads-up, there are new strings (4) on WordPress for IOS.
Hi,
I completed translation of WordPress for iOS and Android to Turkish. What do I have to do now?
Thanks
Nothing, the iOS devs will grab the complete translations when they release. (with all this free time you now have, maybe you could consider changing wordpress-tr.com’s domain name? 
)
haha. I did. 
See: http://www.wp-tr.org What is the next step? Should I put a message to wordpress-tr.com main page or what?
Zé, there is a problem with our host. After domain change we can’t access to our control panel. They are trying to fix that. When they fix it, I’m gonna put a info page for wordpress-tr.com to inform people and redirect them to wp-tr.org. Is this enough or do I have to do anything else?
Cool, thanks. Can’t you do a redirect on the domain name at the host? Should be easy enough…
We’ll make that a bit later. We want to show people that we are changing our domain. If we redirect them automatically, maybe they won’t see the difference. 
This post concerns a serious problem with the iOS app to Chinese users.
Our users report that after their upgrading to version 2.8.1, they are no longer able to type Chinese on the composer screen. I tried and now I can prove this problem really exists.
Most Simplified Chinese users depend on the iOS build-in Pinyin IME to type Chinese on the Qwerty keyboard; and a combination of several letters denote several possible Chinese character / word matches, and users choose from several candidates offered by the IME. (See this screenshot to see how it is expected to work, as in most apps.)
But in the WordPress for iOS app, the candidates cannot be shown. Therefore users became unable to type.
I hope this problem could be investigated and solved as soon as possible. And I really appreciate your hard work. I don’t know if this problem affects other languages.
Hello,
There was a bug in the 2.8.1 release that caused the post editor to work strangely. 2.8.2 was just approved by apple today and it fixes the issue. I assume it will fix the issue you were having with Chinese characters, but let us know if it’s still a problem.
Okay. I will keep checking for available updates on my iPhone and collect reports from Chinese users. I will let you know if this persists.
Thank you!
I already gave my contribution in WordPress for IOS and Windows Phone. Since the number of strings that are still waiting for approval, I hope you can make me(F4dhli) as a validator for WP for IOS and Windows Phone. I am very interested. Is the validator to WP for IOS and Windows Phone already exist or not? Thanks
Hi Zé,
I see Fadhly had indeed suggested translations on both WP for iOS and WP for Windows Phone and currently all strings on WP for Windows Phone are waiting approval. Perhaps you could give me validator access (on Windows Phone and iOS) to approve his translations.
Since Fadhly is so passionate and so wanting to help translate, perhaps it’s best to validate his work first and then perhaps we could weigh on his request.
Thanks.
Thank you. I’ve added you as a validator for both projects.
Hi..
Could you please create a Indonesian project for ‘WordPress for Windows Phone & WordPress for iOS’ on WordPress.org and make me validator? Thanks!
Please do not troll. You have, up to now, left multiple (answered) requests on this blog, on the .com forums, as a personal email to me, as a comment on my own blog and as comments on other people’s blogs. This is not the way to go about things.
Knowing when to hold back is just as important as knowing when to speak up. If you want to contribute to the translations, start suggesting strings first, so that the current validators can determine if your contribution can be elevated to validation rights. Thank you.
Indonesian for WordPress for Windows Phone and WordPress for iOS was created.
When requesting/creating new translations for WordPress for iOS, here’s the exact list of supported locale codes:
ar,ca,cs,da,de,el,en,en-GB,es,fi,fr,he,hr,hu,id,it,ja,ko,ms,nb,nl,pl,pt,pt-PT,ro,ru,sk,sv,th,tr,uk,vi,zh-Hans,zh-Hant
Heads-up, there are new strings on WordPress for IOS.
Hello polyglots! After a long wait, the next release of WordPress for iOS will have translations.
http://translate.wordpress.org/projects/ios/dev
We already have started translating to some languages like es or sv, but it’d be nice if some of the usual translators for those languages could review for consistency. And of course, new languages are more than welcome
Great news!
I’m available for fr_FR.
Nice! Peterhol for Norwegian… Note: I believe iOS only supports “Norwegian bokmål” (nb_NO), not “Norwegian Nynorsk” (nn_NO)
It seems Xcode supports both, but you can only set nb_NO in your phone
That’s a bug, isn’t it?
Not really. Xcode is also for Mac development, where I guess you can set both
Added fr_FR and nb_NO to http://translate.wordpress.org/projects/ios/dev
and Peter as validator for nb_NO
הוספתי תרגומים בעברית. ממתין לאישור המחרוזות.
I would like permissions for Hebrew transtations, i already started translating.
User name: ramiy.
Hebrew = he_IL
Done.
Done translating to hebrew.
( “WordPress for iOS” )
Can you five me permissions to tanslate “WordPress Plugins” and “BuddyPress” to hebrew (he_IL) ?
Pleasepleaseplease start a new thread, before my head explodes thanks
BuddyPress (@polyglot.wordpress.org) sounds pretty good these times, doesn’t it?
I would like to contribute the German language (de_DE).
I forgot your .org username 
Remind me?
Don’t know if you need another translator for de_DE. If so, you can add me as well.
My WordPress.org Username is MartinIQ.
Added. Assumed it was ok with Torsten, given all the rest
I don’t know if a ‘job done’ message is required, but due to a team effort German is now at 100%
Hi Torsten and others,
the translation made in on translate.wordpress.org is not used in WordPress (yet?), so don’t waste time on this. The WordPress Deutschland Team is still translating WordPress at their own GlotPress.
Why? You know the “Sie” and “Du”-Dilemma (formal and informal german), but on translate.wordpress.org it’s weirdly mixed. With our own GlotPress we ensure consistency in translation and language files for both german form of address.
I would like permissions for Bosnian. User name: kenan3008
All set
Thanks Zé, all done
How the translation is going to work? will it be embedded in the IOS app? I would like it to be provided as a plugin and the app to be able to upload the strings from the blog.
In any case, just by looking at the translation strings, the app seems to be geared up towards wp.com users. this is probably the wrong place to bring it up, but if there is no hebrew translation for the videopress plugin then how can I recommend downloading this plugin for hebrew speaking users?
The translations will be bundled with the app. I don’t think it’s possible to do it in any other way
which means that a translation bug will have to wait for the next release (which from what I heard about apple approval process is a slow thing) and it will not be easy to customize the translation for other needs (the best example is that sometimes you want to refer to the wp installation as a blog and sometimes as a site).
The string file can be retrieved from the wp site via xml-rpc. Maybe only on first “registration” with the site with some expiry mechanism in place.
Don’t bother to help translating WordPress stuff to Hebrew, as its translation is currently controlled by a dictator who won’t approve your strings anyway.
I wrote a comment on his blog to remind him that he previously deleted all of our work, and not only he deleted my comment, he also closed the post from new comments.
I hope that one day Ran Yaniv Hartstein will stop from his bad behavior and will allow to WordPress to act as an open community here in Israel.
@Tomer, In my opinion, a little courtesy goes a long way, but be the merits of your point what they may be, this P2 is not the place to present them, much less in such tone. Internal discussions regarding a particular locale should be carried, well… internally. I believe there is a specific section in http://he.forums.wordpress.org/ to do just that. Thank you.
@Zé, I’m involved in many open source projects mostly as a translator but not only, I have never seen such way of acting.
We can’t discuss Ran about anything in his forum since our posts are being deleted brutally.
Regardless of the way we chose to disagree he just ignored both me and Tomer with all sorts of iinadequate responses.
If talking to Ran was the solution we would have done that but his brutal acts and his agressive way of keeping our mouths shut is untolerable and we are turning to you guys after many tries out of desperation.
Ran is not a true open source activist and his way of acting shows that, I coordinate many open source projects and I never disrespected someone the way he did, its both insulting and agressive.
His lack of experience in software translation is pretty clear and instead of listening to our advices he just shut our mouths over and over again, so please guys, we are not shouting out for nothing.
Kind regards,
Yaron Shahrabani.
I wasn’t so much defending the merits of one or the other position. My point is one of procedure, i.e. this debate should happen elsewhere.
It can’t happen elsewhere, he can delete our posts in the Israeli forums.
@Ze, you really don’t get it, do you?
All other bugs will have to wait for next release as well – the current solution should serve just as well for the translations is it does for the rest of the app.
Not sure why you mentioned VideoPress?
Side note: I tried to translate
“http://itunes.apple.com/us/app/wordpress/id335703880?mt=8″
…into…
“http://itunes.apple.com/fr/app/wordpress/id335703880?mt=8″
…and GlotPress gave me a “Warning: Lenghts of source and translation differ too much.” message. I discarded it, but the team might wanna have a look at this. Also, it’s “lengTHs”
According to http://www.apple.com/iphone/specs.html
Language support for English (U.S.), English (UK), French (France), German, Traditional Chinese, Simplified Chinese, Dutch, Italian, Spanish, Portuguese (Brazil), Portuguese (Portugal), Danish, Swedish, Finnish, Norwegian, Korean, Japanese, Russian, Polish, Turkish, Ukrainian, Hungarian, Arabic, Thai, Czech, Greek, Hebrew, Indonesian, Malay, Romanian, Slovak, Croatian, Catalan, and Vietnamese
Not sure about the exact language codes, but those are the supported languages.
Does it makes sense to translate to Serbian since it’s not on the list?
I haven’t used iOS devices so I don’t know how their language support work, ie. is translation automatically enabled if available for app, can user change language (in which case it would be possible to use Serbian if technically possible) etc.
No, if it isn’t on the list you can’t set that as your phone language. While we can add the translation, there’s no way to enable it
Thank you for explanation, it’s pointless to do translation in this case.
You should make this information more prominent so that translators in other unsupported languages can see it before requesting translation and doing it.
Dutch = 100% 
I’m available for the Finnish translation. Don’t know what Apple uses, either ‘fi’ or ‘fi_FI’.
fi and Daniel added, thanks
Thanks!
Please add Croatian language. User name: yuraz
Added
Sadly, iOS do not support Burmese.
Testers needed
Ticket #157 (Add support for iOS/Mac .strings files)
jenia, 
sendhil, 
Dan are discussing. 
Torsten Landsiedel 10:07 am on May 21, 2013 Permalink | Log in to Reply
German back at 100%!
Torsten Landsiedel 10:08 am on May 21, 2013 Permalink | Log in to Reply
Due to a team effort. Props to MartinIQ @iqatrophie !
MartinIQ 3:32 pm on May 21, 2013 Permalink | Log in to Reply
Hey, thanks for the shout-out.
By the way, my .org username is ‘MartinIQ’.
sendhil 4:43 pm on May 21, 2013 Permalink | Log in to Reply
Thanks guys!
Kevin Kyburz (@swissky) 5:43 pm on May 21, 2013 Permalink | Log in to Reply
I have translated yet 3 strings which were still empty
Sendhil 5:32 pm on May 22, 2013 Permalink | Log in to Reply
Sorry about that! I think we had some strings for the next release that got tweaked that snuck in there.
Xavier Borderie 12:03 pm on May 23, 2013 Permalink | Log in to Reply
French is back at 100%, thank entirely to @paolal
Sergey Biryukov 4:57 am on May 27, 2013 Permalink | Log in to Reply
Russian is done. Thanks to @jenia and @kovshenin for help.
jenia 7:41 am on May 27, 2013 Permalink | Log in to Reply
Thank you for bringing it to 100%!