Hi I would like to know answers to…

Welcome to the official blog of the translator team for the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. 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 translate WordPress to your language by logging in to the translation platform with your WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account and suggesting translations (more details).

Want to help in managing and validating translations? Get in touch with the existing language team and follow the glossaries & style guides if the team has them.

Don’t see your language? You can request support for it.

Weekly Meetings

We have meetings every week on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. in polyglots (the schedule is on the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. of this page). You are also welcome to ask questions on the same channel at any time!

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.

#polyglots

Mark Thomas Gazel 1:11 pm on October 25, 2013

At WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe we discussed what would tricker an update of the translations. @nacin said it would be when the translations of the stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. hit 100%. Zé wanted a deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors.-button too, though 🙂

So I’m thinking if I upgrade my danish version to US version 3.7 it will notice danish strings are ready and promt me to update those. Is that what we should expect?

I’ve done the above and it haven’t happened yet i might add.
- Ze Fontainhas 1:24 pm on October 25, 2013
  
  I suspect it may have to with the fact that there is no 3.7.x in Translate yet. Let’s wait for the Big Effing Branching Of Dev to 3.7.x to make sure. cc @nacin
  - Mark Thomas Gazel 1:44 pm on October 25, 2013
    
    Yes. Of course. That sounds very likely.
  - Naoko Takano 12:56 pm on October 27, 2013
    So, my current understanding is this:
    
    @pavelevap ‘s assumption #1 was correct (we built packages and users updated as usual)
    
    #2 – all users’s non-language files will be updated to 3.7.1 English package. This shouldn’t matter for localized version users since there won’t be any stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. change.
    
    readme.htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.
    
    wp-config-sample.php
    
    version.php
    
    are currently localized for Japanese package, but for minor releases these will be overwritten with EN – which is not ideal but “okay”. Functionalities of already-running install won’t be affected.
    
    We’ll still build packages (correct?) for minor releases but that’s for a snapshot purpose.
    
    Do you guys agree? Are we okay with this for now, or is there any need to create a new tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket reporting something that’s missing?
    I have a lot of question marks here 🙂 that’s because I’m still trying to comprehend the intended process. Let me know if any of you have any additional information to what I described!
    - pavelevap 1:03 pm on October 27, 2013
      
      Hi, problem is for example when there will be 3.7.1 release really early (tomorrow?) and there is no localized version for 3.7 yet (it will be ready in several days). So, how can users update to localized version when they will be automatically updated to 3.7.1 (English)?
      - Naoko Takano 1:14 pm on October 27, 2013
        
        I see. 3.7-ja is already out so your situation is different from ours. If users updated early to 3.7-en, they will have missing translations (same for 3.7.1). They will need to click “upgrade to localized version” to update the language files when your 3.7 package is ready.
        
        At this point, I think the best thing you can do is to let users know that’s what’s going to happen – similar to the manual upgrade process in the past.
    - pavelevap 1:20 pm on October 27, 2013
      
      Yes, but it is not good solution. Example: Localized version of 3.7 is not yet out. Some users can update to english version of 3.7. Now they will be automatically updated to 3.7.1. And some days later we will release localized 3.7 version and when user update manually, they will be downgraded to 3.7? It is a mess, I think developers should handle it somehow…
      - Naoko Takano 2:09 am on October 28, 2013
        
        So, according to The definitive guide to disabling auto updates in WordPress 3.7:
        
        And by default, translations (for themes, plugins, and eventually coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.) are updated automatically.
        
        Core translation files will not be automatically updated yet.
        
        @pavelevap – in your case, how about releasing 3.7.1 as soon as 3.7 localized version is out ? Do you have a lot of file changes that makes it hard to build 3.7.1 quickly?

Translate WordPress

Weekly Meetings

Posting here

Share this: