WordPress.org

Translate WordPress

Welcome to the official blog of the translators team for the WordPress open source project.

This is where we discuss all things related to translating WordPress. Follow our progress for general updates, status reports, and debates.

We’d love for you to help out.

Translate WordPress

You can help translating WordPress to your language at any time. Just log in to the translation platform with your WordPress.org account, and suggest translations. If you want to help in managing and validating translations, please make sure to get in touch with the existing language team first.

Don’t see your language?

Request support for it by following this guide. We’ll have you up and running in no time.

Weekly Meetings

We a weekly meeting on Slack in #polyglots, Wednesdays at 10:00 UTC. If you have any questions, bring them to the weekly chat!

Posting here

In order to post to this site, you will need to log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow our tag policy when posting.

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • petergatuna 12:02 am on May 29, 2015 Permalink |
    petergatuna  

    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.

     
    • Samuel Sidler 12:57 pm on May 29, 2015 Permalink | Log in to Reply

      Hello @petergatuna.

      You can give your translation editor on your team page.

      It looks like @mrfroasty is the translation editor for Kiswahili / Swahili and can approve translations.

    • petergatuna 8:53 pm on May 29, 2015 Permalink | Log in to Reply

      @samuel I have tried to contact @mrfroasty but it seems he is not active at moment since his wp 3.0.5 translation I am stuck and not where to start.

    • mrfroasty 8:24 am on May 30, 2015 Permalink | Log in to Reply

      Sorry guys I had a bit of issues to login.
      Well its true I have not made any releases since somewhere 3x versions.I did somewhere attempted to recover and translate 4.x but it was never completed for use in public domains….Definately we can use some extra hands to get WordPress SW versions.

      How can I help ?

  • Caspar 3:18 pm on May 27, 2015 Permalink |
    glueckpress • de.wordpress.org editor
    Tags:   

    As a follow-up on the Development Project testing idea, and after @ocean90 kindly clarified again what that is all about, here’s the copy we’ve come up with so far:

    Development

    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.

    Translators: Please allow a reasonable time frame for validation of newly translated strings. You can always ping a validator from your team in the #polyglots slack channel.

    This is what it would look like on https://translate.wordpress.org/projects/wp/dev:

    Screenshot of translate.wordpress.org/projects/wp/dev with proposed copy

     
  • Petya Raykovska 7:53 am on May 27, 2015 Permalink |
    petya • bg.wordpress.org editor
    Tags:   

    Agenda for the Polyglots chat on May 27th 

    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!

    Cheers,

    Petya

     
  • Petya Raykovska 7:08 am on May 27, 2015 Permalink |
    petya • bg.wordpress.org editor
    Tags: , documentation l10n,   

    Translating documentation 

    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.

    Cheers!
    Petya

     
    • Caspar 7:19 am on May 27, 2015 Permalink | Log in to Reply

      Regarding version control and collaboration, the easiest thing coming to my mind is GitHub. The WordPress Book has been written on GitHub. Why not the handbooks?

    • Torsten Landsiedel 7:52 am on May 27, 2015 Permalink | Log in to Reply

      Here is the plugin I was talking about:
      https://wordpress.org/plugins/email-post-changes/

      • Samuel Sidler 5:20 pm on May 27, 2015 Permalink | Log in to Reply

        We already use this on a number of dotorg sites to monitor changes. I don’t think it’s a viable solution to translating docs, however.

    • Xavier Borderie 7:55 am on May 27, 2015 Permalink | Log in to Reply

      So glad this conversation is finally happening!

      Versioning is one thing, but I think a changelog would be very useful too, at least for the main changes. Not everyone wants to spend time comparing text changes, even more so when the change are spread among many pages (and several pages have no changes — frustrating).

      In that, I’m not sure using WordPress’ versioning is optimal in our case. Git is a solution for diff-ing pages that would help a lot, and which, in addition to a changelog, would form a great and helpful combo.

    • Andrew Nacin 6:32 pm on May 27, 2015 Permalink | Log in to Reply

      We should solve this problem by eating our dogfood. I feel very strongly about that. If we can’t make WordPress excel when it comes to managing and translating content, I’m not sure why we’re all here.

  • Jenia 7:20 am on May 26, 2015 Permalink |
    jenia
    Tags:   

    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.

     
    • Marko Heijnen 11:00 am on May 26, 2015 Permalink | Log in to Reply

      Currently it’s a hack to me. This information (words but also ltr) should not be in GlotPress but should be data inside WordPress. Worse case is that translate.wordpress.org has a little plugin that includes these entries based on the information inside GlotPress.

    • akerbeltzalba 11:11 am on May 26, 2015 Permalink | Log in to Reply

      Agree with Marko, it should not be stuck in with the translation strings. In my experience, this almost always goes wrong unless you have a tiny number of very good translators handling the entire project. In most cases, it will be a well meaning volunteer who looks at the source, thinks ‘easy’ and translates but does not check the comment – which you mostly look at when the source is confusing.

    • Dominik Schilling (ocean90) 3:37 pm on May 26, 2015 Permalink | Log in to Reply

      Thanks for the hint @jenia. I rejected the wrong strings for these locales:

      Azerbaijani - default - az
      Bulgarian - default - bg
      Danish - default - da
      Greek - default - el
      Peruvian Spanish - default - es-pe
      Estonian - default - et
      Persian - default - fa
      Kannada - default - kn
      Kirghiz - default - ky
      Malay - default - ms
      Sinhala - default - si
      Albanian - default - sq
      Swahili - default - sw
      Thai - default - th
      Uighur - default - ug
      Vietnamese - default - vi
      Nepali - default - ne
      Welsh - default - cy
      Uzbek - default - uz
      Macedonian - default - mk
      Croatian - default - hr
      Urdu - default - ur
      Persian (Afghanistan) - default - fa-af
      Scottish Gaelic - default - gd
      Icelandic - default - is
      Telugu - default - te
      Ossetic - default - os
      Corsican - default - co
      Lao - default - lo
      German (Formal) - formal - de
      Tajik - default - tg
      Tagalog - default - tl
      Hazaragi - default - haz
      South Azerbaijani - default - azb
      Afrikaans - default - af
      Swiss German (Formal) - formal - gsw
      Pashto - default - ps
      Rohingya - default - rhg
      German (Switzerland) - default - de-ch
      Algerian Arabic - default - arq
      Occitan - default - oci
      

      If you are an editor of one of the locales please read the translator comment again:

      translators: If your word count is based on single characters (East Asian characters), enter ‘characters’. Otherwise, enter ‘words’. Do not translate into your own language. translators: If your word count is based on single characters (East Asian characters), enter ‘characters’. Otherwise, enter ‘words’. Do not translate into your own language.

    • Sergey Biryukov 10:07 pm on May 26, 2015 Permalink | Log in to Reply

      Introduced in [19966] and [20859].

    • kOoLiNuS 10:22 am on May 27, 2015 Permalink | Log in to Reply

      I have proposed “parole” for Italian – it

    • Dominik Schilling (ocean90) 4:37 pm on May 27, 2015 Permalink | Log in to Reply

      @muhsinmushviq and @Gwgan please read this. I have rejected your strings again.

    • Gwgan 7:18 pm on May 27, 2015 Permalink | Log in to Reply

      Thanks for the heads-up. Corrected.

    • Dominik Schilling (ocean90) 12:17 pm on May 29, 2015 Permalink | Log in to Reply

      @haroonyousuf please read this. I have rejected your string.

    • Seisuke Kuraishi (tenpura) 3:16 am on May 30, 2015 Permalink | Log in to Reply

      At first, I thought storing options into a translation file was a cool idea, but soon I realized that was a bad implementation. Translations are constantly in flux, and not suitable as a place to save the important options. They are unstable and unreliable.
      To solve this problem, WP Multibyte Patch has a function to force character counting, so that Japanese blogs could always be locked in the “characters” wordcount mode even if the Japanese translation file is not available. In my opinion, language specific options and functionality should be decoupled from translations.

  • mbigul 11:55 am on May 23, 2015 Permalink |
    mbigul • ml.wordpress.org editor
    Tags: Malayalam, Malayalam Translation,   

    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

    https://profiles.wordpress.org/nejwrks – Nebu

    https://profiles.wordpress.org/mbigul — Myself

    Thanks in Advance

    With Regards

    Bigul

     
  • Petya Raykovska 12:04 pm on May 20, 2015 Permalink |
    petya • bg.wordpress.org editor
    Tags:   

    Notes from the Polyglots chat on May 20th 

    Locale stats:

    46 locales are up to date.

    5 locales are 100% translated but not yet released for 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”

    Localizing Documentation

    • 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.

    Thanks everyone!

    Petya

     
  • Petya Raykovska 8:11 am on May 20, 2015 Permalink |
    petya • bg.wordpress.org editor
    Tags:   

    Agenda for the Polyglots chat on May 20th 

    Dear Polyglots,

    Here’s a short agenda for the Polyglots chat today:

    If you have anything else to add to the agenda, please feel free to add it in the comments.

    Cheers!
    Petya

     
  • Dion Hulse 6:53 am on May 20, 2015 Permalink |
    dd32 • en-au.wordpress.org editor • test.wordpress.org editor  

    Hi everyone!

    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:

    If you spot any bugs, please either report it here, or on meta.trac under the Theme Directory component (or the Plugins Directory component).

     
    • Stephen Edgar 7:26 am on May 20, 2015 Permalink | Log in to Reply

      This is incredibly cool, thanks 😊

    • Kazama 7:38 am on May 20, 2015 Permalink | Log in to Reply

      Both themes and plugins page look great. 😛

    • Petya Raykovska 8:00 am on May 20, 2015 Permalink | Log in to Reply

      Thank you, Dion! :)

    • Remkus de Vries 8:42 am on May 20, 2015 Permalink | Log in to Reply

      Very cool indeed, thanks Dion!

    • Rami Yushuvaev 8:50 am on May 20, 2015 Permalink | Log in to Reply

      Very nice but it has RTL issues.

      https://he.wordpress.org/themes/

    • codeinwp 8:14 pm on May 20, 2015 Permalink | Log in to Reply

      I am curious how can this be integrated in themes/plugins, like will be some language specific themes/plugins displayed before others ?

      For example a theme translated in Romanian compared with other that is not translated.

      How this will affect us as plugin/themes authors in the long run and what we need to do to help :)

      • Dion Hulse 1:24 am on May 21, 2015 Permalink | Log in to Reply

        Once we’ve got WordPress.org-hosted translations for Plugins & Themes rolled out, I would expect we’ll start tweaking our search & view algorithms to favour a plugin/theme which is translated into their language – keeping in mind that there are a lot of WordPress users out there who may not be able to read English (or at least, be comfortable reading it).

        Hopefully one day not-too-far-away every plugin & theme will be translated into every language, so this isn’t even an issue :)

    • Mayo Moriyama 3:05 pm on May 21, 2015 Permalink | Log in to Reply

      Thank you Dion! We really waited for that day. We can explain about commercial theme and uploading theme in the official WordPress.org site in our language! Thank you so much!!!

  • Alvaro Gois dos Santos 8:43 pm on May 19, 2015 Permalink |
    alvarogois
    Tags: AO90, ISO, Portuguese Language Orthographic Agreement, , , variants   

    Hi Polyglots,

    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?

    Thanks.

     
    • TacoVerdo 1:48 pm on May 20, 2015 Permalink | Log in to Reply

      It sounds like this is quite like the situation the Germans have with default vs formal language. They have two projects on translate.wordpress.org.

      Could that be a solution for you as well?

    • Alvaro Gois dos Santos 2:42 pm on May 20, 2015 Permalink | Log in to Reply

      Hi Taco,

      Thanks for replying.

      As a matter of fact, we already have two similar projects on translate.wordpress.org, for formal (default) and informal Portuguese.

      But this isn’t enough, since it’s only an infrastructure for collab translation management, not actually a way for everyone to add the alternative version to WordPress.

      Unless there’s an easy way to get those alternatve language files from the repository. Is there?

      I came across a plugin (WPTB) to change WordPress language from within the admin, but, as WordPress core itself already does, it only loads the default language packs. In a situation were we have no variants, no ISO codes that identify the alternative language files, we cannot load the pack from the repo.

    • Torsten Landsiedel 10:40 am on May 21, 2015 Permalink | Log in to Reply

      Here is the trac ticket for that:
      https://core.trac.wordpress.org/ticket/28303

      The whole German community is hoping for a solution!

      @ocean90: You said, we have to think about a core solution. Is someone working on that already? Can we help?

      • Alvaro Gois dos Santos 10:45 am on May 21, 2015 Permalink | Log in to Reply

        Do you have any experience with a solution that overrides the default packages, but using the same locale with packages on an alternative repo?

        We’ll probably try a solution like that for the Portuguese Orthographic Agreement version. It’s not perfect but can be accessible, if it works…

    • Angelika Reisiger 7:12 pm on May 21, 2015 Permalink | Log in to Reply

      This is a huge problem for a lot of countries. After a short research I found this wikipedia article:
      https://de.wikipedia.org/wiki/H%C3%B6flichkeitsform#Die_H.C3.B6flichkeitsform_in_anderen_Sprachen

      They don’t list all countries with formal and informal language, but here are a few:
      France, Finland, Germany, Portugal, Hungary, Luxembourg, Serbian, Montenegro, Bosnia, Herzegovina, Croatia, Russia, Nederlands, Poland, Japan, China

      You could also read:
      https://en.wikipedia.org/wiki/Honorific

      All these countries only can use an informal (and rude) address to the visitors of their WordPress Website. Even, if they install the formal language – after the next wp-update will override the informal language.

      Please, take this problem seriously, cause it is a serious problem for all the WordPress Admins in such countries. Can we help?

    • Alvaro Gois dos Santos 9:04 pm on May 21, 2015 Permalink | Log in to Reply

      As to the formal vs. informal, that’s also a problem for us in Portugal, as you mention, though we have the opposite situation, our default language is formal and we have an informal GlotPress branch which is not accessible for the average user.

      What we’re trying to achieve, using a plugin, is a way to override the default language files for new ones, managed by the Portuguese Community. Possibly in an alternative GlotPress or Github repo.

      Why? Because there’re no variants in the Portuguese language (Portugal), hence we’ve to use the same ISO code so that other translations don’t break.

      I’ll post our findings here, Angelika.

    • Alvaro Gois dos Santos 10:41 am on May 25, 2015 Permalink | Log in to Reply

      @tacoverdo, @zodiac1978, @la-geek: update on language variants. We’re now testing a plugin solution that will enable local communities to ship language variants with their version of the plugin. So far it seems the best way to have a community driven solution that takes advantage of already existing translations, without imposing any variant.

      As to the specifity of Portuguese language translations, our goal is to avoid dispersing translation resources.

      I’ll be updating this soon 😉

      • Torsten Landsiedel 10:53 am on May 25, 2015 Permalink | Log in to Reply

        I would really prefer a core solution (as @nacin promised me @ WordCamp Europe in Sofia one year ago 😉 – but a community driven plugin workaround would be great until this is fixed. Please keep us updated! If we can help / beta-test, please ping me/us as well!

        • Alvaro Gois dos Santos 10:58 am on May 25, 2015 Permalink | Log in to Reply

          Thanks! I would have to agree with you as to a core solution, truth is we have an immediate demand.

          And a core solution won’t be that easy, I suppose, due to the ISO codes regarding locales and the possibility of disrupting plugin and theme translations.

        • Andrew Nacin 2:13 am on May 27, 2015 Permalink | Log in to Reply

          It’ll happen! I know @ocean90 has been looking into it, and I have some ideas. There’s some movement happening now on user locales (https://core.trac.wordpress.org/ticket/29783) and I suspect these will both move forward together in some way.

          It isn’t too hard to do, we just have to change how we key things and introduce a slight tweak to how we store locales in the DB and on the filesystem. So something like pt_PT_informal. Not a hard problem and won’t disrupt anything. Just takes time.

    • Angelika Reisiger 3:55 pm on May 26, 2015 Permalink | Log in to Reply

      Thanks @alvarogois for the heads up! Yeah, a core solution would be the best one – of course. But your efforts to build a plugin are really great and very appreciated. Do you need any help with testing in other language – here german formal?

      • Alvaro Gois dos Santos 4:17 pm on May 26, 2015 Permalink | Log in to Reply

        Hi @la-geek. We already have a plugin in test mode :)

        We’re facing some issues with server memory.

        I believe we’ll have a version for beta testing soon.

        It’s not the perfect solution but can be a temporary one.

        In it’s current form, the plugin installs two variants of the Portuguese (pt_PT) language, namely, Portuguese Orthographic Agreement (1990) and Portuguese Informal. After plugin installation, user goes to options > general and has two more options below the site language, one for frontend and the other for backend. It’ll only work if the exact same locale is defined, in this case Portuguese (Portugal), because the plugin overrides the locale’s default, admin and network admin language files. My guess is that this is the only way plugins’ and themes’ translations won’t break.

        To make it work with other languages – if we maintain the current architecture –, it has to be edited to work with your locale.

        I thought of a larger scale infrastructure, one where you could have a group of WordPress language variants. But I sense a lot of issues.

        In Portugal we have a small community, relatively close to one another. We almost know everyone who’s involved translating WordPress. But in other countries is not like that. It would be impossible to validate the accuracy of variants in an 100% open environment. I’m not sure how to do it.

        As soon as we get to beta I’ll post it here for everyone who wants to give it a try (and help making it better 😉 ) .

    • Alvaro Gois dos Santos 12:38 pm on May 28, 2015 Permalink | Log in to Reply

      Update: we now have a working plugin we called PT Variants available from WordPress.org (way faster than we thought…) and GitHub.

      It installs two variants of the Portuguese (pt_PT) language, namely, Portuguese Orthographic Agreement (1990) and Portuguese Informal. After plugin installation, user goes to options > general and has two more options below the site language, one for frontend and the other for backend. It’ll only work if the exact same locale is defined, in this case Portuguese (Portugal), because the plugin overrides the locale’s default, admin and network admin language files.

      To make it work with other languages it has to be edited to work with your locale.

  • Siobhan Bamber (siobhyb) 9:27 pm on May 17, 2015 Permalink |
    siobhyb  

    Could you please add Welsh (cy) to the WordPress for iOS project?

    https://translate.wordpress.org/projects/apps/ios

     
  • Kouteki 11:15 am on May 17, 2015 Permalink |
    Kouteki  

    If I notice an a typo in the original text, how do go about reporting it?

     
  • Dominik Schilling (ocean90) 10:37 pm on May 14, 2015 Permalink |
    ocean90 • de.wordpress.org editor
    Tags:   

    Notes from the Polyglots chat on May 13th & 14th 

    Logs: https://wordpress.slack.com/archives/polyglots/p1431511282000095

     

    Local Stats
    Skipped.

     

    Translation Project for WordPress 4.3
    (Post: https://make.wordpress.org/polyglots/2015/05/12/discussion-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.

     

    Open discussion

    • 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.

     
    • Stephen Edgar 11:19 pm on May 14, 2015 Permalink | Log in to Reply

      A note on the Asia Pacific chat participation level, anecdotally I think this is because of daylight savings time, with the current alignment of time zones this makes the Europe, South America, Africa and West Asia chat is more accessible, that is definitely the case for @japh and I as it is 8pm local time, switch to DST and it’s 10pm local time and not as accessible.

      I’m more than happy to revisit adding the Asia Pacific chat back once DST changes occur again ~5-6 months from now, I’m also more than happy to kick of the chat again now or at any time in the immediate future if the level of participation would be more than just one or two people.

    • Stephen Edgar 11:29 pm on May 14, 2015 Permalink | Log in to Reply

      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

      Further to this I had a discussion with Dion in #core-i18n about this and about collations.

      A quick summary from @dd32:

      > If the site uses a utf8mb4 charset, and they have a utf8_* character set set, it’ll be overridden to utf8mb4_unicode_ci.

      > If the site uses utf8 and they set utf8mb4_swedish_ci things will break

      > If the site uses utf8mb4 and they set utf8mb4_swedish_ci, then.. it’ll use utf8mb4_swedish_ci.

      > “In other words, customising those values in the default file is really a bad idea. Site admins can do that sure, but it should default to our defaults.”

      Currently @danielck is using the following for Finnish:

      > Netweb: “So after the various chats last night it looks like we have the Finish locale leaving the charset as UTF8 but defining the collation as utf8_swedish_ci for the Finish locale, will that explode?

      > dd32 “I don’t know the answer here.”

      I need to summarise up all of what we chatted about and create a ticket in Trac so that we can investigate what currently works and what does not, from there we can then work out what we need to do to make various charsets and collations work well for i18n locales.

      You can check out the full discussion here:
      https://wordpress.slack.com/archives/core-i18n/p1431559485000017

  • patilswapnilv 11:50 am on May 14, 2015 Permalink |
    patilswapnilv  

    Hey,
    I could see a lot of transactions waiting at https://translate.wordpress.org/languages/mr
    Is there any Review process which is pending for these translations ?If yes, How can I help?I suggested some new translations; but could know why there are around 1312+ waiting translations. Please let me know how I can help

    @vinod-dalvi @yossarianc @jaays @developerpaddy

     
    • YossarianC 9:02 am on May 15, 2015 Permalink | Log in to Reply

      Hi,
      Thanks for writing.
      A reasonable number have been reviewed, yesterday. More will be reviewed each fortnight.
      Do you want to contribute as a Translator for MR? If yes, please send a request via polyglot. You will be added accordingly thereafter.
      Regards.

    • svd02 3:35 pm on May 16, 2015 Permalink | Log in to Reply

      i did that translation. but no response from moderator. rest of the things i will do in near future. you can join me. no problem.

    • patilswapnilv 4:18 pm on May 16, 2015 Permalink | Log in to Reply

      @YossarianC by contribution do you mean as a moderator?

      Because I am already translating. @svd02 is also doing a great job with it. I will be translating more as much as possible.

      Here my concern is after translation it needs to be moderated, so the efforts taken for translating are useful. And it is going slow. We either need more people to look after it or the 4 moderators have been busy lately.

  • Petya Raykovska 8:43 am on May 13, 2015 Permalink |
    petya • bg.wordpress.org editor
    Tags:   

    Agenda for the Polyglots chats on May 13th, May 14th 

    Hey everyone,

    Quick agenda for today’s chat:

    • Local Stats
    • Translation Project for WordPress 4.3 – we need to have a decision by the end of the Asia/Pacific chat tomorrow.
    • Filling in our translation editor profiles
    • Open discussion

    See you there!

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel