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 have two weekly meetings on Slack in #polyglots. Wednesdays at 10:00 UTC and Thursdays at 04: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

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

    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 Raykovska 8:11 am on May 20, 2015 Permalink |
    petya • bg.wordpress.org editor

    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.


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


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


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

      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:

      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:

      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.

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

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


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

    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

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

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


    Local Stats


    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:

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

    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

      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.

    • 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

    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!

  • Dominik Schilling (ocean90) 8:27 pm on May 12, 2015 Permalink |
    ocean90 • de.wordpress.org editor
    Tags: 4.3,   

    Discussion: Translation Project for WordPress 4.3 

    Hey, this a follow-up to our latest week chat and summarizes some points regards an early project for WordPress 4.3 on translate.wordpress.org. See also the meetings notes from last week.

    For the upcoming release I would like to test if it would be a good idea to have projects for the next WordPress version as soon as possible. Currently the Development project represents the latest stable release (WordPress 4.2.x) and not the version which is in active development.

    Here are some pros and cons, commented by me:


    • You don’t have to wait until one month before a release to start translating the new version.
    • We can build language packs for alpha/beta versions too, so you could test strings “live”.
      This would be useful for reporting bugs for too long strings, typos, missing contexts or comments, etc.


    • We have a dev project and a “stable” project which could confuse new translators.
      Each project has an “active” status. The development project can marked as non-active so it won’t be visible directly. We can/should also add a banner/warning to the project, which explains the state of this project/strings.
    • If a string gets changed a lot you’ll end up on translating over and over again variants of the same string.
      That’s true, but this is a decision which has to be made by each translator and/or team. We won’t force anyone to translate/validate the strings. But have in mind, that GlotPress now can detect minor changes so you don’t have to retranslate the whole string.

    I don’t want to make this decision by my own, it should be a decision made by the team. So please use the comment section below and/or the weekly chat (Wednesday @ 10:00 UTC / Thursday @ 04:00 UTC) to raise your concerns and if you think we should try this.
    As mentioned above, it would be a test which we can cancel at any time.

    • Sergey Biryukov 9:40 pm on May 12, 2015 Permalink | Log in to Reply

      Having strings from trunk in the Development project as soon as possible sounds great. I used to build localized beta and RC packages in the past, I think it’s a good way to make sure there are no unnoticed i18n issues.

    • savione 7:07 am on May 13, 2015 Permalink | Log in to Reply

      Possibility to build language packs for alpha/beta version also means that more people can test translations because it would be easier to set up. I think it’s worth a try.
      Two questions: If I change current string in a dev project, would that string be changed in “stable” project as well? Would that cause an update of stable projects language pack?

    • Caspar 9:39 am on May 13, 2015 Permalink | Log in to Reply

      We have a dev project and a “stable” project which could confuse new translators.

      In conjunction with the proposed banner/warning, this shouldn’t be an issue. UI ftw.

      Generally, separate dev and stable versions certainly will make the translation workflow easier, so hooray!

  • hienzquynh 6:04 am on May 11, 2015 Permalink |
    Tags: , , ,   

    Dear admin,

    I finished translating the entire bbPress 2.5.x Vietnamese language pack in a .PO file. Now that I would like to upload, it seems as though the option to uploading is not available for me as a contributor. Can you either let me join the bbPress Validator team (temporarily) and / or let me know the assigned Vietnamese validator to whom I can send the .PO file to? Entering the translations one string at a time online (more than 1,000 strings) is not practical nor doable for me since I am on and off the Net very frequently due to my job. Since there is currently no bbPress Vietnamese translation, this .PO file is perfect to upload all at once.

    Thank you so much!

    P.S: I am thinking of translating other components such as BuddyPress or WordPress and many others in due time. Will I need to put out requests similar to this request every time when I need help in uploading the .PO to the appropriate component(s)?

  • fgienr 8:37 pm on May 7, 2015 Permalink |
    fgienr • fr-ca.wordpress.org editor
    Tags: fr_CA,   

    There is no validator for the French (Canada) project. I would like to get this status in Rosetta, for the work to get done.

  • Dominik Schilling (ocean90) 9:16 am on May 7, 2015 Permalink |
    ocean90 • de.wordpress.org editor

    Notes from the Polyglots chat on May 6th & 7th 

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

    Locale stats
    We have 48 locales up to date and 3 are behind one minor version. One new locale for Occitan.

    Tech stats
    The meta i18n team had a meeting yesterday, the logs are at https://wordpress.slack.com/archives/meta-i18n/p1430823944001111
    Topics were the status of GlotPress and the localized sites, like theme and plugin directory.
    We have changed the project structure on translate.wordpress.org. Rosetta is now a sub project of WordPress.org aka “Meta”, see https://translate.wordpress.org/projects/meta. There are also two new projects, WordPress Plugin Directory and Forums. Forums is the theme for the new forums with bbPress 2.x, the old Forums project is now deprecated.
    The localized theme directory will probably go live first.

    GlotPress changes
    On import, GlotPress detects now when a string has minor changes and keeps the original translations. Existing translations will be marked as fuzzy. Which means if a string gets a period you don’t have to re-translate the whole string. Just watch the fuzzy column, adjust the string and approve again.
    Second feature: Cross project translations matching.
    When a new string is added, and the exact same string (singular/plural/context) exists (and is active) in other projects for the same translation set (locale + slug), then current translations will be copied to the new string. Or: When a new translation is added (as current) to a string in a project, and the exact same string (singular/plural/context) exists (and is active) in other projects for the same translation set (locale + slug), then the translation will be added as current there too.

    New locales page on translate.wordpress.org
    Some feedback:
    @zodiac1978: “maybe adding a tooltip could add some explanation what the number means”
    @igorkol: “persons involved cannot be seen/clicked on?”
    @igorkol: “although, it is not clear instantly what is represents. especially because there is so many 100% translations”

    There are some to-dos, if you want to get involved please take a look at https://meta.trac.wordpress.org/ticket/994#comment:5 and join #meta-i18n on Slack.

    Upcoming releases
    In the next few days a new version for WordPress 4.2 will be released to fix some bugs. So please prepare your locales as always.
    As a reminder: You don’t need to create tags in SVN, branches are fine too (https://make.wordpress.org/polyglots/2015/04/28/i-think-that-with-so-many-minor-versions/)

    WordPress 4.3:
    I would like to create a project for 4.3 on translate.wordpress.org, even it’s still in alpha.


    • You don’t have to wait until one month before a release
    • We can build language packs for alpha version, you can test strings “live”
    • Core can do string changes faster


    • We have a dev project and “stable” project which could confuse new translators.
    • If a string gets changed a lot you’ll end up on translating over and over again variants of the same string

    I’ll do an extra post for this and we’ll discuss this again in next week’s meeting.

  • nizari 5:37 am on May 7, 2015 Permalink |
    Tags: WordPress Amazigh language   

    Is it possible to translate the Amazigh language? If Tatnna will be the first version Tamazight a precedent
    I translation from French, Arabic or Spanish to Tamazight. I just need help in the beginning because I novice. Thank you

  • Dominik Schilling (ocean90) 3:01 am on May 7, 2015 Permalink |
    ocean90 • de.wordpress.org editor
    Tags: ,   

    WordPress 4.2.2 has been released It is a… 

    WordPress 4.2.2 has been released. It is a security and maintenance release. There are no string changes.

    In order to benefit from the automated release process it could be possible that you have to prepare your locale first.

    Translations must be at 100%

    (This includes wp/dev, wp/dev/admin and wp/dev/admin/network.)
    Currently 49 locales are at 100%.

    Update version in readme.html

    • If you have custom changes on i18n.svn.wordpress.org and you are using branches/4.2 to release your package you only have to change the version in readme.html.
    • If you’re using tags/4.2(.1) you have to create a new tag for 4.2.2 first. It’s just a copy of tags/4.2(.1) or trunk and the version change to readme.html.
    • If you have tags/4.2(.1) and branches/4.2, but no tags/4.2.2 the build will use branches/4.2.

    Also released: 4.1.5, 4.0.5, 3.9.6, 3.8.8 and 3.7.8.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc