WordPress.org

Ready to get started?Download WordPress

Translate WordPress

Tagged: svn Toggle Comment Threads | Keyboard Shortcuts

  • BredeBS 5:15 am on April 17, 2014 Permalink | Log in to leave a Comment
    BredeBS • cl.wordpress.org editor
    Tags: , branches, , svn   

    Hi I need to create the Branches 3.9 for es_CL, but I think I don’t have any access to the SVN.
    Thanks!

     
  • Jurica Zuanović 7:41 pm on January 17, 2014 Permalink | Log in to leave a Comment
    yuraz • hr.wordpress.org editor
    Tags: , , svn   

    I have a request for changing Croatian locale from current ‘hr’ to ‘hr_HR’.

    The reason why I’m asking this is because lately I’m getting a lot of complaint from developers and plugin/theme translators about Croatian local code ‘hr’ and requests to be changed to ‘hr_HR’ language country code.

    Back in 2007 when previous administrator requested creating Croatian local site there was an error in the request. Requested stated just ‘hr’ ISO 639 language code without ‘HR’ ISO 3166-1 country code.

     
    • Ze Fontainhas 1:11 pm on January 24, 2014 Permalink | Log in to Reply

      This is not a trivial change, as there would be no more update notifications for sites with the language set to ‘hr’. Also, the country code (‘HR’) is only needed where disambiguation is needed, for example when the language varies significantly from one location to the other, which is not the case for Croatian, as far as I can tell.

      What kind of complaints are you getting, specifically?

    • vipteam 12:12 pm on March 28, 2014 Permalink | Log in to Reply

      I understand that this is not a vital issue. But this is not any rocket science. Make a transitional period where the update go to “hr” as well as “hr_HR”. This is possible to do. Also, in the Admin Dashboard can go a notification that will alert the user to this change.

      I have so far translated over 70 complex translations. I have experience in this.

      Many languages ​​also do not have significant differences. But they are properly labeled.

      Poedit foresaw this possibility. Here they entered the old (incorrect) and the new (correct) labeling.

      Croatian — hr
      Croatian (Bosnia and Herzegovina) — hr_BA
      Croatian (Croatia) — hr_HR

      Also, it is not true that the Croatian language no significant differences. There is a Croatian language spoken by Croats in Herzegovina. And there are differences. And that is a large number of the population.

      Error in the past that has been made in the rashness should not be continued forever.

      Thanks in advance

      • Ze Fontainhas 10:32 pm on March 28, 2014 Permalink | Log in to Reply

        this is not any rocket science

        Not sure if sarcasm or just not reading my response above…

        It’s perfectly ok to have hr_BA, we can do that now, assuming there are volunteers to maintain it. As far as the hr code by itself is concerned, you still haven’t made a compelling argument for changing it, aside from unspecified complaints from developers and plugin/theme translators. If you could detail what those are, it would help.

        In short, why can we not keep hr, and add hr_BA if requested?

    • vipteam 8:44 am on March 29, 2014 Permalink | Log in to Reply

      Hi Ze,

      Around the complaints I did not write. I have just followed up on this. For me, anyway. Translation is a translation. Regardless of the extension. A person who translates everything but uneducated novice. There should be no complaints if anyone knows what works and what extension he would choose.

      Rocketry. It really is my sarcastic remark. But not in a negative sense. I would like to say that there is no technical obstacle to the error of the past can not be corrected.

      All right. I agree that it can leave “hr”. It can be added “hr_HR” and “hr_BA”. First, because it is correct and the other as needed.

      I constantly want to say that “hr_HR” necessary simply because this is correct. “hr” is not used anywhere else. “hr” does not exist. Only in WordPress.

      As I wrote above, it is not of vital importance. But it correctly.

      Finally, I just now see your willingness to change something here. In your last message, I had not noticed.

      Thanks in advance.

    • inWebhr 4:00 pm on April 12, 2014 Permalink | Log in to Reply

      Ze Fontainhas,

      a I agree with boys…there is a huge problem with new WordPress developers in Croatia who can’t figure it out which one to use… hr or hr_HR. Even some translation plugin provide support for hr_HR but at this time they are useless, and still developers are wasting their time finding ways to solve this incompatible problem.

      My opinion is that there should be support for “hr”, but you should integrate support for hr_HR cause this will be a problem for future WordPress community.

      Regards

  • dyrer 6:44 pm on January 15, 2014 Permalink | Log in to leave a Comment
    dyrer • el.wordpress.org editor
    Tags: svn,   

    Hello, I have problem with Locale branch for dist files:
    Is there any problem or just me

     
  • erralin 2:25 pm on November 5, 2013 Permalink | Log in to leave a Comment
    erralin • eu.wordpress.org editor
    Tags: , , svn   

    I can edit the translations in glotpress, I can also edit our locale’s site (eu.wordpress.org), but when writting to the SVN to update the common files, I get::

    svn: E175013: Commit failed (details follow):
    svn: E175013: Access to ‘/!svn/me’ forbidden

    Can someone check my svn writing permissions?

    Thank you,

     
  • Jiehan Zheng 3:47 pm on May 24, 2013 Permalink | Log in to leave a Comment
    jiehanzheng • cn.wordpress.org editor
    Tags: , svn,   

    Hello,

    I am handing over my job to Jimmy Xu (WP.org username: jimmyxu). I’ve already granted him Editor permission on cn.wordpress.org. Would you please grant him SVN permission to i18n repos? Thanks.

     
  • Milan Dinić 8:13 pm on December 7, 2012 Permalink | Log in to leave a Comment
    dimadin • sr.wordpress.org editor
    Tags: me_ME, , svn   

    If I didn’t make a mistake today and needed to do svn update, I probably wouldn’t notice (until after I make a release) that @vanillalounge made fatal mistakes related to Serbian dist files.

    In [20648] and [20903] he obviously wanted to add support for some features we have over at Serbian locale to Montenegrin one, but he made changes to Serbian files that could have affected us.

    I reverted those changes for Serbian but wanted to note that Montenegrin is still missing me_ME.php since it wasn’t copied as wp-config-sample.php was in [20649].

    When you want to fork, you need to make a copy first, and then make changes to that copy, not to original.

    Be careful in the future, @vanillalounge. ;)

     
  • Eivind Ødegård 2:10 pm on December 14, 2011 Permalink | Log in to leave a Comment
    meinmycell • nn.wordpress.org editor • nb.wordpress.org validator
    Tags: , , svn   

    OK. So I have completed the 3.4 translation for nn_NO, re-populated 3.3 and all subprojects with the strings from 3.4 in Glotpress… Now what? I have to do something in svn to make a 3.3 tag, so I can build 3.3 from Rosetta? I fear to go into those mines.

     
  • cubells 7:00 pm on December 4, 2011 Permalink | Log in to leave a Comment
    Cubells • ca.wordpress.org editor
    Tags: delete, svn,   

    I have a problem with svn. I can’t delete tags on server.
    Localy I delete with:
    $ svn delete –force any-dir/
    but when I update the server with
    $ svn update
    the files on server remain.
    It’s a serious problem because I’m preparing the new WordPress version.

     
  • erralin 6:09 am on October 17, 2011 Permalink | Log in to leave a Comment
    erralin • eu.wordpress.org editor
    Tags: svn   

    I’m requesting SVN commit access in order to help to translate WordPress into Basque (eu)

     
  • Samúel Jón Gunnarsson 12:08 pm on October 16, 2011 Permalink | Log in to leave a Comment
    samueljon • is.wordpress.org editor
    Tags: , svn   

    I’m requesting SVN commit access in order to translate WordPress to Icelandic.

     
  • Jiehan Zheng 5:41 pm on October 15, 2011 Permalink | Log in to leave a Comment
    jiehanzheng • cn.wordpress.org editor
    Tags: , svn,   

    Hi there.

    The current JavaScript code for counting words in editor ignores Chinese characters, so I am working on a patch which I intend to ship with future cn.wordpress.org packages.

    It seems that the easiest fix is to enqueue a modified wp-admin/js/word-count.js. Is it okay to put a modified version under the corresponding SVN dist/ directory, and get the original word-count.js replaced, OR I have to put it under wp-content/languages/ and play around with the hook to make it be queued to load?

    Thank you.

     
    • 11:10 pm on October 16, 2011 Permalink | Log in to Reply

      Conceptually, I’d argue that the first option (replacing the original word-count.js) is changing core code, and hence recommend against it. That said, it also depends on what you mean by “play around with the hook to make it be queued to load”. Completely personal and subjective opinion, of course, would love to hear more from the others.

      • jiehanzheng 11:43 pm on October 16, 2011 Permalink | Log in to Reply

        Okay then the first option is out. The real issue is that the built-in word counting function is not working for Chinese characters. By “play around with the hook to make it be queued to load” I mean I intend to include a zh_CN-word-count.js or something else and add a few lines of code in zh_CN.php to make it be loaded and deregister the original word-count.js so that the original core code remains intact and we can make the word counting work when WPLANG is defined as zh_CN in wp-config.php.

    • Naoko 1:25 am on October 17, 2011 Permalink | Log in to Reply

      Japanese package includes a fix for this as a plugin:
      http://wordpress.org/extend/plugins/wp-multibyte-patch/
      If you’re interested, I’d be happy to help the author translate the whole thing but here’s Google translated version of the description page:
      http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http%3A%2F%2Feastcoder.com%2Fcode%2Fwp-multibyte-patch%2F

      • Nikolay Bachiyski 3:32 pm on October 17, 2011 Permalink | Log in to Reply

        @jiehanzheng, I would recommend you do what the Japanese guys did. It’s working great.

        • jiehanzheng 8:13 pm on October 17, 2011 Permalink | Log in to Reply

          Cool. Thank you for your advice. So for the plugin solution, am i supposed to include a copy of the plugin under SVN dist/wp-content/plugins/? Who should be the plugin author, and may I have a WordPress.org account with the name wordpresschina?

          I will look into it, see how it works during the upcoming school long weekend and hopefully include the fix before our next release. I will post any updates here.

      • jiehanzheng 8:14 pm on October 17, 2011 Permalink | Log in to Reply

        Thank you so much, Naoko. It’s a pretty nice idea because of the similarities of Japanese characters and Chinese characters. I will look into it.

        The Google Translate version is… to some extend, readable. So thank you for your offer and I will do the research.

  • Umbrovskis.com 9:52 am on October 11, 2011 Permalink | Log in to leave a Comment
    rolandinsh • lv.wordpress.org editor
    Tags: , , svn   

    Hi! I’m new to WordPress language translations upload to SVN. Somehow I am getting error “access to ‘/wordpress-i18n/!svn/act/—here is some alphanum string—’ forbidden”. I was trying with my username and password. Username: rolandinsh. I have experience with plugin’s SVN and there are no problems. Followed instructions on http://codex.wordpress.org/Translating_WordPress#WordPress_Localization_Repository

     
  • carledug 4:41 pm on September 20, 2011 Permalink | Log in to leave a Comment
    carledug
    Tags: , svn   

    Hi Zé,

    I am just trying to commit the very first strings of sa_IN but all I get here are some svn error messages:

    svn: Commit failed (details follow):
    svn: access to ‘/wordpress-i18n/!svn/act/8d0ce61a-d96e-465f-9e55-7b52327be330′ forbidden

    (my svn software is ok, as I’ve committed a plugin yesterday with no warnings or restrictions).
    Still using my .org username and password…

    Thanks for any clue

    P.S.:
    I suppose Sanskrit files will show up at http://translate.wordpress.org/projects as soon as I manage to commit them, is that right?

     
  • 11:37 am on July 25, 2011 Permalink | Log in to leave a Comment
    RanH
    Tags: , svn   

    Can we give “ramiy” access to he_IL in the i18n svn?

     
  • Ze Fontainhas 1:54 am on July 21, 2011 Permalink | Log in to leave a Comment
    vanillalounge • pt.wordpress.org editor
    Tags: , , svn   

    @Massimeddu, http://srd.wordpress.org is up and running and so is http://i18n.svn.wordpress.org/srd, to which you have been given access (here’s why you need svn). Sardinian was also added to GlotPress, for versions 3.2.x and trunk (future 3.3). Happy translating!

     
    • massimeddu 8:27 am on July 22, 2011 Permalink | Log in to Reply

      Thanks Zé,
      It is possibile recover de translations from Sardinian (sc) to Sardinian (srd)?
      I lost all my translations….

      I thik, it is possible fix it with a single SQL query.

      Thank you

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