Hello there If you create a beta or…

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

Hello there.

If you create a betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. or RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. version in your local site, it automagically goes to the Beta & RC versions place when distributed. If you do the same with an alpha, it goes to the main page and take the main place. I’ve just tested it with 4.0-alpha.

Can you make the alphas go to the Beta & RC versions place too to avoid errors?

Thanks.

samuelsidler 1:57 pm on April 21, 2014

We don’t formerly ship alphas, just betas and RCs. That is, the “alpha” version number is just trunk prior to betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. and RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.. There is no need to package trunk versions, and, in fact, it might be confusing for you to package them given that coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. doesn’t ship them as actual releases.
- Sergey Biryukov 2:18 pm on April 21, 2014
  
  I think Rafael’s concern here is that it’s too easy to build an alpha version by mistake, and it replaces the stable version on the home page. This was an issue with some localized packages a few days ago.
  - Rafa Poveda 2:29 pm on April 21, 2014
    
    That’s the point. Thank you, Sergey :).
    
    I understand that there is no use in shipping alphas, and that we have the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.-tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party if we want to use them (and Vagrant –all hail Vagrant and VVV–).
    
    It’s only the concern that if it’s possible to have the alphas shipped to the beta place, it can avoid problems.
    
    Thanks again.
  - Stephen Edgar 10:39 pm on April 21, 2014
    
    Yes, as I noted here:
    
    b) Some error checking to the build tools so that the ‘WordPress Version’ number we enter in this form field explicitly matches the version listed in `/wp-includes/version.php` against the tag/project/branch/revision/HEAD we are compiling against.
    
    It would be nice if something like this could be adopted as part of the 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. build process.

Translate WordPress

Weekly Meetings

Posting here

Share this: