WordPress.org

Ready to get started?Download WordPress

Translate WordPress

Tagged: glossary Toggle Comment Threads | Keyboard Shortcuts

  • Emre Erkan 10:11 am on April 23, 2014 Permalink | Log in to leave a Comment
    wordpress-tr • tr.wordpress.org editor
    Tags: glossary, ,   

    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.

    Possible solutions;

    • 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 ^ ^

     
  • jenialaszlo 9:37 pm on January 16, 2014 Permalink | Log in to leave a Comment
    jenialaszlo
    Tags: , glossary, translation resources   

    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!

     
  • Ze Fontainhas 9:16 am on March 9, 2012 Permalink | Log in to leave a Comment
    vanillalounge • pt.wordpress.org editor
    Tags: glossary, ostd   

    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.

     
    • Carlos E. G. Barbosa 5:22 pm on March 9, 2012 Permalink | Log in to Reply

      Supposing those other strings are products of human labour, and not of another (or the same) automated source – it seems good.

      I see it as a very short term solution, however. As long as more and more translatorlings leave their job to automated systems, that system becomes vicious, so more and more garbagge will populate those new .PO files.

      Automated good translations are just a dream to this moment. And this OSTD is not an automatic translator, but an automatic searcher for hopefully human strings spread around elsewhere…

      • 5:33 pm on March 9, 2012 Permalink | Log in to Reply

        Very true, and yes, the strings are products of human labor. I agree with the system becoming polluted, but I like the idea of having previous translations as helpers. The ideal scenario would be to have this functionality in a tight system (like GP), where consistency can be a little more accurate. In other words, an internal, human generated, glossary.

        • Gabriel Reguly 6:22 pm on March 9, 2012 Permalink | Log in to Reply

          Speaking about glossaries, how can one generate a glossary from GlotPress?
          Is it possible?

        • Carlos E. G. Barbosa 2:37 pm on March 10, 2012 Permalink | Log in to Reply

          Zé,

          I totally agree with your ideal scenario. When we have a trustable crew (sharing the same semantic universe and) providing equally trustable strings to such a glossary, then we can get consistent suggestions coming from that ‘automated’ system.

          That is a must indeed…

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel