Recent Updates RSS Toggle Comment Threads | Keyboard Shortcuts

  • Nikolay Bachiyski 9:55 pm on November 14, 2011 Permalink | Reply
    Tags: code, HACKING   

    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.

     

  • Zé 5:58 pm on October 18, 2011 Permalink | Reply
    Tags: patches, trac   

    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?

     

    • Carlos E. G. Barbosa 4:10 pm on October 21, 2011 Permalink | Reply

      I would like to take it, hence and while…
      What is the task?

    • Juan Ramon 2:41 pm on November 24, 2011 Permalink | Reply

      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?

    • Peter 3:15 pm on January 17, 2012 Permalink | Reply

      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?

      • Zé 3:21 pm on January 17, 2012 Permalink | Reply

        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.

        • Peter 4:58 pm on January 17, 2012 Permalink

          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.

  • Hugo Baeta 5:42 pm on October 18, 2011 Permalink | Reply
    Tags: design, ui, ux   

    Rethinking the GlotPress UI 

    Hey guys, first post in the GlotPress blog, so I think I should introduce myself and give context to why I’m posting.

    I’m Hugo, I work for Automattic as a Social Designer. I love designing user interfaces and craft the experiences so that a product is easy to use. I’m also part of the Portuguese WordPress Community and I’ve used GlotPress to help translate WordPress to Portuguese!

    My friend and coworker Zé, asked me to “take a look” at the ui of GlotPress and brainstorm a bit on how it could be improved.

    We started talking about a bunch of stuff and details, but I decided to focus on one thing at a time. Here are the priorities on my first iteration here:

    • Improve the visual design of GlotPress (Zé mentioned he’d love to have it look more like the WordPress Dashboard)
    • Improve the information architecture on the header – reducing the redundancy and streamlining the interaction
    • Improve the List Actions / Sorting / Filters to match the needs of a power user, as well as to make it easy for newcomers

    With this list in mind, I sketched some ideas and we ended up coming up with this:

    Things worth mentioning:

    • The visual design is much closer to the one on the WordPress Admin
    • Got rid of the GlotPress logo at the top, as it didn’t really give any context and if you contribute to translations on multiple sites (ie: WordPress.org, WordPress.com, Genesis Framework, etc…). Now you get instantly a notion of where you are without any clutter
    • Separated the Bulk Actions, Sorting and Filters into different areas, to make it clearer what each do. My thinking behind this was to have the filters (I’m calling it “Quick Filters” right up in the visual hierarchy, next to the contextual title (You’ll also notice a “Advanced Filters” link at the end, which I’ll mockup the interaction on a later iteration). On a second line you find the things that directly affect the list – Bulk Actions and Sorting on one side (made it much simpler by just using select items), and the Visualization options (Wishlist – like WordPress does with lists – more on this later on), item count (whishlist as well) and pagination.

    I would like to get the discussion going around this and to get your opinion so I can know if I’m in the right direction or not (feel free to kick me in the but!) :)

    Cheers!

     

    • Carlos Eduardo G. Barbosa 12:36 pm on October 19, 2011 Permalink | Reply

      I totally agree with what Hugo says here on the GlotPress logo. I go a step further, however. Sorry if this mislead a bit the mainstream of this discussion.

      If we treat GlotPress as just an administrative Panel, we will never improve properly its UI, as it will never be anything else just a dry admin panel structure. GlotPress pages, however, are not closed to public. They are public workig pages that can be actually seen by anyone, despite the fact that just registered and empowered users can change their contents.

      I am using GlotPress and I would like to apply too it the same visual rules I’ve addopted to my WP installations. This is preciselly my point, here. It’s nice to have your visitors easily aware of where they are – and this is why we should have visual themes on GP.

      GlotPress is a nice platform, but lacks visual flexibility. That “gp-templates” directory should rather be “gp-themes/gp-basic-templates”, so anyone using GlotPress could develop his own visual conception as a new theme to be added in a new child-directory on gp-themes – as it works with WP.

      Let us choose or make our own themes in GP. If we just add this functionality, a lot of nice visual solutions will pop out from the community, for sure.

      • Hugo Baeta 6:19 pm on November 1, 2011 Permalink | Reply

        If we treat GlotPress as just an administrative Panel, we will never improve properly its UI, as it will never be anything else just a dry admin panel structure.

        Interesting statement. In my mind GlotPress is exactly that, just an administrative Panel to achieve a goal – collaborative translations of something else. The “public” aspect of it is quite limited because of that. I see GlotPress like I see the WordPress admin – it’s a tool, not a front, public-facing, site.

        Now, on that note, I also agree that *some* visual flexibility should be given, maybe the admin could choose a color pallete or something. But if the experience is tailored correctly, messing with that will only create confusion. As I said, I collaborate on several installations of GlotPress – WordPress.com, WordPress core, Genesis Framework – if these 3 had different UIs, it would be a nightmare!!

        Just to clear thing up, the work I’d like to collaborate on here is with the core User Experience of GlotPress, and also cleaning up the UI in the process – it’s not only a visual (re)design. ;)

        • Carlos E. G. Barbosa 1:09 am on November 26, 2011 Permalink

          “In my mind GlotPress is exactly that, just an administrative Panel to achieve a goal – collaborative translations of something else.”
          —————

          Hi Hugo,

          In my opinion it may be just an administrative panel, if concealed and access-restricted to none else than the registered users.

          But it is not thus.

          To achieve its main goal the GlotPress installation must be a “public-facing site” as it is, in fact. How else should the collaborative aspect of the translations be privileged?

          With GlotPress that translation task is no more a blackbox procedure. It is visible and world wide accessible as a site that points to “something else”, isn’t it? The “something else” may give it a reason why, but the translation job has got a face itself. So why be so shy in giving it that nice visual flexibility?

    • Remkus 1:15 pm on October 19, 2011 Permalink | Reply

      Ooh, I quite like this. Love to see GlotPress look it’s a WordPress clone!

    • Wacław J. 10:53 pm on October 29, 2011 Permalink | Reply

      I would like the “Approve Selected”/”Reject Selected” buttons to be moved from the bulk edition box so there is no need to expand something every time you want to use them to make approving/rejecting translations easier (or if the “Details” boxes wouldn’t close after approving/rejecting a translation, which is what happens when you submit your own translation — it skips to the next one).

      P.S.: How do I log in?

    • Kenan Dervišević 5:19 pm on November 2, 2011 Permalink | Reply

      I really like this new look. The new look and keyboard shortcuts (there is a patch waiting for that) would be an excellent improvement. When can we expect this to be implemented?
      Also, I would like to have an option to actually hide this yellow notification for new users so that I don’t have to do it every time I clear cache in my browser.

  • Joost de Valk 9:56 am on October 4, 2011 Permalink | Reply
    Tags: profile, user   

    Profile Page 

    I’ve been working a bit today on creating a profile page as there are some settings that I really think users should be able to set for themselves, most importantly the number of items per page, but also default sort options.

    Right now, it looks like this:

    Profile page

    A preliminary patch for this is attached to this Trac ticket, but just contains the number of items per page, I’ll clean up what I’ve got now and add a second patch, but I’d love to know what you think should be in there…

     

    • Zé 10:00 am on October 4, 2011 Permalink | Reply

      This looks really good. (hint: we.need.moar.testers!). As a note to self, “Filename in source” needs either a better explanation or a different description and “Default Sort How” is rather “Default Sort Order”.

      • Joost de Valk 10:02 am on October 4, 2011 Permalink | Reply

        Agreed, the default sort order is easily changed.

        • Zé 10:03 am on October 4, 2011 Permalink

          Which begets the question if “Default” is needed at all…

    • Joost de Valk 10:08 am on October 4, 2011 Permalink | Reply

      Ok added a patch to the ticket that has the full code for the above, with one minor change: “Order” instead of “How” both here and in the Translations interface :)

    • Milan Dinić 10:26 am on October 4, 2011 Permalink | Reply

      Since Joost is creating hype over GlotPress (and that is good), we should use it to at least fix those issues that have patches, they are sitting over there for a long time.

    • Profesor Yeow 9:18 pm on November 3, 2011 Permalink | Reply

      Nice job! Congratulation Joost

  • Nikolay Bachiyski 2:31 pm on July 14, 2010 Permalink | Reply  

    Projects Page 

    The projects page, listing all sub-projects and translations, is one of the most visited pages in GlotPress. But its current layout lacks vital information. Like which translation teams have reaches furthest in the translation race. Or where should I start translating, if I am not an active translator. That’s why we have some mockups of the project page, redesigned.

    Goals

    Before showing you the mockups, here are what you should be able to accomplish on this page:

    • Know which software application (or which parts of it) you can translate in this project and get more detailed information about the project and its structure (sub-projects).
    • See all of its translations.

    Apart from the general goals, there are more specific goals, depending on the user, visiting the page.

    If you are a random user, just browsing around, you should be able to:

    • Get acquainted with the project
    • Quickly see stats for the project translations: in which languages are there translations and how complete they are

    If you have come to this page to translate:

    • Determine whether this is the right project to translate
    • You should be able to easily access your language translation
    • Quickly see how your language translations compares to other translations

    If you are a validator:

    • Add the translation in your language, if it’s missing in the list

    If you are an administrator:

    • Edit the project
    • Create sub-projects
    • Create translations sets in this project
    • Import originals for this project

    Mockups

    Project Vertical

    The first one has the same layout as the current page, with a couple of new things:

    • Has Active project functionality. Active projects show random users what to translate. For example the Development projects should be active and the 3.0.x one shouldn’t be active, because it is designed to include only string fixes.
    • The actions are moved to the top. Scrolling through all the translations was tedious for project admins.
    • Sub-projects got inline descriptions.
    • There is no delete link anymore. It should be incorporated in the Edit page.
    • Validators will be able to create the translation sets themselves.
    • Each user will be able to set preferred languages in their profile. These languages will always be shown on top.
    • The extra column may include handy stuff, depending on the context. For example on WordPress.com we may include the last deployed time.

    Another, more compact take:

    Project Split

    This is essentially the same, but sub-projects and translations were fit into two, instead of one long column. This layout will be great for projects, which have lots of sub-projects like WordPress (it still doesn’t but a fast forward a few releases and you’ll see).

    We’d like to hear your comments on these mockups.

     

    • Ben L. 2:59 pm on July 14, 2010 Permalink | Reply

      I really like the two column layout. The only thing I’d change about it is the lack of sub-project descriptions. (Maybe they could go below each sub-project name?) Also, after looking at it for a while, the number columns might look better center- or right-aligned. Other than that, these mockups look great!

      • Nikolay Bachiyski 3:06 pm on July 14, 2010 Permalink | Reply

        I didn’t really care about alignments when I did the mockups :-) They will definitely be centered.

        You are right about the sub-project descriptions. They would happily go below the names.

    • Stefano Aglietti 3:08 pm on July 14, 2010 Permalink | Reply

      I’d like both of them with a preference for the #2, i would like to see the tabel splittend into 2 having the first one with the languages u are validator/admin/etc… for casual users trying to guess the right language from browser would be nice.

      Having a preferred languga table, can lead to have, but I do not know if it’s possible, all the project and version active, maybe planning to have text description on top of the page and other palces, and maybe the whoe interface, transalte and customized by admin for various languages…

      Just my 2 cents

    • Milan 4:28 pm on July 14, 2010 Permalink | Reply

      You had a good idea in #95 for POT generated date which is missing from both of these.

      I too prefer second layout but there isn’t “Extra” column for which I like idea from first layout.

      For me, more important page would be user’s profile page similar to one from #94. This could be user’s dashboard with list of projects, POT generated date, number of strings added with that generation, “Extra” column as in project page, number of untranslated, waiting, fuzzy and warnings etc.

    • dominik matus 5:39 pm on July 30, 2010 Permalink | Reply

      hi, can you add links to stable packages of glotpress? I want run glotpress for plugins. Thanks

    • vireax 5:58 pm on August 15, 2010 Permalink | Reply

      It seems that the development is too slow. I need this software to install for my site but there is no back end to add more users or to do administration task.
      I don’t know how fast the development can proceed but I just found http://crowdin.net/ has just went ahead and allow users to add manage their own projects, at least.
      I’m serious in testing, but so sorry not able to help in programming section at all.

    • Armen Danielyan 8:53 pm on October 6, 2010 Permalink | Reply

      Dear Nikolay,

      I want to translate WordPress to Armenian, but unfortunately I can’t find it in the list of available languages. I am native Armenian speaker and I am also fluent in English. Please advise how Armenian language can be added.

      Thank you

    • itgasht 1:26 am on October 23, 2010 Permalink | Reply

      Thanks Nikolay Bachiyski. GlotPress is an useful tool for translators.

    • Atrax 8:00 pm on November 15, 2010 Permalink | Reply

      What about plugin API?

    • Jamàlorg 6:46 am on March 3, 2011 Permalink | Reply

      Are there plans to add some missing languages, I went to the translation page, but I can’t find the language of my country.

    • Aadhil 11:11 am on May 20, 2011 Permalink | Reply

      Hi. I cannot find Maldives or Dhivehi in the transalation area for wordpress.com. I would like to help i translating wordpress to dhivehi.

    • kalamendi 9:48 am on June 2, 2011 Permalink | Reply

      I want to translate wordpress to euskera ( vasco in spanish),

    • Rico 10:52 pm on June 6, 2011 Permalink | Reply

      Hello,
      How is it possible to download the translation for e-commerce in German?
      Thank you & best regards,
      Rico

    • jonezjea 11:30 am on June 9, 2011 Permalink | Reply

      This is an epic way to translate WordPress. You people should make this available for download because other projects could use this very neat method.

    • Yiannis 1:58 pm on June 12, 2011 Permalink | Reply

      Hi,

      I need to use the Greek translation of WP-ecommerce. I am also willing to update it with any words I will add. Can you please tell me how I can download/export a .po file (or any other format for that matter, and then convert to .po)?

      Thanks,
      Yiannis

    • Sundar 8:56 am on July 12, 2011 Permalink | Reply

      Awesome work!
      All the translate editors I’ve seen so far don’t have a UI as great as this =).

      Is this a downloadable plugin?
      Sorry for the amateur question – didn’t know where to look for it.

    • orange frog 3:08 am on July 14, 2011 Permalink | Reply

      I think it needs the aesthetics sorted out. also, GlotPress needs more info about what it is :)

    • GJONETO 5:25 am on August 12, 2011 Permalink | Reply

      Excellent work you are doing. I am with you guys. I’m helping layout the translations in Albanian. Let me know what else you might need. – GJONETO

    • jwtear 3:18 pm on September 4, 2011 Permalink | Reply

      Must be Validator or Admin to add New Translation?

      thanks.

    • Profesor Yeow 9:19 pm on November 3, 2011 Permalink | Reply

      I will try to help you with the Spanish, that is my language.

  • Nikolay Bachiyski 6:22 pm on June 14, 2010 Permalink | Reply  

    Future Roadmap and 1.0 

    GlotPress has been alive and kicking for a couple of months now. There has been positive feedback and there has been not-so-positive feedback. But there have been tons of feedback. Translators have been using inferior tools for years and already have a long list of features they want in a translation editor. This led to the logical question: which feature do we implement next?

    One thing I’ve learned from WordPress development is that implementing every feature users want rarely makes all users happier. Often those who requested it, don’t use it either. We should include only functionality that is useful for 99% of our users. With this smart advice in mind, I started sorting out through the hundreds of suggestions I had collected during last couple of months. But I encountered a little problem.

    Most of the features in the list would be useful to 99% of the users. A collaborative translation editor, which makes translators’ life easy, wasn’t as simple as I wanted. The question again was: which features do we implement now and which do we implement later?

    On the dev-day just after WordCamp San Francisco in May, we had a brainstorm session for features and their priority. You can see the result in the Active Tickets by Milestone report in trac. Roughly when we are done with tickets in the 1.0 milestone will be the time to release 1.0. In each milestone tickets are sorted by priority — these on top will be implemented first.

    Implementation is the hardest part, even though above I complained how sorting out features and priority was hard. If you feel like coding, grab a feature and drop a line in the mailing list. We’ll be more than happy to help with any advice, testing and debugging.

     

    • Josemi 7:39 am on June 20, 2010 Permalink | Reply

      I know that is to early, but, For when can we expect 1.0 final version?

      Greetings.

    • Cyril Duval 6:30 am on June 27, 2010 Permalink | Reply

      Hi, can’t find place to contact you, so go for here! It would be great to have a context filter in the translator system. I mean by context, that we can see were the words are on WP pages or wich part of the dashboard we translate (Poll, settings, etc.) Thanks for your great job.

  • Nikolay Bachiyski 6:09 pm on April 9, 2010 Permalink | Reply
    Tags: , project, sub-project, translation-set   

    Mass-create Translation Sets 

    When you create a new project, it doesn’t have any translations and all translation sets have to be created one by one. In case of a larger GlotPress installation it usually makes sense to use the same translation sets from another project. Usually a parent one.

    This was the case with translate.wordpress.org. We made a project Twenty Ten for translating the new default theme in WordPress 3.0. The project was a sub-project of WordPress Development. Since all translators of the trunk version of WordPress would want to translate the new default theme too, I just synced the translation sets of Twenty Ten with those of WordPress Development using the new mass-create feature.

    You can see the feature in action in this short video:

    As shown in the video, you can choose which project to sync translation sets with and then preview the added/removed sets before clicking Submit.

     

    • drew3000 1:14 pm on April 14, 2010 Permalink | Reply

      Interesting stuff. I’d be keen to try this out to translate versions of Ushahidi.

    • jattboot 1:51 pm on April 25, 2010 Permalink | Reply

      how to add more language, my language Punjabi is not add to list and there is no way mention on page to request for that

    • Francesco Laffi 1:22 pm on April 28, 2010 Permalink | Reply

      GlotPress is really promising, is it planned in the future to integrate it with wp plugin repo? for plugin devs’ and plugin translators’ sake

    • SteveAgl 7:42 am on April 30, 2010 Permalink | Reply

      Where can i find info about how translation leaders in various language can use and administer translation in thi snew project?

  • Nikolay Bachiyski 3:49 pm on March 12, 2010 Permalink | Reply  

    The GlotPress Report #3 (Feb 26 – Mar 12 2010) 

    The most important changes since the last report are the new formats for import/export. GlotPress now can use Blackberry RRC and Android XML files.

    • In [426] the first traces of documentation were added in the form of a README file;
    • In [427] – [430] the format framework and the RRC format were added;
    • [440] fixed a bug when the user wasn’t redirected properly after login. This was annoying.
    • In [442] we added the Android format;
    • [443] fixed a bug introduced in [441], which allowed non-logged in users to be super-admins in certain conditions.
     

  • Nikolay Bachiyski 2:44 pm on February 26, 2010 Permalink | Reply  

    The GlotPress Report #2 (Feb 19 – Feb 25 2010) 

    It was a slow week for GlotPress.

    The only changes were language variants standardizations and plural forms fixes, contributed by Zé. All variants language names are now in the form Main language (Region). Example: Spanish (Chile).

     

    • параклис 10:04 am on April 24, 2010 Permalink | Reply

      Здравеи,

      about the plural form, I find it confusing that 11, 21 etc. is considered single. This should be re-thought. Who says “11 item” instead of “11 items”? Or “21 item was moved to the thrash” instead of “21 items were moved to the thrash”? If by some chance this is considered grammatically correct in English, in other languages it is not.

  • Nikolay Bachiyski 11:46 am on February 19, 2010 Permalink | Reply  

    The GlotPress Report #1 (Feb 5 – Feb 18 2010) 

    Before diving into specific features and bug-fixes, this week’s news it that translate.wordpress.org was launched. It is a GlotPress install, which allows all WordPress translators to collaborate and will host the translations of all the projects in the family like bbPress and BuddyPress.
    • In [407] – [410] we added proof-of-concept JSON API for the translations page. Just prepend /api in front of the URL. For example /projects/wp/dev/de/default gets you the HTML page for German translations and /api/projects/wp/dev/de/default will return the same information, but in JSON.
    • Since [411] and [412] GlotPress can be installed in a directory different from the user-facing GlotPress URL. The purpose of that is mainly to have it as an svn external.
    • In [419] – [421] project pages got visual fixes: description is now shown, the text for no translations isn’t show if there are sub-projects.
    • [422] fixed a serious bug, which prevented users with approval access to discard warnings.
     

← Older posts

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 51 other followers