Hello Everyone. I have a query which is not related to polyglot but this is urgent for the Korean WordPress users. This is a problem since the WordPress 4.2 install is subject to the MySQL version. Any feedback is appreciated.
Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts
Hi, guys. I’d like to request support for the Silesian language.
Country code: none; PL if compulsory here
Plural forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100=20) ? 1 : 2);
Language native name: Ślōnskŏ gŏdka
Sub-domain: szl.wordpress.org (or szl-pl.wordpress.org if really necessary)
Site Title: Ślōnskŏ gŏdka
Site Description: WordPress po ślōnsku
Admin Username(s): gkkulik
Admin Email: gregorykkulik at gmail.com
I have join in translating Kiswahili (Swahili)and wanted to know who is the moderator. I and a friend we been having lots of “with warnings”
1) how do we download the folder after translation.
Translation of the development version of WordPress.
Strings in this project are taken from code under active development. They can and will change until a string freeze for the currently developed version of WordPress has been announced.
This is what it would look like on https://translate.wordpress.org/projects/wp/dev:
Quick agenda for the Polyglots chat today. If someone has anything to add to the agenda, please comment below:
- Locale stats
- Tech stats
- The “words vs characters” string
- Progress on translating the plugin and theme directories
- Updates to the Rosetta Theme
- WordPress 4.3 project description
- WordPress.com has introduced a new translation tool
- Per project validation – it’s happening, has anyone tried it yet?
See you all on Slack!
In last week’s Polyglots chat (logs) we briefly discussed translating documentation, how it was done in the past and how it should be done in the light of localizing the plugin and theme directories and making WordPress.org better fitted for non-English users.
How do we translate documentation now
In the past the Codex has been translated by simply creating new wiki pages and duplicating and translating the content of current pages manually.
The obvious downside of this is that there’s no version control and translators need to check all pages for changes to be able to bring those changes to the translated documents.
Now that Codex is on it’s way to be replaced by the Handbooks, it would be really handy to have those available locally.
So let’s discuss how we can make that happen.
Localizing the handbooks
A couple of options mentioned during the meeting:
- GlotPress – not ideal, @ocean90‘s comment explains better:
“I agree, that it should be handled via WordPress itself, not GlotPress, because you can do quicker previews, add translated screenshots etc. We still can/should show the English text on the same page, maybe side by side so we could track out of date translations.”
- Adding the handbooks plugin to the locale sites so editors can build there own handbooks – the easiest way to go, but would have no version control so will basically replicate the old way of copy pasting the Codex with no way to track changes in the original documents
- Adding the handbooks plugin to the locale sites and including an “Import original content” with an active relation of each duplicate with the original. A way for the editors to pull changes from the original (doesn’t have to be automatic, can be done manually, just as long as editors don’t have to go check every page for changes).
- One option is something @zodiac1978 pointed out is already being done on wordpress.com: “I am doing this for the support pages for wordpress.com. They use a plugin which send you an email for every change (with a revision diff view of the changes). Then we have to manually add these changes to our localised post/page. This could be one way. But much work …”
Let’s discuss the options above and see what ideas the #metai18n team will have too.
Words or characters: the string 40480 in the dev project (change locale code in the slug to see your language) asks to type in “words” if your language’s word count is based on words, and “characters” if that’s what the wordcount is based on (the case of Japanese and Chinese, for example). “Words” or “characters” should NOT be translated from English.
After this question came up for Bengali (BN), I started spotchecking other locales, and took the liberty to fix this for AR, HU, PT-BR, KO, HE, NL, TR, ID, SV (where “words” was translated to the local languages). I did not check/research each language, so if you have a moment, please double-check the string for your locale.
A related question is whether such “developer” rather than “translator” strings should be part of a GlotPress project, or if there is a better way to handle them to minimize the confusion.
Hi Polygots Team,
I am Bigul from Kerala, India. We have a small WordPress community here in Cochin. We would like to translate WordPress in Malayalam(our mother tongue).
As an initial setup we have translated 2015 WordPress theme and almost completed the 1/4 translation of 2014 theme today( https://translate.wordpress.org/languages/ml ). Before that I have translated few strings of WordPress development and WordPress.com couple of months and still it is pending for approval. Couple of other guys also done the same in past and that is also still waiting for approval.
Therefore please consider me, Nithin and Nebu as Malayalam translation editors. Please note our profile links
https://profiles.wordpress.org/nitkr — Nithin
Thanks in Advance
46 locales are up to date.
5 locales are 100% translated but not yet released for 4.2.2:
- ID is still at 4.1.1, @ekajogja can we help you in any way to release 4.2.2?
- Welsh, Polish, Catalan and Chinese are still at 4.2 or 4.2.1 – @gwgan, @jimmyxu, @xavivars, @waclawjacek, @eclare Can we help in any way to release to 4.2.2?
Localized Plugins and Themes directories are here
@dd32 posted earlier today about Plugin and Theme repositories made available on local sites.
- Theme Directory is available at /themes
- The Plugins directory is also available at /plugins/
- Both already have existing projects on translate.wordpress.org available for localizing
- Deploy after translation should be requested the same you would do all other rosetta translations.
- @chantal: Is there any timeframe when it will be possible to translate plugins/themes thru GlotPress?
- @dd32: No hard timeline, most of the groundwork is there for plugins and it’s just waiting for the floodgates to open after more testing, me or @ocean90 will be working on the Themes-in-Glotpress in the next few weeks I expect, not sure how long it’ll take to get that finalised but now that these directories are localised, we kind of want to finish the job
Also from @dd32 about what plugins are going to be available for translations first:
“The “official” plugins in https://translate.wordpress.org/projects/wp-plugins is the start-list, we’ll expand from there, but no definite what we’ll include first. I suspect we’d start with the most popular ones and work the way down the list, biggest impact first. We might also do some smaller plugins first to get the feeling for the process, work out any bugs.. so no, not sure yet”
- There was a brief discussion around localizing the plugin and theme handbooks and different approaches to that.
- @dd32: “We’d love to have translations of resources such as that. I personally don’t know of any effort to get that working yet though”
- The best solution would allow Translation Editors to easily get notified on changes in the documentation so that those could be applied to localised versions. This means there has to be a direct relation between the original documentation and all the local versions.
- According to @ocean90 GlotPress is not the way to go for Documentation
- @zodiac1978 shared a possible solution wp.com uses: “I am doing this for the support pages for wordpress.com. They use a plugin which send you an email for every change (with a revision diff view of the changes). Then we have to manually add these changes to our localised post/page. This could be one way. But much work …”
- Petya to post a separate post on the P2 to discuss this with more people and bring it to the attention of the metai18n team.
Polyglots at #wceu
- A lot of us will be at WordCamp Europe in Seville – raise your hand if you’re one.
- Let’s discuss a more formal gathering with an agenda for Contributor day, June 28
- Let’s discuss organising a global translation sprint around WordCamp Europe’s contributor day including polyglots who’re not in Seville
- Petya to post a separate discussion topic on make/polyglots about this
If anyone has anything to add to the notes, feel free to drop it in the comments.
Here’s a short agenda for the Polyglots chat today:
- Locale Stats
- Tech stats
- Localized Themes and Plugin Directories announcement – https://make.wordpress.org/polyglots/2015/05/20/hi-everyone-as-some-of-you-are-aware/
- bbPress contributor efforts and local forums
- Polyglots team at wceu – who’s going to be there?
- Open discussion
If you have anything else to add to the agenda, please feel free to add it in the comments.
As most of you are aware, we’ve been pushing to get more of WordPress.org localised, such as the Theme directory and Plugin directory.
Today I’ve enabled localised Theme Directories for all rosetta sites, all sites now have the themes directory available at /themes/, for example: https://ro.wordpress.org/themes/
A few important things to note about this setup:
- The header menu is inherited from the main site (it’s cached for up to 1hr).
- A ‘Themes’ and ‘Plugins’ page have been created on your blog as placeholders for the site, to ease adding these both to the Menu. The title of these pages has been defaulted to
__('Themes')so hopefully it’s translated correctly already for you, but update it if need be.
- The slug ‘themes’ in the URL cannot be modified at this time, that may change in the future though.
- The Themes Directory interface itself can be translated, you can do so via https://translate.wordpress.org/projects/meta/themes and request a deploy the same you would do all other rosetta translations.
- The Themes Description & Title is not yet translated, that’s coming a little later.
- You won’t have access to the wp-admin part of the blog, that’s expected.
A Quick word on the Plugins Directory:
- The Plugins directory is also available at /plugins/
- Still being tested, feel free to join in the testing!
- It can be translated at https://translate.wordpress.org/projects/meta/plugins
- https://ro.wordpress.org/plugins/ is a good example of it in action
If you spot any bugs, please either report it here, or on meta.trac under the Theme Directory component (or the Plugins Directory component).
I’m a validator of the Portuguese (pt_PT) translation team. We’re facing a major issue with our translation. Some of you may have heard of the Portuguese Language Orthographic Agreement of 1990 (AO90). Well, it’s being implemented for 5 years now, with huge resistance in Portugal and several other Portuguese language countries. It’s mainly a political decision, with little respect for history and some basic rules. Nevertheless, it’s being
used byimposed to public institutions.
A while back we had an internal discussion in the Portuguese WordPress Community regarding the adoption of the AO90. The vast majority said no. But now the question arises again, and it seems unfare, even if we still have a strong resistance, that there’s no alternative for those who want or need to have WordPress in accordance to AO90.
Therefore, what I need to discuss with you is the possibility of having variants for the Portuguese language, despite Portuguese in Portugal having only one norm. Me, @ze-fontainhas and several other members of the Portuguese Community have long discussed this possibility and how to implement a solution. Since there are no variants in the Portuguese language in Portugal, there are no ISO codes to identify possible variants. Anyway, it’s something we have to address and we wanted the Polyglots to help us.
Does anyone have any idea how we can deal with this?
Could you please add Welsh (cy) to the WordPress for iOS project?
If I notice an a typo in the original text, how do go about reporting it?
Translation Project for WordPress 4.3
We had a great discussion about this topic, here are some comments which I want to highlight:
- As long there’s a notice on those projects, I think it would be fine. @deconf
- The development project should have a version number.
development - 4.3. @nullbyte
- Should development not always be the next new major release? @chantal
- My greatest fear is that translators happily jump on the dev project and get frustrated when no validators are validating that language. That will cost goodwill and motivation and possibly scare translators away. @tacoverdo
- The best thing would be that this is opt-in so validator for each projects @dimadin
- There are no opt-in situations possible, that would cause a mess we can’t handle. @petya
- For translators and teams that don’t want to translate the strings beforehand, they don’t need to do it. We will still ping everyone that hasn’t begun translating on string freeze and you can handle it after that. @petya
- I don’t see a problem. As soon as somebody decides he/she wants to translate, they no it can take some time to get strings validated. Validators aren’t waiting all day for strings to be approved or not. @chantal
- Ok, let’s say we agree to try it out for 4.3 and monitor the results. If there is screaming and kicking after, we can reconsider. The other important thing to monitor is if it will have actual value for translation editors in terms of testing and deploying translations. @petya
There was no Asia/Pacific chat but I think we can say that decision of the team is pretty clear: We will try this out for 4.3.
I’ll prepare everything so we can start with this by the end of next week. We talked about adding a notice to the project (current text; text can include HTML). @petya and @gluckpress volunteered to prepare a text for this. Feel free to join them if you want to help.
Filling in our translation editor profiles
We need translation editors’ profiles on wordpress.org to be complete and have means for translators to reach you. You should check out your own profiles and then check the profiles of other translation editors on your team and urge them to complete those. A separate post will follow and the info will also be added to the handbook as proposed by @xavier.
Note: Avatar and social media accounts are automatically pulled from the Gravatar profile associated with your e-mail address on wordpress.org.
- The Dutch team got a lot of bad translations again. @chantal
- I’d like to ask EU people, to spend 5 minutes, after the end of this polyglots chat, to talk about the crazy EU cookie law. @wolly
- Just a reminder that locales who create custom builds, specifically a custom `wp-config-sample.php` it should be based on the original file, do NOT change the default charset from `UTF8`. @netweb
- I would like to point on two older tickets for GlotPress, which are, at least for me, still big issue, maybe some dev could look it: https://glotpress.trac.wordpress.org/ticket/228 and https://glotpress.trac.wordpress.org/ticket/338 @dimadin
A note for the Asia/Pacific meetings: @netweb, @japh, and @nao have decided to stop the Asia/Pacific meetings because of the lack of participants.
But please have in mind that the channel is still open for questions at any time.