me again, A user reported a problem related…

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

Milan Dinić 1:39 pm on February 11, 2011

Maybe problem is that he has default keys (as in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. en_US version, ie. ‘put your unique phrase here’).
Sergey Biryukov 2:06 pm on February 11, 2011

https://core.trac.wordpress.org/ticket/14024

Milan is right about the potential reason, but actually it shouldn’t happen even with the default keys. I guess $wp_default_secret_key should also be translated in wp-includes/default-constants.php.
- Zé 2:45 pm on February 11, 2011
  
  That is correct. What we (pt) do is just leave it in English. It’s too easy to forget to translate.
  - Mattias Tengblad 3:23 pm on February 11, 2011
    
    So what you’re saying is that if we translate $wp_default_secret_key in wp-config-sample.php and setup-config.php we should also translate $wp_default_secret_key in default-constants.php? If so, where is this documented?
    - Sergey Biryukov 3:54 pm on February 11, 2011
      
      I’ve added a note on Files For Direct Translation.
      
      To be clear, there’s no $wp_default_secret_key in setup-config.php.
      
      When you translate it in default-constants.php, the stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in wp-content/languages/<your-localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/>.php is actually no longer necessary, however it’s still required to be there in order to build a localized package. So yes, currently it should be translated in all three places (wp-config-sample.php, <your-locale>.php, default-constants.php).
      - Da^MsT 3:59 pm on February 11, 2011
        
        Good to know, should have been pointed out earlier.
      - Cátia Kitahara 4:17 pm on February 11, 2011
        
        Wait, please. Just to clarify things. There are two possible solutions:
        1. Don’t translate the variable at wp-config-sample.php and don’t add the locale.php file
        2. Translate the variable at wp-config-sample.php and at default-constants.php and add the locale.php?
        Both solutions are admissible, is that correct?
      - Milan Dinić 4:20 pm on February 11, 2011
        
        If you don’t translate it in locale.php file and you did translate it before, this could affect existing installations.
      - Cátia Kitahara 4:24 pm on February 11, 2011
        
        so my best approach should be translate the default-constants.php from now on?
      - Sergey Biryukov 5:54 pm on February 11, 2011
        
        Yep, until a proper solution is found. Currently it’s more like a workaround.
      - Milan Dinić 4:24 pm on February 11, 2011
        
        I don’t like this. Instead of reducing direct translation and simplification of that, we are adding more files, and complicate already complicated situation.
        
        This is a clear sign of how i18nInternationalization Internationalization (sometimes shortened to I18N , meaning “I - eighteen letters -N”) is the process of planning and implementing products and services so that they can easily be adapted to specific local languages and cultures, a process called localization. This is the process of making software translatable. Information about Internationalization for developers can be found in the Developer’s handbooks. is getting in worse and worse position, how it is ignored, how there isn’t care to truly fix existing issues and to make improvements.
      - Mattias Tengblad 4:34 pm on February 11, 2011
        
        +1
        
        “Opened 8 months ago” (ticket mentioned above) kind of tells the story.
      - tsjogren 11:50 am on February 17, 2011
        
        Hi Mattias
        This is Torbjörn (Translating BP to Swedish).
        I have the same problem reports from swedish users.
        1. When does the problem occur? What WP versions?
        2. What is the workaround? renaming sv_se.php did help.
        3. Is this fixed in future versions (WP 3.1)
        Please advice so i can give the users the correct answers.
        
        I did a WP 3.0.1 install, upgraded to 3.0.5 and installed BP with no problems…
      - Mattias Tengblad 2:26 pm on February 17, 2011
        
        1. From 3.0 and up
        2. Yup renaming or deleting sv_se.php will work. Tell the users to update their secure keys in wp-config manually.
        3. Yes, the workaround mentioned above is already applied in trunk (3.1).

Translate WordPress

Weekly Meetings

Posting here

Share this: