I would like to request commit access to the i18n 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. SVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. for /lv/ subfolder. My username is orvils
I am the validator See translation editor. for the Latvian language and I need to remove WPLANG from wp-config-sample.php so I can build the new version.
I am new to WordPress so if I am missing something, please point me to the right direction
In case you haven’t noticed, WordPress.org profile redesign is up. People can now get badges for their contributions. Here is an example for polyglots https://profiles.wordpress.org/vanillalounge/.
@vanillalounge I assume that you have access to the list of people currently contributing in make/polyglots. Could you please send it to someone in meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. (probably Ian Dunn), so that we can get those shiny new badges? 😀 Thanks
@nacin Could you please add the ‘en_AU’ translations for bbPress (/2.4.x branch) & BuddyPress ( /dev branch as there is no /1.8.x branch) .po & .mo files to i18n, similar to https://i18n.trac.wordpress.org/changeset/22193/
All of us here belong to the WordPress translating community and many know how frustrating the translating process is. WordPress has more than 3,300 strings A string is a translatable part of the software. A translation consists of a multitude of localized strings. (+500 for MultiSite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network.), it’s just too much.
I think that the translators community has to be more involved in the development process to reduce the strings ammount and improve it’s quality. WordPress trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. already have a few interesting ideas like:
- Consolidate string with same meaning but different wording (https://core.trac.wordpress.org/ticket/14039)
- Merge similar string (https://core.trac.wordpress.org/ticket/18218)
- Replace/Remove html code entities (https://core.trac.wordpress.org/ticket/7098#comment:10)
I would like to hear more ideas, based on your experience, how do you think we can improve the translating process and/or reduce the strings ammount? (you can add your trac tickets)