I have given out our language url (https://translate.wordpress.org/languages/nb) to potential translators. I recently discovered that the “Administration” partial of the WordPress translation isn’t visible there. This led to me not getting any help with that one this time… What’s up with that? 😉
Tagged: glotpress Toggle Comment Threads | Keyboard Shortcuts
I keep getting all sorts of warnings like “Warning: Lengths of source and translation differ too much.” or “Warning: Lengths of source and translation differ too much.” when I try to translate a string at translate.wp.org. This happens for every string. Could someone please take a look?
Notes from the discussion on improving GlotPress (Mon, Oct 29th), suggested by Marko for the Community Summit in San Francisco.
Birgit Olzem, Catia Kitahara, George Stephanis, Mayo Moriyama, Marko Heijnen, Paolo Belcastro, Petya Raykovska, Rafael Funchal, Sam Sidler, Stephane Daury, Xavier Borderie.
If you were there and I missed your name, please leave a comment.
Here are my (slightly) structured notes from the Polyglots and GlotPress meeting at WordCamp Europe Contributor day on September 29th.
If you were there, please feel free to add to the notes if you feel I missed something important.
Roadmap for GlotPress
- GlotPress is not even at 1.0 – Doesn’t have caching, doesn’t have translation memory. Who’s gonna work on it?
- Data Schema, different one – Nacin and Nikolay are going to work on that
- Next step: Include Themes and Plugins in GlotPress
- Be prepared for hundreds of new validators
- Find a way to fight spam and security issues
Promised: Marko will ship profiles for GlotPress before WCSF
Scaling the community
A lot of languages don’t have an active validator – we need to change that
Average number of strings:
- Themes – 200-300 strings
- Plugins – 150-200 strings
- Core – 4000 strings
- BuddyPress – 1400 strings
Next step for Polyglots and i18n: Plugins & Themes
There needs to be a way for readmes to be translated.
There’s a lot of potential to get WordPress to 90 different languages.
We need to find developers to help with translations who are not heavily involved with core.
How do we put all the plugins on GlotPress (translate.wordpress.org)?
30 000 plugins that need to be translated
Rosetta sites will have their own theme and plugin directories with all translated plugins and themes
need a search that will work across languages. Search for plugins and themes should target both the translated language and English.
We start with 25 plugins
We need a mechanism to block spammers better. For forums, for local sites.
- agreed that each global communit should have their own P2
- there will be functionality to approve comments as approve/delete/move to forum
- @siobhan to get in touch with Jetpack ppl about subscribing to tag
- should have lists of validators. Lists of validators should also be on local sites.
Promised: Remkus is doing the forum theme for BB Press for the local sites/forums
We need to make it easier for validators to work
Redesigning GlotPress, improving the tools
Security concerns with strings
Possible decision: Two tears of validators. Trusted validators for the core project and some of the other main projects.
Other validators for all of the plugins etc.
Polyglots team leads
The current goal is to split the role of Polyglots lead in two:
Community role/team – pushing validators, pushing people, finding validators, pinging validators, giving validator rights, helping validators and translators get started. The goal is to have a team of community ppl from at least three different parts of the world.
Sam will document the specific tasks of the role of Community Lead for Polyglots and also the technical lead
- Select people from the existing validators and community
- Select people who we know are responsible and will get the job done
- Give them a long term role and back them up with others
As I understand, there are no (active) validators for Lithuanian at the moment. I would like to be one.
How do the translations of the GlotPress web interface itself (i.e., those at https://translate.wordpress.org/projects/glotpress/dev) get implemented?
As there are currently three separate discussions regarding GlotPress enhancements I’ll post this here as it probably should have been posted already.
Secretmapper will post updates to http://blog.glotpress.org/
Now is probably be a great time to get more involved and help shape the direction of GlotPress
Something that would really help the English variants is to have a feature that can copy all of the original strings for untranslated as the translated string, and leaves them as Waiting status.
Being able to check and bulk accept these strings (fixing variations where necessary) would be considerably quicker than going through each string one by one to click on Copy original and accepting.
~95%+ of strings are going to be identical anyway between US English and British, Canadian and Australian etc. English, so I think it’s sensible to go with the assumption that strings match, and change where necessary, than assume the US English is going to be wrong (as with all other non-English variant languages).
First of all, thanks for glossary. It’s a life saving functionality.
I’m currently validating lots of project and trying to maintain order between them. Glossary is a very helpful tool to accomplish this but it’s project specific. Is there a way to use a common glossary for selected projects or for all of them?
Please don’t say import/export. It’s not functional when you try to keep all glossaries from all projects updated. For example when translating or validating a project, you see a term which needs to be put in glossary. You can’t add it to just that project if it’s a very general term. You have to put it to all glossaries. Yoı choose a projects glossary as primary glossary and update it, export it and import it every project you’re validating.
- A single glossary for all projects
- Import functionality betweeen glossaries
- Inheritance (When you create a glossary you choose a parent and with this it contains all the terms of parent glossary)
TL;DR -> title ^ ^
Is it possible to make GlotPress dashboard a little bit more useful? Like showing active projects and their statuses to validator like this: http://imgur.com/Bh2Kg1x
It’s hard to track all the projects. I have to check every project to see if there is new or waiting translations. Just WordPress Core has 6 active projects (3 themes, WordPress, Administration and Network). There is mobile projects, plugins etc. It’ll be a handy feature if implemented.
Version 3.9-fr_FR shipped with a set a bad strings (slippery fingers, honest mistake, but still). I compiled a new archive with the corrected strings, but how can I make sure the translation files are getting pushed to users who have already upgraded to 3.9?
Noticed a bug (?) while editing translation of BuddyPress here https://translate.wordpress.org/projects/buddypress/dev/ru/default
Not all untranslated strings are showed. How did I found that:
1) went through all untranslated strings,
2) exported the po file of everything ru_RU
3) opened in Poedit and noticed that some strings appeared to be untranslated, although they are not listed under Untranslated filter in GlotPress.
4) translated them in Poedit and imported into GlotPress
5) got the message that 16 new strings were translated.
So in general – untranslated strings were not showing under Untranslated filter in Glotpress.
If some of you know I’m working on GlotPress and since it’s getting more activity I would love to setup a biweekly meeting. If you would love to help out by sharing ideas or maybe contributing back then please leave a message at http://blog.glotpress.org/2014/02/28/since-we-gain-a-bit-more-activity-lately/.
I just translated 125 terms to Arabic for GlotPress Development. please validate https://translate.wordpress.org/projects/glotpress/dev/ar/default