Petya Raykovska 12:40 pm on July 15, 2015
Tags: weekly meeting notes ( 122 ), weekly meetings ( 408 )

Notes from the Polyglots chat on July 15th

Language variants: we can officially install language variants (formal, informal) from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: https://twitter.com/glueckpress/status/620866636384309249

All TE of localesLocale 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/ with language variants, please write a request on make/polyglots for the option to be added for 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/. Requests should include a slug (like `formal`), the english and native name of a variant.
Let’s document the different language variant usecases we have now, @alvarogois, @dimadin @gluekpress, could you describe your particular usecase and how you have handled things prior to this?
A quick reminder you can translate 4.3 stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in the development project now. The teams page shows the progress of locales on the 4.3 dev branch. This, as mentioned last week, will also give you the opportunity to test translations if you 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 running in your install
Themes and Plugins are coming to the repoWordPress Localization Repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details. (https://make.wordpress.org/polyglots/2015/07/14/translating-themes-and-plugins/), minimal requirements for TE to be added as per project validators:
- Description including projects and locales they’re taking care of
- 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/. name (unless limited by a technical issue)
- Other means of communication – email, twitter or other social account
- GravatarGravatar Is an acronym for Globally Recognized Avatar. It is the avatar system managed by WordPress.com, and used within the WordPress software. https://gravatar.com/.
Plugins and themes who do not want dotorg translations (language packs from translate.wordpress.org) can “opt-out.” The way for them to use their own translations, instead of ones from translate.wordpress.org is to… do nothing. Or, to keep doing what they’re currently doing. Translations that are shipped with themes/plugins take priority to language packs. WordPress will use them first and not download the language pack.
We’d love the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team’s input on these requirements – Taco to pint Rian for her opinion
The process for plugin/theme authors to request external validators for their plugins/themes to be added is described in https://make.wordpress.org/polyglots/handbook/rosetta/theme-plugin-directories/#requesting-new-translation-editors
Handbook updates: In august Petya will organise a handbook sprint for all handbook pages that have been reported to have issues. To help this process along, you can either report issues (slack or make/polyglots blog) or if you want to get involved more, request to be added as an editor to the handbook. The translation sprint will have tasks outlined for everyone who wants to join in to claim and work on.
Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. volunteers – with a lot more people joining the polyglots community, we need all the help we can get to help people with locale requests, questions, new validators orientation, documentation. If you’d be interested in helping out with any of the tasks below, please raise your hand in the comments:
- Answering people’s requests on the polyglots P2p2 "p2" is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog https://make.wordpress.org/polyglots/.
- Doing locale research for new locale requests – includes checking the request on the p2 and communicating with the person requesting the new locale, ensuring the ISO-3 codes are correct, adding information about how many people speak the language, double-checking plural forms, creating a ticket on the GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. track with all the information needed to add a new locale. (You will be trained by Petya)
- Monitoring feature requests/bug reports from polyglots and filing those as issues on the metaMeta 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. track

Cheers!

Petya

#weekly-meeting-notes, #weekly-meetings

Alvaro Gois dos Santos 2:37 pm on July 15, 2015

Thanks @petya. As to variant usecases, you want us to describe them here?
- Petya Raykovska 3:33 pm on July 15, 2015
  
  Yes, Alvaro, let’s get them all here and we can work out how to add them to the documentation after.
- Alvaro Gois dos Santos 9:07 am on July 20, 2015
  
  In pt_PT we have 3 language versions: default, which is formal (and old orthography), informal (also old orthography) and the new orthography formal, not yet in GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org..
  
  The Portuguese Language Orthographic Agreement of 1990 (AO90), the new orthography, is 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 by~~imposed to public institutions. There is still hope that this Agreement is rectified, if not disposed, at least to eliminate it’s most absurd flaws.
  
  A while back we had a 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 was no alternative for those who wanted or needed to have WordPress in accordance to AO90. On the other hand, it’s not fair either to automatically update an orthography (with a new WordPress version) for thousands of users without their consent. That’s why, in the meantime, we came up with a 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 solution for this: PT Variants.
  
  There’s also the issue of maintaining two versions (three, if we include informal, which has almost been an one-man-project), regarding consistency of terms and available resources. There’s software that can automatically convert old to new orthography, therefore, consistency can be kept in the current form. But the ideal way, IMO, would be to integrate variants in GlotPress in a side-by-side flow. Since only some of the stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. actually differ, it would be easier to maintain variants this way, using the default version as a fall-back for not yet translated or equal entries.
  - Samuel Sidler 1:08 pm on July 20, 2015
    
    I can see why that feature would be ideal for you. There aren’t very many localesLocale 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/ with variants, however. Speaking for the metaMeta 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. team, this isn’t something we’re going to spend time on as there are other, higher-priority things that we need to work on, which affect all (or most) locales.
    
    If someone from the Portuguese community wants to work on this for GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., I’m sure we would enable it on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. shortly after the feature was committed to GlotPress.
    - Alvaro Gois dos Santos 5:20 pm on August 24, 2015
      
      Thanks @samuelsidler (and excuse my late reply). I’ll see what @pereirinha has to say about this. I have no clue how this is/could be done.
      
      As to the variants discussion itself, I’m not so sure there aren’t many more variants. Probably they aren’t used because we had no infrastructure to address it until now.
      - Samuel Sidler 5:58 pm on August 24, 2015
        
        Perhaps, but I think we would have received requests for them over the years. 🙂
duytrung2121 12:27 pm on July 18, 2015

Hello Petya!
I see bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. support many language but without Vietnamese, So, can you add Vietnamese to bbPress project to translate? Thank you.
- Stephen Edgar 10:24 pm on July 19, 2015
  
  @duytrung2121, the upcoming bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. 2.6 stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are in `/dev` and already available and awaiting Vietnamese translation https://translate.wordpress.org/projects/bbpress/dev/vi/default
  
  Also the strings for the new 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. forums that use bbPress 2.6 are available for Vietnames here https://translate.wordpress.org/projects/meta/forums
Milan Dinić 10:37 am on July 21, 2015
Here is description of Serbian case as mentioned in the meeting.

Why we have this? Wikipedia says that “Serbian is practically the only European standard language with complete synchronic digraphia”. What that means is that both Cyrillic and Latin script are used, one letter from Cyrillic can be transliterated to Latin and vice versa, they are pronounced exactly the same, and that every Serbian speaker understands both.

Automatic transliteration from Cyrillic to Latin is practically 100% safe. Theoretically you can do that from Latin, but in reality that is not an option because you can use Western words like ‘WordPress’ or typos like c, č, ć (in Cyrillic quite different ц, ч, ћ) etc. That is one of the reasons why texts that should be available on both scripts (like translations) are made in Cyrillic and then automatically transliterated.

That is what plugin in /dist does, when turned on, simply replaces each letter from Cyrillic to Latin thus enabling Latin translation. It was proposed on mailing list (thats why Finnish guy made it, wasn’t that into WordPress then) more than seven years ago since otherwise we would have another 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/ to maintain which is completely same, only difference is writing system.

Since ditching of /dist is announced, I have thought about how to solve this. What shouldn’t be done is starting new locale and treating it as a separate language as it’s really not. Problems are that no human can manage this as there are many projects with same repetitive work done, confusion for users as to where to contribute, many unfinished or duplicated work in both sides, many wasted time and energy, etc.

I think that @nacin first mentioned idea that I am more toward it, especially when formal variants are introduced. That is doing work on 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/ that would make language pack for Latin from Cyrillic translations on the fly.

So how would this work:
- Create new code, lets name it sr_RS@Latin for now, that is only exposed through APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., so it would appear in dropdowns in WordPress but no separate locale site or GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. projects.
- Create language packs from GlotPress exports as usual. When sr_RS is processed, also create language packs for sr_RS@Latin from the same base using code like in our 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 to automatically transliterate. Save additional data about package if needed for API.
This way users could switch to that variant and stop shipping plugin with each release while it will still be untouched on older installations so we would have backward compatibility.

I know that this involves some work on metaMeta 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. side (I would gladly contribute but that part is private, I think), but is far less than having two localesLocale 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/, and it’s the only idea I can get right now. Other proposals are welcome.
Alvaro Gois dos Santos 3:04 pm on August 25, 2015

You understimate the power of WordPress ad-hoc translation… 😉

Translate WordPress

Weekly Meetings

Posting here

Notes from the Polyglots chat on July 15th

Translate WordPress

Weekly Meetings

Posting here

Share this: