Updates from January, 2012 Toggle Comment Threads | Keyboard Shortcuts

  • stefangabos 8:49 pm on January 11th, 2012 Permalink | Reply
    Tags:   

    Hi, I would like to help translating to the Romanian language which, for the most part, is translated word by word, without context and without proper meaning. Can you make me a translations “validator”? I speak fluent Romanian and English. I’m at stefangabos.ro. Thanks!

     

    • Zé 12:10 pm on January 13th, 2012 Permalink | Reply

      Coud you contact the Romanian team with your request first? Thanks.

      • Stas Sușcov 4:09 pm on January 13th, 2012 Permalink | Reply

        @vanillalounge could you add @stefangabos as a validator for wp.com?
        He is interested in correcting out contributions from wp.com users. He didn’t explain that in the initial post, so I was confused.

        Thanks in advance!

    • Stas Sușcov 12:40 pm on January 13th, 2012 Permalink | Reply

      Thanks @vanillalounge
      @stefangabos I will email you asap. Please, in future don’t be so rude when speaking about volunteers work, it makes ugly the whole concept of community people are trying to build here.

  • Akerbeltz 2:40 pm on December 13th, 2011 Permalink | Reply
    Tags:   

    A question about the main http://wordpress.org/ website – how is a user supposed to know there are localized versions of WP? There don’t seem to be any links. For some reason, I get a yellow box suggesting it’s available in German but German is way below Gaelic (the order I’m using is gd, en, de) in my preferred languages setting in Firefox and even if, not everyone who might want WP in language X uses a browser in language X. Am I missing something or is that just an oversight?

     

    • Nikolay Bachiyski 12:43 pm on December 15th, 2011 Permalink | Reply

      This should be fixed now: http://cl.ly/CdIk

      • Akerbeltz 12:59 pm on December 15th, 2011 Permalink | Reply

        Ok, the autodetect is fixed, thanks very much. But is there a static link to some page where people can browse through the available releases? Not everyone has the right language settings adjusted correctly.

        • Zé 1:28 pm on December 15th, 2011 Permalink | Reply

          • Nikolay Bachiyski 2:15 pm on December 15th, 2011 Permalink | Reply

            @vanillalounge, he means all available languages, I guess.

            @akerbeltzalba, such a page has been on the TODO list for some time 🙂 We will get there some day.

            • Akerbeltz 4:17 pm on December 15th, 2011 Permalink | Reply

              Yes, that’s what I mean. Here, many people don’t use a Gaelic browser and unless they know the gd.wordpress page, they won’t know it exists. Will be the case for many other locales too.
              @Nikolay I look forward to it – can’t be hard to write though, it’s just a “list” – currently a bit like creating an art gallery and then hiding most paintings in the basement behind the boiler 😉

  • Andrew Nacin 8:50 pm on December 2nd, 2011 Permalink | Reply
    Tags: ,   

    We’re in string freeze.

    Heads up on timing: We’re aiming to release 3.3 final before December 13.

    Please post here and use the “core” tag if there are any issues, typos, etc. If we need to change a string, I will post here (and beg for forgiveness). Tickets with potential string changes will be marked with the ‘i18n-change’ keyword.

     

    • Mattias Tengblad 10:18 pm on December 2nd, 2011 Permalink | Reply

      Before is when?

      • Andrew Nacin 2:42 am on December 3rd, 2011 Permalink | Reply

        We haven’t discussed the timing yet, but RC is going well. We will be in RC for at least a week and translators will have at least one weekend. At the time of this writing, 41 languages are at greater than 90%, so it seems things are in very good shape.

        • Mattias Tengblad 3:53 am on December 3rd, 2011 Permalink | Reply

          Sounds good. Please remember to notify us something like 12 to 24 hours before release 🙂

    • Akerbeltz 10:35 pm on December 2nd, 2011 Permalink | Reply

      What’s the deadline for translations? I have all done bar core which is at ~60% – keeps fluctuating cause someone keeps dumping new strings in it 😉
      I note that quite a lot of locales are in the same broad area… what’s the deal here if you don’t have 100% on the cutoff day? Sorry for the noob questions, not been through a l10n release on wordpress before.

      • Zé 10:40 pm on December 2nd, 2011 Permalink | Reply

        You don’t need to release at the exact same time, especially not if it’s the first time WordPress is translated into a particular language. Just translate at you normal pace and release when you’re ready. (and by the way, “string freeze” = “no one dumps new strings”. If there are new strings, @nacin buys everyone drinks)

    • Andrew Nacin 3:53 am on December 3rd, 2011 Permalink | Reply

      First “string” change is likely to be this: http://core.trac.wordpress.org/attachment/ticket/19427/19427.diff. I would beg forgiveness, but I’ll save that for string changes that will actually affect your amount of work. 🙂

      • Zé 4:19 pm on December 3rd, 2011 Permalink | Reply

        I’ll have a beer

    • Kenan Dervišević 12:35 pm on December 3rd, 2011 Permalink | Reply

  • Remkus de Vries 6:17 pm on August 23rd, 2011 Permalink | Reply
    Tags: ,   

    Oy,

    How can we have the translations updated on our xx.wordpress.org sites? I’d love to see the fruits of my labor in fy.wordpress.org and nl.wordpress.org. As long as we don’t have any language packs just yet, the only thing I can do is bug you @vanillalounge ?

     

    • Zé 6:52 pm on August 23rd, 2011 Permalink | Reply

      By ‘translations’ I assume you mean a fresh rosetta.pot? If so, I’m on it.

    • Remkus de Vries 6:57 pm on August 23rd, 2011 Permalink | Reply

      I actually meant the actual translation in Dutch and Frisian I see when I am logged into those websites.

      • Zé 6:59 pm on August 23rd, 2011 Permalink | Reply

        • Remkus de Vries 7:03 pm on August 23rd, 2011 Permalink | Reply

          I somehow always think of the extra stuff – like the deploy stuff – on the international sites as the rosetta.pot. Not the actual translations we create in GlotPress .. but hey, if that’s what you mean, go for it 😉

          • Zé 7:13 pm on August 23rd, 2011 Permalink | Reply

            rosetta.pot is a superset of WordPress, i.e. it’s WordPress (duh) with a few additional features, like deploy requests and the packaging and releasing of downloadable versions.

  • Dreamcolor 2:39 am on July 21st, 2011 Permalink | Reply
    Tags: ,   

    Hello Zé,

    I’m a validators of BuddyPress for a long time, and I’m the maintainer of BuddyPress China (cn.buddypress.org) from BP 1.0.

    But today when I wanna to import my translations to glotpress, I found that my permissions was been removed.

    There wasn’t any notices and reasons.

    Could you tell my way? And how to restore my permissions?

    I really don’t want my long time works been finished without any reasons. And I hope somebody can friendy to handle this case.

    Thank you so much.

     

    • jiehanzheng 3:23 am on July 21st, 2011 Permalink | Reply

      Validators are now controlled through Rosetta

      Sorry. I did this because I thought the permission settings in the Rosetta site only applies to WordPress projects — therefore I removed you from the list.

      Let’s ask @vanillalounge if there’s any way to make these permissions per-project. Before we get a solution, I will add you back. But please do not import your translation for other projects again.

      My apologies,

      Jiehan

      • Dreamcolor 8:53 am on July 21st, 2011 Permalink | Reply

        As you said, I can ensure that I won’t import my translations.

        And I found that bbPress still have so much work havn’t proof. I already finish the translation for a long time and request for the validator for three times. Could you add me into that?

        You just need to tell me which project I shouldn’t to touch. I won’t to make any obsession to you.

        • jiehanzheng 3:53 pm on July 21st, 2011 Permalink | Reply

          Once I promote you to Validator, you will have access to ALL these projects. Please, again, do not import translations to any projects other than BuddyPress, which you are originally in charge of.

          However, you may translate them one-by-one using your validator account, if the person in charge of the language allows so. If they don’t, you can still feel free to make translation suggestions with another account which is not a Validator. For detailed permission information and contact info of validators, please refer to:
          http://cn.wordpress.org/validators/

          May I have your email address for your WordPress.org account to get proceed?

      • Andrew Nacin 6:12 am on July 22nd, 2011 Permalink | Reply

        We don’t plan to implement per-project permissions at this time.

        • Mattias Tengblad 6:29 am on July 22nd, 2011 Permalink | Reply

          Not good :/ Why isn’t things like this discussed with the translation team before it’s implemented?

          • jiehanzheng 9:18 pm on July 22nd, 2011 Permalink | Reply

            I agree with you. This mechanism change caused a little collaboration problem.

  • suscov 5:56 pm on July 5th, 2011 Permalink | Reply
    Tags: ,   

    Hey Zé, please remove de-ce from moderators for ro_RO.
    Thank you.

     

    • Zé 11:16 pm on July 5th, 2011 Permalink | Reply

      ‘moderator’ (forums) or ‘validator’ (GlotPress)?

      • Stas Sușcov 12:18 am on July 6th, 2011 Permalink | Reply

        Uh, validator please.
        Thanks.

        • Zé 12:22 am on July 6th, 2011 Permalink | Reply

          Done.

          • de ce? 11:53 am on February 21st, 2012 Permalink | Reply

            I want to be back on the team 🙂 (de-ce)

            • Stas Sușcov 12:37 pm on February 22nd, 2012 Permalink | Reply

              Hey @vanillalounge
              I had a skype chat with @de-ce and he seems interested in coordinating our team (which right now has nobody as responsible for translations).

              Could you please add him back as validator (GlotPress) for ro_RO.
              Thanks.

              @de-ce please leave a post on this blog once you get validator rights, and introduce yourself as coordinator for ro_RO. Also feel free to ping me anytime you need help with infrastructure or other details.

              Thanks.

              • Zé 1:56 pm on February 22nd, 2012 Permalink | Reply

                As per Skype chat, all this is done.

  • xavier 10:02 pm on June 12th, 2011 Permalink | Reply
    Tags: potbot, ,   

    About Twenty-Ten: Wondering whether “, ” was a list separator or a numeric separator (y’know, 1, 000.55 and all that), I went into the theme’s code, and sure enough, there was a “translators:” indication… but somehow potbot doesn’t integrate it into the POT. Could that be resolved, so as to help us get a quicker grasp of the context for a string?

    Thanks guys!

     

  • suscov 12:57 pm on June 8th, 2011 Permalink | Reply
    Tags: , ,   

    @vanillalounge could you please remove `c00l2sv` from Romanian validators on GlotPress.
    Thank you.

     

    • Stas Sușcov 1:02 pm on June 8th, 2011 Permalink | Reply

      Also please remove niladam from validators.
      People that should have left are:

      grammarfreak
      cheeprey
      de-ce
      and me sushkov

      Some 3.2 cleanup.

      Thank you.

  • jiehanzheng 12:00 pm on June 8th, 2011 Permalink | Reply
    Tags: , , ,   

    This post concerns the Chinese Credits page. Hope @nacin and @vanillalounge or anyone else this may concern could take a look.

    First I am happy to see that the Chinese separator (“、”) is in place on the contributor’s list, but there’s an imperfection that in Chinese we use “。” rather than “.” to indicate the ending of a sentence. So I have one suggestion: to substitue “.” with “。”, or you can just remove the ending period.

    I just discovered that this is managed by the po translation files. So no need to fix on the API side. Sorry for this. Please see my next issue:

    Another thing I want to report is that the current translator list is inaccurate for Chinese. I don’t know how about other languages, but for Chinese it is not. None of the current 4 “validators” indicated on the Credits page is a currently active validator. It should have jiehanzheng (me) for WordPress, and musiclog for bbPress Plugin. kingler and Paveo also worked on WordPress, but they no longer do. Please help remove those who are inactive if possible.

    Thank you.

     

    • Zé 10:57 am on June 9th, 2011 Permalink | Reply

      kingler and Paveo (and jtam) were removed.

  • herzcthu 8:31 am on June 4th, 2011 Permalink | Reply
    Tags:   

    Hi everyone,
    I’m editing Translator’s Handbook. Posting it here. I hope this will help new comers and anyone who want to start translating WordPress.
    Any experienced person’s suggestion is welcome. Actually I also am a beginner at WordPress translation. So some information may be wrong. So need correction or suggestion.

     

  • jiehanzheng 1:01 pm on May 27th, 2011 Permalink | Reply
    Tags: , ,   

    Hi. Could you please list all validators of the zh_CN WordPress core project in GlotPress? I found that there are many strange strings who don’t have a “Translated by” field and were not translated by me. It seems that they were imported, but as far as I know, other validators (Paveo and kingler) are no longer working at WordPress.

    Although I am going through all the thousands of translations but I am eager to figure out where did stings like this come from in order to prevent such conflict and overriding in the future.

     

    • Dreamcolor 1:05 pm on May 27th, 2011 Permalink | Reply

      It’s me. I did that. I had imported all those strings.

      • jiehanzheng 1:22 pm on May 27th, 2011 Permalink | Reply

        I wonder when and how you became a validator of the core project. Please don’t simply import your translation again, since that will override all the existing strings, and your expression for some words is kind of different from those existing. I think translate or modify them one-by-one is more acceptable. Thank you.

        Another example is that I replaced most of the links to English Codex articles by links to Chinese Codex articles, and your import just wiped them off and I have to revert to my previous translations one-by-one.

        • Dreamcolor 1:53 pm on May 27th, 2011 Permalink | Reply

          Sorry about that. I just found that so many strings did not being translated. So I did that. OK, I won’t do that again. And I do.t know when and how I became a validator. If you feel not good. You can ask administrator to remove my permission. I just wanna to help. If you didnt need that. I stop. Sorry again.

          BTW, should I become a validator of bbPress? I already 100% finish the translation of it.

          • jiehanzheng 3:49 pm on May 27th, 2011 Permalink | Reply

            @vanillalounge: as he stated, I hope his validator status at WordPress core could be revoked if possible.

            My suggestion for GlotPress is not to directly overwrite any existing strings when importing, instead, mark them as waiting when there are conflicts, to prevent such incident from happening again. Reviewing all translations is really a heavy work that can take days.

            @Dreamcolor: I really appreciate your help. I am open to any suggestions from the community and, as many can see, I always reply and process every email, forum post and comments on cn.wordpress.org regarding translation mistakes carefully and correct them as soon as possible, but to some extent I can not stand such suggestions that overrode all of my existing work that will cost much of my extra time to fix.

            However, please believe that I will be reviewing all the strings, and I will keep those who are better than existing ones.

            • Zé 8:48 am on May 28th, 2011 Permalink | Reply

              It’s now revoked

              • Gregorovius 9:34 pm on May 28th, 2011 Permalink | Reply

                My suggestion for GlotPress is not to directly overwrite any existing strings when importing, instead, mark them as waiting when there are conflicts

                I agree with ‘jiehanzheng’ in this suggestion, since we are three validators for Galician in WordPress.com. And I wouldn’t like to see my work of two years deleted with a single upload.

                • herzcthu 2:28 am on May 29th, 2011 Permalink | Reply

                  It would be great if only one person has full rights to review all others’ works. New role like “language coordinator” or “project leader” may resolve this.

                • jiehanzheng 3:48 am on May 29th, 2011 Permalink | Reply

                  Just to be accurate, they won’t be deleted but marked as “Old.” Then we will have to double-click on all the translations, then “All translations of this original,” double-click on your translation again, and “Approve” our translations. This process will need tens of thousands of mouse clicks.

                  • Gregorovius 9:04 am on May 29th, 2011 Permalink | Reply

                    When translation is made on line and approved in GlotPress, it saves previous strings as Old. But seems that when a PO file is uploaded, this action deletes the entire history.
                    Either way, from now I will save a PO file each time I add a new string, in order to facilitate the restore if there is a similar situation.

  • suscov 5:40 pm on May 26th, 2011 Permalink | Reply
    Tags: ,   

    Now that we have 3.2 on XX.wordpress.org, can we have those grunion contact forms? Please please…
    cc @nacin @vanillalounge

     

    • Zé 8:36 am on May 31st, 2011 Permalink | Reply

      As per IRC conversation earlier, I vote for making the existing contact form an option, and leave grunion out of this altogether.

  • ipapu 5:39 am on May 25th, 2011 Permalink | Reply
    Tags: ,   

    Would you please add the chineses language(zh-cn) support for bbPress in GlotPres? With musiclog as validator. I wish I could do something for this amazing project. 🙂

     

    • Zé 2:17 pm on May 25th, 2011 Permalink | Reply

      zh_CN now exists for bbPress, but I’d like to have @jiehanzheng feedback in what concerns validation perms. Thanks.

      • jiehanzheng 2:28 pm on May 25th, 2011 Permalink | Reply

        Thanks for notifying me, @vanillalounge. I think it would be nice to add someone to help validating strings of bbPress Chinese translation. I wonder if it is possible to apply the permission to bbPress only, since I can handle validating WordPress core translations. 🙂

        @ipapu: but… just to remind you that please add a space between Chinese characters and English words; and please get familiar with WordPress core translations by actually using it — in order to keep coherence of some particular terms with existing core translations (e.g. “Posts”, “Categories”, “Permalink”, “RSS feed”, etc.). Thanks for your help!

        • Zé 11:27 am on May 27th, 2011 Permalink | Reply

          Absolutely, permission are per-project, not language wide. You and ‘musiclog’ are now validators for the bbPress project.

    • ipapu 2:44 pm on May 25th, 2011 Permalink | Reply

      @jiehanzheng Thanks! I didn’t have much experience and I appreciate your help and guidance. I will try my best and I wish someone can help to correct the improper translation I’ve made. Bbpress is enough for me to start with, thanks!

  • Andrew Nacin 9:04 pm on May 23rd, 2011 Permalink | Reply
    Tags: , ,   

    The WordPress Credits page (wp-admin/credits.php, new in 3.2) shows the list of translators for the active locale. There are a few things you need to know:

    • There is a string “Translators” with the context of “Translate this to be the equivalent of ‘English Translators’ in your language for the credits page Translators section”. Please do as requested.
    • The names are pulled dynamically from GlotPress. It is designed to show anyone who has contributed an approved string for the current release. (If something doesn’t feel right, let me know.)
    • Please update your display name in your WordPress.org profile. It will use this if present, but please note that UTF-8 characters are not currently allowed. (Known limitation.) The data is cached both in core and on the API server, so updates won’t be immediate.

    Happy translating,
    Nacin

     

    • Milan Dinić 10:35 pm on May 23rd, 2011 Permalink | Reply

      Thank you!

      The names are pulled dynamically from GlotPress. It is designed to show anyone who has contributed an approved string for the current release. (If something doesn’t feel right, let me know.)

      There are translators who are the only one working on their language and who use SVN only, so it would be better to also include validators from GlotPress too, or those who committed on SVN for that locale.

      But even GP thing doesn’t work perfect, I import PO files in it (which means strings are approved since I’m validator) and I’m not shown.

      And one bug: if there are no translators, there shouldn’t be ‘translators’ slug in API response (as in en_US) since there will be errors “Warning: array_walk() [function.array-walk]: The argument should be an array in wp-admin/credits.php on line 100” and “Warning: shuffle() expects parameter 1 to be array, string given in wp-admin/credits.php on line 101”

      • Andrew Nacin 10:48 pm on May 23rd, 2011 Permalink | Reply

        SVN will not be supported. I would argue that the reason why they’re the only person on their language is because, in part, they’re not working in the open with GlotPress.

        I’ll look into supporting strings you import, thanks.

        I’ll check on the bug. In which locale are you seeing the warnings?

        • Milan Dinić 11:02 pm on May 23rd, 2011 Permalink | Reply

          In which locale are you seeing the warnings?

          sr_RS

          I would argue that the reason why they’re the only person on their language is because, in part, they’re not working in the open with GlotPress.

          Every language is on GP and anyone can submit translations. But that doesn’t mean that there will be community around that translation project. Many languages are small and one can’t except that in all of them there will be many people working on it since translating WP nowadays requires a lot of work and knowledge.

          • Andrew Nacin 6:13 pm on May 24th, 2011 Permalink | Reply

            The warnings are fixed – the API was returning invalid data.

            In the end, the strings need to be in GlotPress. In your case, you’re importing them. That will be supported. Pure SVN will not.

      • Remkus de Vries 12:14 am on May 26th, 2011 Permalink | Reply

        Now thát is a cool feature. I just checked to see what that looks like, but I think a seperation between a list of Validators follewed by contributors would look even better. I don’t how this is with other languages, but in our case the validators do the bulk of the work …

        • Andrew Nacin 1:10 am on May 26th, 2011 Permalink | Reply

          Thought about that, but I’m not sure if it’s necessary. Not to discount the work of the validators, but our contributors are all listed together, whether they’ve submitted a single patch to fix a typo, or dozens of major code contributions.

    • Remkus 1:16 am on May 26th, 2011 Permalink | Reply

      Necessary is a big word, but greatly appreciated, yes! Having the validators in plain sight would also help in making that person / team more visible to the dedicated user group and isnt’t that what the credits page is all about?

      • Mattias Tengblad 12:43 am on May 27th, 2011 Permalink | Reply

        +1

      • herzcthu 3:44 am on May 27th, 2011 Permalink | Reply

        At least, should be visible user avatar of validator as in core developer group and show as validator in bracket.
        And one thing is all names in contributors list and translators list are very close to each other. It is not looking good and difficult to see clearly. Should be some space in each name.

      • Peter Holme 3:43 pm on May 27th, 2011 Permalink | Reply

        +1, will make it easier to spot who’s responsible for releases as well (I’d guess)

  • jiehanzheng 4:42 pm on April 22nd, 2011 Permalink | Reply
    Tags: , , ,   

    @vanillalounge, please take a look at this: https://wppolyglots.wordpress.com/2011/04/20/may-i-ask-for-a-new-locale-association/ Thank you.

     

    • Zé 12:35 am on April 23rd, 2011 Permalink | Reply

      I had seen it already, yes. Please don’t duplicate threads if at all possible. A suggestion (to all) is to just tag your post as “pending” so that it doesn’t get lost in the paging. Thanks.

      • jiehanzheng 4:53 am on April 23rd, 2011 Permalink | Reply

        It seems that the entry is now in place. Thank you! I apologize for any inconvenience and I’ve just tagged a post posted months ago, regarding a connectivity problem, as “pending.”

        For the support forum, we are still getting several spam posts every day. Although we do manual removing, spam posts are messing up the tag cloud on the forum home page. Could you please give me a higher permission on the forum so that I will be able to clear the cache.

        Another problem is I don’t have access to the spam / pending list under bb-admin.

      • jiehanzheng 4:38 pm on April 24th, 2011 Permalink | Reply

        Oh. It seems that the lang-guess-ajax.php for the forum is still not working properly under some circumstances. For instance I can get the correct prompt on my iPhone, but I keep getting a link to tw.forums.wordpress.org when I access http://wordpress.org/forums on my laptop.

        http://wordpress.org/lang-guess/lang-guess-ajax.php?uri=%2Fsupport%2F&latest=

        My Accept-Language field in the request is en-US,en;q=0.8,zh-CN;q=0.6, and my IP address is 124.126.225.85. Then I did some dubugging — when I use cURL to get the response, which does not send the Accept-Language field, I can get the correct prompt for our Chinese forum.

        My assumption: the Accept-Language judgement is malfunctioning; as the IP geo-location works fine.

        • Zé 9:51 pm on April 25th, 2011 Permalink | Reply

          I’ll look into it, but experimenting with HTTP Client (which is incredibly useful in general), returns “WordPress is also available in 中文(简体), for me, with the same Accept-Language as above.

          • jiehanzheng 1:06 pm on April 27th, 2011 Permalink | Reply

            Seems that this problem occurs only when I use Chromium browser. And what’s more strange is that for the WordPress.org homepage, download page and the Forums, I get two different language guess results. I will do a tcpdump tomorrow and I will get in touch with you once I have results. No need to spend time on this. Thank you so much.

← 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