In August I written this https://make.wordpress.org/polyglots/2016/08/23/the-glossaries-in-the-wordpress-localization/ and now the talk at Mozfest is confirmed (the agenda is not yet published).
As I said I am here to share to you the information gathered and the talk itself.
The slides (working in progress) are here: https://docs.google.com/presentation/d/1RrDjagEKXx12kRSolAg9_UP-MdMduL1hQpdaqKgeMBU/edit?usp=sharing
They contain also the link to all the information like result and analysis
this title it’s for a call to action in filling a survey.
I proposed a talk for the Mozilla Festival (http://mozillafestival.org/) in London “GlotDict and glossary in WordPress” https://github.com/MozillaFoundation/mozfest-program-2016/issues/8 .
As you can see the topic is the glossaries in WordPress and how much they are important as polyglot.
The talk is under consideration so if that talk will be not approved I will prepare the talk for a future WordCamp, so no worry!
All the data gathered will be published publicly for the end of September 2016 on make.wordpress.org so all the community can benefit from this information!
The anonymous survey: https://goo.gl/forms/jPq9TBu9vkiclW2v1
Thank you for your time!
We have a Glossary section of the handbook: https://make.wordpress.org/polyglots/handbook/glossary/
I need your help with gathering all the terms we need to explain in the glossary, so here goes:
- Experienced contributors, please add the terms you’re missing in a comment of this post
- New contributors, please add any term you’re not familiar with you come across – again in a comment here.
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 ^ ^
Translation style guides and glossaries: I created a draft Codex page for Translation Resources. The goal is to improve multilingualization. Would you mind sanity-checking/adding links for your language? Feel free to drop them in comments or edit the Codex draft page. Particularly curious about Dutch, Turkish, and Indonesian resources (did not find any links). I appreciate your help and feedback on this!
This is interesting:
The OSTD ( http://littlesvr.ca/ostd/ ) is an automatic translations system – it will take your .POT file and populate it with translations based on strings in other open source software, generating .PO files. Given that you can see which software the strings come from – this will be much more accurate than other automatic translation systems such as Google Translate.
In short, the beginnings of an automated glossary. Maybe worth exploring a collaboration? No API at the moment.