Here’s the follow-up on the survey regarding external communication tools. Data can be downloaded in PDF or xls format.
As a follow up to Contributor Day at WordCamp London, I’d like to ask 3 simple questions to all the polyglot teams here. Answering shouldn’t take longer than a couple of minutes and would be greatly appreciated.
TL;DR: I’m asking to evaluate whether what has been on my mind lately addresses a real need, or an edge case.
During Contributor Day at WordCamp London I meant to contribute wireframes for commhub. Looking at what we have so far, though, questions rose (at least for me) whether our current MVP feature set really focusses the most pressing needs of communities we’re building commhub for. At their core those communities imo can be seen as language-centered, so there is an interrelationship/overlap with polyglots. (See mind-map from Contributor Day.)
Thanks for your help!
Where are you taking the revision numbers from? I assume core.trac.wordpress.org isn’t the right place?
Is there any chance of getting a P2 for a locale?
Since forums translations are now taken from GlotPress, are the rosetta/ directories in locales’ SVN repos now redundant? To be precise, I mean the support-forum.po and support-forum.po files. (And if so, can the entire directories be removed?)
Please deploy the Polish translation of Rosetta forums.
Locale site changes being in progress, can I request some kind of menu bar synchronization between locale sites and locale forums, so that the menu is the same on the forums? At https://pl.wordpress.org/ we have a link to the forums in the main menu, but if you click it, you get an entirely new main menu, provided by bbPress. Can this be changed somehow?
Where are WordPress Forums translations taken from? SVN or GlotPress?
Quick question. Where should I keep a log of the changes made in translation? I thought of keeping a handbook with some translation rules on the Rosetta site.
A question about the main https://wordpress.org/ website – how is a user supposed to know there are localized versions of WP? There don’t seem to be any links. For some reason, I get a yellow box suggesting it’s available in German but German is way below Gaelic (the order I’m using is gd, en, de) in my preferred languages setting in Firefox and even if, not everyone who might want WP in language X uses a browser in language X. Am I missing something or is that just an oversight?
There’s a bug on the tag policy page – there are two rows with the “request” tag, though one links to “announcements”. 🙂
Since this blog serves as both a place for announcements and discussion, it’s quite hard to filter out the /really/ important messages, such as new version notifications. Because of that, I have an idea – maybe a new blog could be created, e.g. wppolyglots-announcements (though that is a really long name), on which only important announcements from the core developer team would be posted?
Editors of Rosetta sites can now control who the validators are for their language. GlotPress will use these permissions across all projects on translate.wordpress.org. You no longer need to post validator requests here.
Validators are users of that locale’s Rosetta site having the role of Editor, Author, or Contributor. You can also use the new role of Validator (otherwise equivalent to Subscriber). I’ve ported over all existing validators.
Editors can now add and promote users, as well as edit the theme’s screenshots and navigation menu (Themes > Custom Header and Menus, see previous post). All administrators are now editors instead.
With this change, we’re also dropping support for locales that do not have a Rosetta site. This applies to 21 languages*, all of which are inactive anyway. GlotPress will no longer function properly for these languages, and a future cleanup will likely remove them from SVN and elsewhere.
(* – Affected languages are: br, gd, kk, ku, lt, mn, no, pa_IN, zh, az, bn_BD, en_GB, es_CO, fo, haw_US, is_IS, kn, ky_KY, lb_LU, ta_IN, ur.)
We’re working on some Rosetta updates. Here’s the first two: Menus and Screenshots.
You no longer need to request a deploy for Rosetta screenshots. Instead, you should now use the Custom Header feature under Appearance. The size is limited to 466px by 303px, the same width we use on WordPress.org.
You no longer need to use the Rosetta menu editor under Tools. You can now go to the Menus feature under Appearance. You are limited to top-level menu items, as before.
Screenshots needn’t be committed to svn anymore as they won’t be deployed. I’ll be phasing out the old menus system soon. It took me three minutes to switch over pt_PT and I don’t even understand Portuguese, so it’s quite easy.
This is totaaly weird, what is the reason of tags (3.x, 3.1.x, 3.2.x) in GlotPress if the translations are not copied along?
I’m using my tool, localize to test the translations, and when I tried to switch to 3.2.x, it downloaded an empty .mo file.
Which is wrong, because people will think that previous versions were not translated at all :/