Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • smoliak 10:12 am on July 9th, 2012 Permalink | Reply  

    Who is the validator to the Ukrainian language?

     
  • Bage 5:34 pm on July 2nd, 2012 Permalink | Reply
    Tags:   

    Hello,

    Greetings!

    I am not sure this is the right place, but I also wish to be a validator for Tamil at WordPress.com. Please add me.

    Bage.

     
    • 4:30 pm on July 4th, 2012 Permalink | Reply

      In principle no, but it looks like a Tamil translation isn’t being maintained, aside from this Google Group (which I can’t read). It would maybe a good ideia to present the Getting Started guide to that group and see if you can gather a team for the Tamil translation.

    • Jenia 5:51 pm on July 4th, 2012 Permalink | Reply

      Bage, I see that you also posted your request on the WordPress.com Translations forum (which is the right place) – I’ve responded there, thanks!

    • Bage 11:17 am on July 6th, 2012 Permalink | Reply

      Ze, Jenai, I posted in the forums after posted here. Sorry about that. I have access now and started translating.

  • Atrax 7:46 am on July 2nd, 2012 Permalink | Reply
    Tags: , ,   

    Greetings!
    I am back to L10N-RU team.
    Please, add me as validator to all russian translate.wordpress.com / translate.wordpress.org projects

     
  • Diana 10:11 pm on June 30th, 2012 Permalink | Reply
    Tags: ,   

    The first screen when installig WordPress aren’t reached by translation: http://img546.imageshack.us/img546/7360/24179209.png

     
    • Milan Dinić 11:03 pm on June 30th, 2012 Permalink | Reply

      Either language code is missing from wp-config-sample.php or there are no translation files. Otherwise, this should be translated.

      • Andrew Nacin 11:12 pm on June 30th, 2012 Permalink | Reply

        Normally, but this screen is different. We can’t read wp-config-sample.php to check the language code (WordPress would break if we tried to include it), but we also don’t need to. Any localized release downloaded from WordPress.org not only includes a change in wp-config-sample.php for WPLANG, but also a line in wp-includes/version.php called $wp_local_package.

        So this seems to tell me that you have language files in place (based on your inquiry) but nothing in wp-config-sample.php unless you added it yourself. The only other way this page could be in English is if you updated the install into English, not removing the existing language files but removing the line from version.php, and then lost your wp-config.php file.

        Regardless, this isn’t a bug in core, and I don’t see anything we could do more effectively. It’ll work almost every time.

        • Diana K. Cury 11:34 pm on June 30th, 2012 Permalink | Reply

          So running a fresh install will always display the first screen in english? I tried the localized package and also the original (then placing files after), neither worked.

          • Diana K. Cury 11:38 pm on June 30th, 2012 Permalink | Reply

            Just in case: this is a local install and the page title get translated.

          • Milan Dinić 11:49 pm on June 30th, 2012 Permalink | Reply

            I’ve just tried Serbian version and this screen is translated which means problem is just with your package.

  • chyngyz264 2:27 pm on June 29th, 2012 Permalink | Reply  

    I have read the Getting Started, can I become a validator?

     
    • 3:32 pm on June 29th, 2012 Permalink | Reply

      It looks like you’ve missed the “Prepare your request” part…

      • chingis091 3:50 pm on June 29th, 2012 Permalink | Reply

        WordPress.org username of the administrator: chingis
        Language code: ky
        Language name, both the English and the native name: Kyrgyz, Кыргыз тил
        (if applicable) Country code: KG
        (if applicable) Country name, both the English and the native name: Kyrgyz Republic, Кыргыз Республикасы

    • 1:12 pm on June 30th, 2012 Permalink | Reply

      You’re all set, time to read “First steps: translating the Rosetta site” on the the Getting Started guide.

      • chingis091 1:52 pm on June 30th, 2012 Permalink | Reply

        Thanks for your help!

  • Rafa Poveda 10:48 am on June 29th, 2012 Permalink | Reply
    Tags:   

    Hello there.
    We need a change in this contact page: http://es.wordpress.org/contact/

    “foros WordPress en español (no oficial)” needs to change to “fofos oficiales de WordPress en español” and link to es.forums.wordpress.org.

    Thanks.

     
  • chyngyz264 1:10 am on June 29th, 2012 Permalink | Reply  

    Hi!
    I want to translate the WordPress into kyrgyz language with Pootle.
    Thanks.

     
    • 11:12 am on June 29th, 2012 Permalink | Reply

      We don’t use Pootle to translate (nor do I know how it works), I’m afraid. You’re free to do it there, if you want, but be aware that it won’t be possible to build and release a Kyrgyz WordPress package. Take a look at this post, to see how that’s done.

    • 11:23 am on June 29th, 2012 Permalink | Reply

      Kyrgyz is already supported by GlotPress, by the way.

      • chingis091 12:49 pm on June 29th, 2012 Permalink | Reply

        Who approves kyrgyz translations in GlotPress?

        • 12:52 pm on June 29th, 2012 Permalink | Reply

          No one, no team exists. Care to organize one?

          • chingis091 12:57 pm on June 29th, 2012 Permalink | Reply

            Can I start a translation without the team.

            • chingis091 1:00 pm on June 29th, 2012 Permalink | Reply

              ?

            • 1:09 pm on June 29th, 2012 Permalink | Reply

              Not recommended over time (there are *a lot* of strings), but sure, you can start alone. Just make sure you read the Getting Started instructions very carefully and make your request on a new thread. Thanks.

  • Diana 6:43 pm on June 28th, 2012 Permalink | Reply
    Tags: , ,   

    Why the BuddyPress projects never keeps past translation files, at last previous relesead versions? I just found out that the available files in GlotPress are for 1.6, while a lot of people are using 1.5.x.(that’s the version availabel in plugin directory as well). I used to keep the translation in my site but now that I’m running the br.buddypress seemed right to lead people to download files in Glot instead. Am I missing something?!

     
    • Andrew Nacin 12:29 pm on June 29th, 2012 Permalink | Reply

      It looks like 1.2.x was branched but that 1.5.x was never branched. We can do this, if you’d like, but it might need to wait for http://glotpress.trac.wordpress.org/ticket/207, as any strings removed in 1.6 but present in 1.5 would need to be re-translated for 1.5 based on a simple PO/MO export and re-import.

      • Diana K. Cury 4:31 pm on June 29th, 2012 Permalink | Reply

        Thanks Nacin, I see that many strings was changed/added, but at least for versions said stable there should be versions, i.e. 1.6 and beyond?! Now that 1.6 are about to be released there is no need to worry about the past ones indeed.

  • frilyd 3:44 pm on June 28th, 2012 Permalink | Reply
    Tags: ,   

    In Glotpress, I see 40 untranslated strings for WP 3.4 nn_NO, but the list of untranslated nn_NO strings is empty. Any ideas?

     
    • Andrew Nacin 3:54 pm on June 28th, 2012 Permalink | Reply

      Where does it say you have 40 untranslated strings? URL, screenshot?

    • Wacław J. 12:41 pm on June 29th, 2012 Permalink | Reply

      The same happens in pl_PL: https://translate.wordpress.org/projects/wp/3.4.x

      It says there are 40 untranslated strings, while in fact there are none (a caching issue I guess? I think it was already discussed somewhere).

    • frilyd 7:44 am on July 4th, 2012 Permalink | Reply

      It probably was a caching issue, because everything is OK now. Thanks!

  • Wacław Jacek 1:05 pm on June 28th, 2012 Permalink | Reply
    Tags:   

    Are non-validator translators no longer listed on the credits page?

     
    • Andrew Nacin 3:54 pm on June 28th, 2012 Permalink | Reply

      Bug on my part. Fixing.

    • Andrew Nacin 4:01 pm on June 28th, 2012 Permalink | Reply

      Ah, just didn’t deploy some code. Fixed. Credits screens hold cache for a long time, so you’ll have to clear the transient or try a different install.

  • Andrew Nacin 8:16 pm on June 27th, 2012 Permalink | Reply
    Tags: , ,   

    3.4.1 has just been released. No string changes. There is a 3.4.x project in GlotPress for you. The revision is 21156 for either tags/3.4 or branches/3.4. This is a security update, so speed is important. Cheers!

     
  • jamaljama 9:26 am on June 27th, 2012 Permalink | Reply
    Tags: , , ,   

    Zé,

    Could you please, deploy the SO translation of Browse Happy?

    By the way, “Brought to you by WordPress” in the footer is an image; untranslatable O_O

     
  • SteveAgl 8:31 am on June 27th, 2012 Permalink | Reply
    Tags:   

    Why till today on glotpress there is no 3.4 branch and 3.5 but we are still at 3.3.x and 3.4 with this last one that is a 3.5alpha? Is going to be realsed 3.4.1 and we have to struggle with version to generate packages with right tag. Since last week when i asked about it noone answered… why? Pls we need an answer

     
    • Wacław J. 9:11 am on June 27th, 2012 Permalink | Reply

      • SteveAgl 10:02 am on June 27th, 2012 Permalink | Reply

        I read it and i generated the italian 3.4 version… but i would like to get an official answer and the reasons why the glotpress is still unupdated… for year i generated the version using svn and all was under control, I was very happy for glotpress that made release easier than before.. but i would like to see more care for translation people that do a lot of work to spread the Word

    • Da^MsT 9:20 am on June 27th, 2012 Permalink | Reply

      Another reason that shows that we are definitely not ready for the full switch to GP…

      • 9:52 am on June 27th, 2012 Permalink | Reply

        For all purposes we already did, I’m afraid.

    • 9:51 am on June 27th, 2012 Permalink | Reply

      Because it takes time and we all have other lives that need tending to. Also, I wouldn’t describe finding the appropriate svn revision number as a “struggle”, it’s a simple process. Be it as it may, we’re working on it.

      • SteveAgl 10:05 am on June 27th, 2012 Permalink | Reply

        That take time i can agree… taht you have other lives… but it’s a non answer… all translation team try to give local version as fast as possible… we do on volunteer basis… if after the release someone wrote here explaining that glotpress will be updatedin weeks and why… noone would have said a word… i already asked about this problem and noone ansered but some other volunteer did… anyway thank for the answer

      • Wacław J. 10:06 am on June 27th, 2012 Permalink | Reply

        It would be nice if the GP branch (“project?”) was created ASAP though (but no pressure), so that strings that go missing during the development of 3.5 don’t get lost.

    • Andrew Nacin 2:56 pm on June 27th, 2012 Permalink | Reply

      There’s no 3.4.x project yet because I wanted to make sure we created the “branch” in a way that is smarter than what we’ve done in the past. Basically, I want to prevent you guys from re-importing everything into the branch, which is no fun, as well as maintaining history in a better fashion than the current pomo import.

      No strings have been touched in 3.5 yet, and I actually paused the script to prevent trunk from overwriting things until we branch in GP. This should go ahead soon.

  • Andrew Nacin 6:39 am on June 26th, 2012 Permalink | Reply
    Tags: ,   

    [ Edit: I no longer need an answer to this question. ] All translators — Did anyone have a locale.php file (like ru_RU.php) in 3.3 that they no longer included in 3.4? If so, what is your locale? Those files are going to sit there (and be included) after an upgrade, so we need to remove them manually: http://core.trac.wordpress.org/ticket/20974. Unfortunately it is not easy to ascertain which locales used to have them but no longer do.

     
  • DjZoNe 7:28 am on June 25th, 2012 Permalink | Reply
    Tags: , , 3.5,   

    Hi, when will be a 3.4 sub-project created on GlotPress?

    Because, if I build a package from development branch, it will end up with 3.5-alpha package, and the next branch is 3.3, which will end up a 3.3.2 package…

     
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