Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Marko Heijnen 12:52 pm on April 12, 2014 Permalink | Reply
    Tags:   

    It has been almost five months since the last update post. Since then we added two major features to GlotPress.

    The first one is that we have glossaries now. It gives validators the opportunity to have a list of most used words and how they should be translated. It makes it easier to manage translators since you can point them to the glossary. There are still some things to do but you can already use it. For progress see ticket #97. Props for Yoav on this one.

    And as second we finally have project branching. It allows admins to duplicate a project with all the originals, translation sets and translations. Milan Dinić worked on this a long time ago and we finally committed this. See ticket #65.

    Other features added are:

    • Allow setting originals’ priority on import. See #275.
    • Skip strings that are marked as untranslatable when using the Android format. See #279.
    • Stop needed ?action=upgrade when upgrading the database. See #281.
    • Improved guess_uri() to also work when there is an url passed in a GET parameter. See #282.
    • Updated jQuery and stop using $ sign. See #284.
    • Added phpunit.xml file and moved tests in their own folder. See #285.
    • Fixed UTF16 and escaping issue when importing new strings with the .strings format. See #295.
    • Generate .htaccess file automatically when posibble. See #280.
    • Added more unit tests.
    • Added support for Fulah, Tigrinya and Rohingya.
    • Added wp_locale for Irish, Marathi, Mongolian and Amharic.
    • Fixed the Rohingya locale information.

    We recommend everyone who is using GlotPress to update to the latest code base.

     
    • Mattias Tengblad 1:40 pm on April 12, 2014 Permalink | Reply

      Good job guys! Keep it up.

  • Yoav 8:37 am on March 4, 2014 Permalink | Reply
    Tags: intro   

    So Marko said:

    I’m a developer working at Automattic, with a big interest in everything i18n and l10n. I started diving into GlotPress a few months ago with hope that we can get some traction into the project, fix bugs and introduce some much needed features.

     
  • Marko Heijnen 7:44 pm on February 28, 2014 Permalink | Reply
    Tags: ,   

    Since we gain a bit more activity lately due the fact that Yoav Farhi started to contribute back to GlotPress. One of the great things he did was building the glossary features which still needs some fine tuning but already looks really great. Because of this I would love to have a weekly or biweekly meeting and I would love to hear if you would like to see this and when it would fit best.

     
    • Yoav 8:31 am on March 4, 2014 Permalink | Reply

      Good idea. Morning or late evenings UTC would work best for me. Bi-weekly seems fine to begin with.

    • Jenia 11:08 am on March 4, 2014 Permalink | Reply

      Hi Marko! I am helping out with the translation side of things at Automattic/WordPress.com, working with volunteer, in-house, and professional translators so that translated WordPress.com is just as awesome as the English one. We use GlotPress extensively: http://translate.wordpress.com/projects/wpcom . I also help out with the Russian translation.

      I’d love to see GlotPress grow further and would be interested in joining the IRC chats from the user point of view. UTC 7-11am works best, could make do 7-9pm, not available on Wednesdays.

      Maybe repost on http://make.wordpress.org/polyglots/ to get more involvement?

      • Marko Heijnen 11:14 pm on March 4, 2014 Permalink | Reply

        I guess for now I would choose the early time since that would work best for us. Also if we want to do some work after the meeting then we still can do that.

        I will report it right now Polyglots. That is a really good idea.

    • Jenia 11:15 am on March 4, 2014 Permalink | Reply

      the glossary features which still needs some fine tuning

      I still don’t see the glossary live on translate.wordpress.org. I wonder if the fine tuning you mentioned could be a separate trac ticket/task? In the meantime, I would suggest deploying v1 so that .org translators have a chance to test it and provide feedback. Then, it would be possible to deploy the fine tuning fixes and anything else stemming from the feedback in v1.1. How does it sound?

      • Marko Heijnen 11:08 pm on March 4, 2014 Permalink | Reply

        We don’t really control that. I can only request that they update it and hope for the best. I will do that in the weekend.

    • Naoko Takano 2:05 am on March 5, 2014 Permalink | Reply

      I’m in JST timezone (UTC +9) but willing to wake up whenever, as needed :)

    • Petya 8:28 pm on March 11, 2014 Permalink | Reply

      I don’t know why I’m only seeing this now, but I’d like to join too. Sorry if I’m missing something (it’s been a long day), but it seems to me you set up time but no date for the chats?

      Is there a date set that I somehow managed to miss?

  • halimovparviz 7:29 pm on February 26, 2014 Permalink | Reply  

    how can I translate a wordpress into Tajik Language. I don’t know how could anyone help me ? Not like giving a link just say how to do pls?

     
  • Marko Heijnen 9:01 pm on February 22, 2014 Permalink | Reply  

    Unit tests improvements 

    The last 24 hours I made a few changes to the unit tests. I little bit cleaned out some of the code and move all the tests inside its own folder. I also added a phpunit.xml.dist file that by default also logs the coverage. The progress can be followed on https://glotpress.trac.wordpress.org/ticket/285.

    This log file is used for code coverage and you can see it on http://github.com/markoheijnen/glotpress. Currently the coverage is 34% and that isn’t high enough. In the next weeks I’m going to try to get the coverage above 50%.

    If you want to use git on a production site I would recommend git://glotpress.git.wordpress.org. My repo is more an experimental one that adds additional files for testing.

     
  • xijina 12:44 pm on February 5, 2014 Permalink | Reply
    Tags: enhancement request   

    Hello, I have an enhancement request and hopefully I’m in the right place to suggest it, but let me know if I need to create an actual ticket or move the request elsewhere.

    In order to improve as a translator and mostly to not repeat the same translation mistakes, I often go back to check on my translations and have a look at the validator’s correction, this requires some shorts steps:
    1. Enter my username (User:)
    2. Select “Rejected” or “Approved, but obsoleted by another string” (Status:)
    3. Click on the Filter button
    4. Click on Details for the string I want to inquire about
    5. Click on “All translations of this original” (open in new tab)
    6. Close tab
    7. Repeat 4-6 until I get through my list

    Repeating steps 4-6 quickly becomes painful when there’s a long list to go through, but that’s the only method I have found so far to get feedbacks on my translations, and this the reason I’d like to suggest for a way to have a quick glance at all my inaccurate translations and the final correction by the validator.

    For example, when I filter by “Rejected” or “Approved, but obsoleted by another string”, the filtered page could display an additional column, so that we’d have: Original string, Translation (could be renamed to Suggested Translation) and Final Translation. Else, what’s the point of having a list of my rejected or obsoleted strings without knowing what was wrong or what needed to be modified?

    Comments or advice are welcomed.

     
  • Yoav 9:51 am on January 30, 2014 Permalink | Reply
    Tags: glossary, new feature   

    Glossary feature: there’s some progress over on https://glotpress.trac.wordpress.org/ticket/97, and an actual patch that can be tested. Comments/reviews appreciated.

     
  • Marko Heijnen 12:05 am on January 21, 2014 Permalink | Reply  

    The last week I ported the default theme to a bootstrap theme. The translation view still needs some attention and hopefully that will be fixed this week. I’m really curious what you guys think about it. You can check it out on http://wp-translate.org/projects and you can find the code on https://github.com/markoheijnen/WP-Translate-Theme.

     
    • Martin (IQ) 12:52 pm on January 21, 2014 Permalink | Reply

      Hi Marko,

      I’m one of the german validators in the WordPress.com GlotPress. So basically I’m just a GlotPress user. I’ve no experience in setting it up or working in the backend. So bear that in mind when reading my feedback. :)

      I like the overall look and feel of it. Look a lot more like a WordPress dashboard
      I love the fact that the numbers of translated, untranslated and waiting strings are recognizable as links. I had no clue when looking e.g. at http://translate.wordpress.com/projects/wpcom
      What do you think about the ‘navbar’ height being adjusted to the one of the adminbar of WordPress?
      The contrast between font color and ‘navbar’ background isn’t very high. It’s maybe difficult to read for some visually impaired people.
      Lots of scrolling on the projects page. *hatescrolling* ;)
      The projects page is very empty. How about an extra ‘description’ column?
      For consistency I’d find it better to display the same breadcrumb navigaton (gray background) in single project view (e.g. http://wp-translate.org/projects/acf) on the projects page instead of a h2 headline (Projects)
      I’d prefer a darker background for the table head (instead of white)
      The percentage of completion is displayed twice. As a label (green) to the language column and as extra column. Redundant?
      Just like the WordPress.com GlotPress there’s no column for fuzzy strings. I only recently discovered we had a lot of them on translate.wordpress.com.
      The WordPress.org and Github links on every project could use some title attribute. Just for a little description on mouse hover
      I’d prefer a recognizable “cancel” button in translation view.
      The overall alignment in the “Filter ↑” and “Sort ↓” menus looks a bit messy. ;)

      That’s all for now. I hope it’s of any help. :mrgreen:

      • Marko Heijnen 2:39 pm on January 21, 2014 Permalink | Reply

        Hey Martin,

        Thanks for your feedback. Personally I think the navbar height should not be to small as of WordPress. The bar will get more meaning. I didn’t check accessibility yet since I have a list for that to check. Also as mentioned this is currently just a port. More work will be done.

        The scrolling part was always there but now a bit more due to the padding. Not sure what you mean with description. Like a global “what is this site about” one? Not really theme specific.

        The breadcrumbs is again the normal GlotPress behavior created in https://glotpress.trac.wordpress.org/ticket/244.

        The next things is how GlotPress is. Percentages above 90 do show duplicated labels. The WordPress/Github link is the description so content.

        As mentioned the translations page still needs a lot of work so that one is indeed still a mess. Just like the cancel button but still unsure about if it should change.

    • Martin (IQ) 3:01 pm on January 21, 2014 Permalink | Reply

      Not sure what you mean with description. Like a global “what is this site about” one? Not really theme specific.

      You’re right. On second thought this isn’t theme specific. Just to clear this up, I was talking about another column where you could display a short description of the project.

      Advanced Custom Fields | This plugin offers blablabla….
      Advanced Text Widget | Plugin description

      • Marko Heijnen 12:27 pm on January 22, 2014 Permalink | Reply

        Not sure if that is a good idea. I’m going to play with the projects page when I got the time. I got some ideas how we could use the full screen but I need to look into that

    • Robert 5:43 pm on January 21, 2014 Permalink | Reply

      Hi Marko,
      the new theme looks great! would like to test it out on my glotpress instance too.
      Can you please add some install instructions to the git repo?
      thx,
      Robert

      • Marko Heijnen 6:28 pm on January 21, 2014 Permalink | Reply

        it’s just a dropin in your plugins folder. So folder name is child-theme so it will load child-theme/child-theme.php

    • David Decker 1:07 pm on February 7, 2014 Permalink | Reply

      Awesome work, Marko!
      Any chance this could be a new default theme for GlotPress? (I hope so! :)

  • Yoav 9:06 pm on December 29, 2013 Permalink | Reply
    Tags: development, trunk, vvv   

    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.

     
  • cfoellmann 9:13 am on December 10, 2013 Permalink | Reply
    Tags: homepage, site   

    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?

     
    • Marko Heijnen 2:42 pm on December 10, 2013 Permalink | Reply

      That is something on my roadmap. I thought I blogged about that but I was wrong on that. I did mention on my own site that I want to have a downloadable zip file but we aren’t on that state yet. GlotPress first need to have some major improvements before I’m happy to have a downloadable zip file.

      But if we have that then sure we need a real site on http://glotpress.org

    • Xavier 3:24 pm on December 10, 2013 Permalink | Reply

      Couldn’t agree more. I always was surprised to see the root of this domain redirects to the project’s P2.

    • tn 5:15 pm on December 18, 2013 Permalink | Reply

      yep, landed here from another site to know something on this project but it’s not really simple… also the trac’s not so useful, since the wiki is completely blank… i’m a programmer, but not so willing to read all the source code to know what it does…

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