Hello everyone! You probably know me as a WordPress core dev, but I also work on wordpress.org the site. That includes translate.wordpress.org and now I’ve ventured over to GlotPress as well. 
As you can probably see, I’ve been active in the last week in GlotPress development, on the heels of spending the last few months working on i18n in WordPress.
I hope to spend a few hours here and there making GlotPress and translate.wordpress.org better, but for that, this American monoglot needs your help. I’ve read this blog, but perused only some of Trac. I’m also still getting familiar with the codebase, so I’ll be looking to @nbachiyski to advise on architectural questions.
I do want to talk about the roadmap, but not yet. (Next week!) Help me get up to speed first. So: what are the nagging bugs and enhancements? Which tickets or patches on Trac need traction? What’s your pet project or peeve? What feature requests do you consider to be the highest priority? Who is willing to contribute code, who already has? How is GlotPress working for you? How is it not working for you? What else should I know or see? Tell me what to read and I will do what I can to absorb.
Here’s what I’ve worked on so far:
- Wrote a plugin for translate.wordpress.org that overrides the permissions system to use Rosetta user roles (happy to open-source this for the GP community at large)
- Performance improvements [671], [672]
- Updated jQuery and jQuery UI, and updated JS to use newer methods [673] [675]
- Fixed #183 (“Copy to original” on plural strings)
- Committed fixes for #169 and #184
- Bulk actions UX/UI changes, see previous post here
- I have looked at and asked Nikolay to review #187, #170, #135, #139, #163, #150, #129, #115, and #14.
I also put in a request to have a GlotPress mailing list receive SVN commit and Trac ticket/comment emails, which should happen his week. (#174)
Hope to see you around. Happy translating!
Jenia 1:27 pm on April 24, 2012 Permalink |
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 |
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.
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 |
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.