Updates from Martin (IQ) Toggle Comment Threads | Keyboard Shortcuts

  • Martin (IQ) 2:46 am on November 24, 2012 Permalink | Reply
    Tags: related strings, ticket closed   

    Sushkov closed my ticket #39 because he thinks it’s a duplicate of #9. I disagree. #9 deals with the translation history of one particular string. What I was talking about it #39 are related strings across all strings in the .pot file.

    Let’s say I have to translate a string containing the word ‘media library’. In order to translate it the right way, it would be of great help to see other strings containing the word ‘media library’ which have already been translated. In this way the translation is consistent. It’s meant as some kind of 2nd level glossary. No actual glossary, but in this way words like ‘media library’ are translated the same way across all strings. Would be very useful for e.g. translate.wordpress.com where we have over 16,000 strings for translation.

    On a side note about related strings: As we can already search for the filenames in GlotPress, how about a ‘related strings’ link in the Meta section that performs a search across all strings with the same filename?

     
    • 12:51 am on November 26, 2012 Permalink | Reply

      I’ve commented #39, could we continue this conversation there?

      As to searching by filename, and if I understand the question correctly, you already can do that: try searching for “wp-login.php” on the main file, for instance.

    • Sandra 5:55 am on December 24, 2012 Permalink | Reply

      I think this question is not WordPress-specific enguoh to stay on this site, so maybe you should re-post it on Stack Overflow, or maybe Super User (since you also mention a program). Nov 2 ’10 at 13:42

  • Martin (IQ) 6:45 pm on April 23, 2012 Permalink | Reply
    Tags: context, GlotPress, Treeview   

    I’ve created a little mockup screen I wanted to share with the glotpress people.

    https://iqatrophie.files.wordpress.com/2012/04/glotpress-treeview.png

    I’m just interested if something like this would technically be possible. I’ve drafted something similar in my trac ticket at http://glotpress.trac.wordpress.org/ticket/41

    This would help to bring some order in the huge amount of different strings on translate.wordpress.com and would help to get the context of a string. Well in a perfect world every string on translate.wordpress.com would come with a screenshot where the string to be translated would be highlighted in any way.

     
    • jrduboc 7:43 pm on April 23, 2012 Permalink | Reply

      That looks pretty neat :)
      I don’t know enough about the internals of GlotPress to know how it would be possible, but I’m guessing you’d need some sort of reference to the original file for each string, maybe stored in a database or XML file.
      I imagine that would makes things much faster than to generate this screen from scratch every time.

    • Jenia 1:27 pm on April 24, 2012 Permalink | Reply

      Well in a perfect world every string on translate.wordpress.com would come with a screenshot where the string to be translated would be highlighted in any way.

      That’s indeed the perfect world. I am not aware of any translation tools that do that. If you know some, I’d be interested to take a look :) In the ideal world, we would be able to seamlessly translate right from the interface.

      Regarding your idea, I agree it’s very helpful to know the name of the file where the string is coming from, and some people will find the tree picture helpful, too. Context always helps :)

      • Martin (IQ) 11:22 am on April 25, 2012 Permalink | Reply

        If you know some, I’d be interested to take a look

        I’m not aware of one but I think it’s important to fantasize and discuss about a perfect system without constraining oneself about what’s technically possible or not. I like this kind of brainstorming.

        In the end we should try to build a perfect system that is fun and easy to use, shouldn’t we? And I find it interesting what other think about a “perfect” system. :)

        I agree it’s very helpful to know the name of the file where the string is coming from, and some people will find the tree picture helpful

        That’s the idea behind it. The reference comments are already part of the .po files. I don’t know much about php programming but have seen some jquery treeview solutions and so I put two and two together and thought it must be possible. ;)

        • Andrew Nacin 1:19 pm on April 25, 2012 Permalink

          The GlotPress database schema is not designed for such a UI. Sure, you can search for references, but to query for them over and over, it’s just not feasible with a single LONGTEXT field. If we are going to do something like this, we’d probably need another table.

    • Martin (IQ) 1:33 pm on April 25, 2012 Permalink | Reply

      Thanks for your input Andrew. :) I don’t know anything about the GlotPress database or its inner (PHP) workings. That’s why I put this idea up for discussion. I can see why we would need another table. Building the treeview every time on the fly would probably slow down page creation to a degree where GlotPress isn’t usable anymore.

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
Follow

Get every new post delivered to your Inbox.

Join 159 other followers