I was looking for a quick way to setup GlotPress under Varying Vagrants Vagrant, and since I couldn’t find anything, I created vvv-glotpress. Use this to quickly get GlotPress trunk running under VVV.
Recent Updates Page 11
Proper Landing/Home Page
We need a proper landing page for the GlotPress project!
Something simple, approachable to appeal to the visitor. A P2 is somewhat repelling for most users or casual visitors.
It is a big problem for open source projects to present itself to the public in an appealing way. I am thinking of a simple one-pager with some headlines, screenshots and feature listing.
We should also provide tagged, downloadable zip files with short install instructions.
What do you think?
Redesign of GlotPress
It came to my mind that to get things further we might first need to make a redesign. So the plan is to work on that in January. The focus then is to make GlotPress a better collaborative place since that is the thing what it lacks now.
The most important thing is that we need to use user data to build the UI. So knowing which language the user translates for and which projects he likes. Having localization pages is one of the tasks that need to be done. I already blogged about it and Hugo Baeta already expressed his thoughts in 2011. He had some really good points there and after two years I guess we finally can work on those.
The idea is to make an plan on what pages are needed and what functionality should be provided. It should end up being a roadmap for the next year. When that is done and I got feedback on it, I will start working on the UI. I’m not a designer and I do need your help on this.
From there I can create tickets and build on the features. It’s not something that will be done in a few months but doing things step by step makes it really good to get feedback from the community and in the end to have a great product we all love and use.
Related posts:
http://blog.glotpress.org/2013/03/08/a-few-hours-ago-we-had-our-first/
http://blog.glotpress.org/2011/10/18/rethinking-the-glotpress-ui/
http://blog.glotpress.org/2010/07/14/projects-page/
Since the last update nothing special happend outside…
Since the last update nothing special happend outside our first IRL meetup. Changes since the last time are:
- Setting the correct last PO-Revision-Data instead of the current time
- Unit tests are fixed
- Changed Uzbek to LTR
- Added word-break & word-wrap to the translation table
- Added wp_locale to Tibetan and Khmer
- Added locales: Australian English and Spanish (Argentina)
- Synced POMO library and made it GlotPress independent
- Only load PHP files in the plugin folder
- Always return JSON data when using the API
From next week I will start working more heavily on GlotPress and trying to tackle the WordCamp Europe results. This also means that running GlotPress in trunk will not be recommended for a while due some changes that need to be made. Nothing should break but it’s something you never know.
WordCamp Europe results
At WordCamp Europe we had our meetup on sunday and I talked about my plans for this year and we talked about the current issues for validators and translators and builded a list from that. The following list is the issues that were mentioned and hopefully we can fix most of it this year. Some of the issues is harder to fix because I think we need a complete new UI to be able to fix it.
- Better installation process
- Delete project
- Suggestion list
- Find strings only in the translations
- Notifications on translations
- User related view of your worked on projects
- Create a user dashboard
- Comments about the translations
- Dictionary
- List of translators/validators
- Group translated strings by original
- Multiple levels of warnings
- On upload file only change the name of all changed strings
WordCamp Europe meeting
In a few weeks WordCamp Europe will have it first edition and I would love to have a short meeting over there with people who are interested to join. To bad I couldn’t speak about it but within this meeting I would love to express my vision on the project and see what your opinion is. Maybe we can work together on your idea and make it happen.
I’m not sure yet when it will be planned. It depends on the schedule but it will most likely be lunch on saturday or sunday. But would love to have this as a start point to see what you guys think and if you are interested.
The last 2 months not a lot of…
The last 2 months not a lot of stuff happened. All the changes are now on translate.wordpress.org. The focus is still more and less the same.
Changes
- Google translator does work again as a plugin. So by default you don’t
- Better Android support. Now all strings should be translatable
- Added actions when finished with importing originals and translations
- Fix some other minor issues and reverted some changes
Since the last update there are quite some…
Since the last update there are quite some nice changes. Probably the biggest is a new filter that allows you to create a “child theme” with a plugin. Because of that translate.WordPress.org has the same header/footer as WordPress.org. Also it has a link to the blog/Polyglots and the translator handbook.
Changes
- Finally fix caching bug when using Memcache including small improvement when importing strings
- Improved project view. It’s now always 100% wide
- Reverted code for changing the po/mo file names on export
- Fix typos in locales.php
- Added a new filter “tmpl_load_locations”. Now you can add your own template folder. Thanks to Nacin.
- Moved project actions outside the template and added a filter “gp_project_actions”
- Fix notice when importing new strings
- Fix all kinds of strict PHP warnings. See #220
- First small change to improve accessibility.
The next weeks I will concentrate on cleaning up milestone 1.0. Fixing some irritating bugs or moving it to milestone 1.1. Even if we don’t have versions it does help out to structure the flow.
- Improve dealing with strings. Adding ability to import fuzzy strings (#138) and be able to mark a string as “waiting” (#84)
- Ability to copy projects (#65) and copy translations between translations sets (#66)
- Ability to check the same strings in of a language in main projects and it’s sub projects
- Move Google translator out of core into the plugins folder (#170 and #133)
- Add Microsoft translator (#103)
- Records validator when importing (#217)
- Improve check for empty translations (#149)
- Improve/checking deleting of projects, translation sets and suggested translations (#186 and #223)
- More accessibility improvements.
- Remove “default” slug from a translations set (#67)
Lots of things that need to be done and the target is that everything should be fixed before WordCamp San Francisco. The main problem will probably creating unit tests
Hi Everyone I’d like to get involved and…
Hi Everyone,
I’d like to get involved and help with Brazilian Portuguese translations. What’s the best way to get started? Can I add to the translations that are marked as ‘Waiting’? Or should I work only on ‘Untranslated (random)’?
Thanks,
Aida.
I think we need to give Marko a…
I think we need to give Marko a hand, or at least some recognition of the huge amount of work that’s being done. It would probably increase participation if we had a chat and then a post on the main WP news sites about GP’s intended future. If so, when/where can we talk?
GlotPress 