Timeline
The glotpress-updates mailing list was broken, and is now fixed. You can subscribe to http://lists.automattic.com/mailman/listinfo/glotpress-updates to get emails for Trac comments and SVN commits.
This was tracked in #174. If there are any further issues, let me know.
Hello everyone. I’ve made some changes and I would like to know what you think.
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.
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
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. 
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.
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.
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:
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!
Happy GlotPressing @nacin, we’re happy to have you around!
Great!
Like we talked about on Skype, there are a few things GP is really missing so far that would make the software a lot better.
A couple of things that spring to mind:
I’m sure I’ll come up with more stuff, but this is off the top of my head
Great to get you on this project too Nacin, just gave #14 another whirl.
Hmm, what about some integration with profiles.wp.org to show some love for translators?
That’s more of a suggestion for wppolyglots/translate.wordpress.org, but yes, it is something I’d like to do. Just need to figure out how to display it.
Great! Our main problems for collaborative work:
Define validator rights only for a specific project(s).
Comments! We need to add some explaining words to rejected suggestions, etc.
Wiki page per project – for common terms, what should be done (changes), etc.
I’ll be checking the tickets and ideas I had after I’m back from spring break. Good to see this are moving forward.
Great to see glotpress getting some more love! Looking very forward to seeing this grow.
I’d love to use this for my wp plugins, but I found this particularly difficult to use in terms of updating the strings to be translated via e.g. a new pot file. That said, this was roughly a year ago…
Being able to actually delete project would be nice too. You know.. with going to the DB
Being able to actually delete a project without having to go in to DB mode would be nice too ..
+1 on this!
Also sorting projects would be great: after project ID, after date, or alphabetically after project title.
Thanx, Dave
I would suggest to add Remkus’ tutorial on installing and actually using GP for translations project, also with WP. It can be found here: http://remkusdevries.com/how-to-use-glotpress-for-your-translations/
Thanx, Dave
some way of adding comments will also be nice
I second that
Later edit: and a search-replace function
How about a subscription box here on the blog? WPDevel, BPDevel, bbPDevel, WPPolyglots all have subscription boxes.
Done
Sorry, took a bit of liberty with http://glotpress.trac.wordpress.org/ticket/193
Hope you don’t mind.
It would be great for corrections if you can search just in the translation strings and if you can search case sensitive.
For example:
email would be translated “E-Mail” in German. But sometimes the people translating it with “eMail” or “Email”, etc. Without case sensitive search and translation only search this is a nightmare to check …
+1
Would be really handy addition!
We’ve recently started using GlotPress to manage the 14 languages [and counting] supported by the WordPress Editorial Calendar plugin, and I find it useful but very far from full-featured for managing multi-contributor translations for open source projects.
First major area of concern is proper user management and permissions [yes, we would love to see the permissions structure gp plugin you mention]. This is touched on by 3 of Remkus’ points, and a bunch more in the comments.
My main question is, why isn’t GlotPress actually itself a WP plugin?!?!?! Why a separate and decidedly not mature/robust platform? Would solve so many things and make sense going forward!
If I have 1 suggestion, it would be to immediately focus on porting GlotPress to be a WP plugin to use WP custom types & taxonomies, regular WP admin, user management, commenting, subscriptions, etc. This is basically what everyone here is asking for; platform maturity and robustness, plus extensibility.
Anyone agree?
I added a ticket to refine the UX of bulk actions (approve, reject). #188, patch: 188.diff
Before:
After:
Cool.
Nice improvement.
In trunk with [680] and [681].
I’ve added a ticket to allow anonymous exports of language files (much like you can download WordPress itself without logging in to anything), but didn’t commit, to wait for everyone’s opinion on this.
Cool!! i can’t wait to see that feature!
I was going to ask for some pointers on how to update the Gaelic build from 3.3 to 3.3.1 and noticed that we’re at 0% (http://translate.wordpress.org/projects/wp/3.3.x) – seems I’ve been keeping the future 3.4 (http://translate.wordpress.org/projects/wp/dev/gd/default) up to date instead. Now I fervently hope I don’t have to redo that all – could someone let me know what I need to do to get those into 3.3.x? Cheers
You should be able to import your existing translations. Ask about the best way to do so on wppolyglots.
Yargh, caught out again… thanks. You know, from a common-mortal POV, WordPress is really confusing, not only does it use the same name for two very different products but also splits and straddles l10n over so many places I feel a bit like Alice in Wonderland sometimes
Yep, it can be pretty confusing when you are getting started, sorry! But you get used to it quickly. And if you have suggestions about improving/simplifying, they are very welcome!
Yes I do. Put them all together in the same place. From an l10n point of view, there’s no need to spread support across Glotpress and Polyglotts and whatever and to have the translations sites across a zillion pages. Create one central hub for support and another central hub where all the translation projects for .com and .org can be centrally accessed on a locale by locale basis. I have so many bookmarks for .org current, future, Continents and Cities, Multisite, Rosetta, 2010, 2011, .com – it’s a total mess. I bet I’m not the only one who gets confused – and you’re probably turning potential l10n volunteers away because it’s so confusing.
We use the polyglots blog to coordinate translation efforts. A lot of those translation efforts are centered around translate.wordpress.org, which is a GlotPress install. GlotPress is an open source project.
So, blog.glotpress.org is a place where we can talk about the code that powers translate.wordpress.org, and wppolyglots.wordpress.com is a place where we talk about translation efforts that occur on translate.wordpress.org.
There is a pretty strict separation of translation efforts on .com and .org so you will not see those merging.
That might as well have been in ancient Sumerian as far as your average willing translator is concerned. I don’t doubt there are reasons for separating stuff at the back end but in terms of the front end, that’s really contortionist to people who don’t eat foobars for snacks…
Anyway, I shan’t carp on about it. Thanks for your help, the setup may be spaghetti, but the support rocks
Well, let me try again:
GlotPress is like WordPress. It’s a piece of software you can run. WordPress has its own blog at http://wordpress.org/news/. This blog here is the same thing, but for GlotPress.
translate.wordpress.org is like your personal blog. It’s where the software runs. If your personal blog had a contact form, you could think of that as being wppolyglots.wordpress.com.
Thanks. You know, I’m not dense and I localize a lot. The fact you had to try so hard to finally get me to just about understand the difference should tell you something :/
There’s a bit of a learning curve in the beginning, especially for people who come from the localization background but don’t have lots of developing background. It does start make sense pretty quickly though, please don’t despair!
For the translation of WordPress.com specifically, there is this FAQ: http://en.support.wordpress.com/translation-faq/
And there is an overview of GlotPress: http://en.support.wordpress.com/glotpress/
What are GlotPress passwords encoded with? How can I manually generate a password hash, so that I can replace it with the default password in the database?
GlotPress uses BackPress, so phpass is used. Assuming GP/BP works the same way as WordPress, you can generate an MD5 hash, and GP/BP will then update the MD5 hash to a phpass hash.
When I started GlotPress, one of its goals was to be a sandbox for ideas, which could eventually land in WordPress. Some of the experiments made it depart a little from the (Word|Back)Press code structure. Which can be a little bit for new-coming GlotPress contributors.
That’s why I started writing a HACKING file. It’s not complete, but it’s a start.
If you are developer, I would appreciate if you have a look and tell me if it made the architecture more clear. Or if it helped you find where some part of the code lives its happy life.
Kudos, for sharing!
I would love to see the testing chapter finished
I would love to finish it, too. And I will.
thanks for sharing! Maybe it’s time to dig in the system
Hello, want to be part of the team and try my hands on it and see if I can glean for more bugs how do I get an account.
Can GlotPress be used for non-WordPress projects?
Absolutely, as long as the language files being used are in a GP supported format.
Hello.
I cant find any way to contact maker of WP translate http://translate.wordpress.org
I want to translate Latvian (LV) and pressing google translate gives error. Plz fix so most correct translations can save time of translators.
Please post your request on http://wppolyglots.wordpress.com
Also, would be AWESOME if you could help quell curiosities about GlotPress here http://bbpress.org/forums/topic/what-is-glotpress-how-does-it-work-howwhen-does-bbpress-plan-to-start-using-i
Milan, I completely agree with this, but we’ll need more hands/eyes to test the patches on the code that has changed, quite a lot sometimes, since they were submitted. Any takers?
I would like to take it, hence and while…
What is the task?
I’ve seen that most issues in the trac are very old. If we review them and upload patches to the trac or we test another patches, it will be merge to the core?
As Juan asked, will reviewed patches be merged into the core? The reason for asking is the fact that you yourself have a trac ticket #164, that is on needs-review for 4 months now.
Is there a development team who approves patches and merges them into the core? I know you can submit to the SVN as can Nikolay of course but who else?
Right now, only Nikolay and myself (and Nacin) can commit, so, the question here is how to work out a way for patches to get in to core? I suggest (subjectively) that we do a thourough review and testing of the more pressing patches and commit those. The quality of code of individual contributors should then, over time, indicate candidates for core-committing privileges. Again, that’s just me, all suggestions are welcome.
Sounds good. Do you with “we do a thorough review and testing” mean the 3 mentioned or will there be a review/testing team, or is it just anybody who can say Yes It Works
I do suggest that you and Nikolay setup a roadmap with milestones and assign the tickets accordingly. That way it’s easier to pick up tickets and work on them.
Maybe even set Trac up the way WordPress core is setup.
I commented on #199.
#170 looks good — will get to that soon. I have a feeling there might be a few more things we need to tear out, but it looks pretty thorough.