WordPress.org

Translate WordPress

Tagged: request Toggle Comment Threads | Keyboard Shortcuts

  • WordPress Suppo 9:01 pm on June 24, 2015 Permalink |
    Anasslikewordpress • ar.wordpress.org validator
    Tags: , request   

    Spanish (Colombia) does not have any validators yet.

    New Locale Request for Spanish Colombia

    Locale: es_CO
    Country code: CO
    Plural forms: nplurals=2; plural=(n != 1);
    Language native name: Spanish (Colombia)
    Sub-domain: es-co.wordpress.org
    Site Title: WordPress de Colombia
    Site Description: WordPress en Español de Colombia
    Admin Username(s): nsdirectomo
    Admin Email: anrahou at gmail.com

     
  • daniluk4000 7:02 pm on June 24, 2015 Permalink |
    daniluk4000
    Tags: , request, ,   

    Russian Validator 

    Hi, I want to be a Russian Validator. For our translators: I will be active and check all the words, i.e. will work better than before. I will translate absolutely all the projects in my (a lot) spare time. Take into consideration what @sergeybiryukov not check my translations for a few weeks. I hope for a favorable reply, really want to be, sincerely, me.

     
    • Sergey Biryukov 2:33 am on June 25, 2015 Permalink | Log in to Reply

      Hi @daniluk4000,

      Being a validator is more than just translating and approving strings, it’s also making sure that the context is right, the wording and sentence structure sounds natural for our language and is not a direct copy of the English sentence, the word choice is consistent across similar strings, the punctuation is correct, the string doesn’t break the UI in an unexpected way, etc.

      While I approve most of the strings submitted by others, I usually have to make a lot of edits to make sure everything above is accounted for.

      I’m not the only validator, but we’re doing this in our spare time, so it might take more than a week or two for things to happen.

      We always finish WordPress core projects on time. Other projects might occasionally fall behind, but we’ll get there.

      That said, there’s a plan to open up GlotPress for all the plugins from the repository in the upcoming months, and we’ll need a lot of new validators when it happens.

      Don’t get me wrong, I know we both want to make WordPress and related projects better. By all means, please continue contributing, your efforts are appreciated.

      I’m going to look through all the projects with waiting strings this Sunday during the WCEU contributor day.

    • daniluk4000 7:04 am on June 25, 2015 Permalink | Log in to Reply

      @sergeybiryukov I know that you is WordPress Core contributor, but as I said, I can work better than before. So I’m currently the validator of getbblog.com/ru, and I think that is my biggest, important and most correctly largest translation.

      By the way, when I have done the new translation, I need to create a post in this blog. I can’t just translate, because you don’t see it. This is the main difficulty. Besides, I know a lot of lines that are poorly and incorrect sound in Russian in several projects. And how do I fix them?!

      • Sergey Biryukov 3:14 pm on July 1, 2015 Permalink | Log in to Reply

        All done, thanks for your contributions!

        The list of projects I’ve checked:

        • Akismet
        • Blogger Importer
        • Tumblr Importer
        • User Switching
        • Forums
        • WordPress.org Themes Directory
        • GlotPress
        • WordCamp for Android
        • WordPress for Android
        • WordPress for iOS

        (WordPress core strings will be checked once the release candidate comes out.)

        I’ve sent you an invitation to ru.wordpress.org, and I’ll make you a validator for plugins (including Akismet and importers) once you join.

        Notifications for waiting strings should eventually be implemented in GlotPress for all projects: https://glotpress.trac.wordpress.org/ticket/100

        Feel free to ping me on Slack any time if there are new strings I should check.

  • brandbrilliance 6:54 am on June 19, 2015 Permalink |
    brandbrilliance
    Tags: , request   

    English (South Africa) en_ZA 

    Locale: en_ZA
    Country code: ZA
    Plural forms: nplurals=2; plural=(n != 1);
    Language native name: English (South Africa)
    Sub-domain: en-za.wordpress.org
    Site Title: English (South Africa)
    Site Description: WordPress in South African English
    Admin Username(s): brandbrilliance
    Admin Email: john at brandbrilliance.co.za

     
  • brandbrilliance 3:29 pm on June 18, 2015 Permalink |
    brandbrilliance
    Tags: english, request, south africa   

    For proper LOCALE settings, how can we get an official translation for English (South Africa) added under en_ZA. Basically we use British English, so you can just copy the en_GB as a starting point. I have added custom language files in my wp-content/languages folder, but these don’t show up in the GENERAL|SETTINGS as “English (South Africa)” because this mapping is missing (I don’t know where it’s coded), as it’s not in the language file either.

     
  • thierryyyyyyy 12:43 pm on June 17, 2015 Permalink |
    thierryyyyyyy
    Tags: , , request   

    Dear fr_FR validators,

    I finished to translate the last strings waiting, I would love that the bbPress get finalized. It’s only waiting for validators….

     
  • daniluk4000 10:39 am on June 11, 2015 Permalink |
    daniluk4000
    Tags: request, ,   

    Please check new Russian projects

     
  • Greg Kulik 6:44 pm on May 31, 2015 Permalink |
    gkkulik • szl.wordpress.org editor
    Tags: request   

    Hi, guys. I’d like to request support for the Silesian language.

    Locale: szl
    Country code: none; PL if compulsory here
    Plural forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100=20) ? 1 : 2);
    Language native name: Ślōnskŏ gŏdka
    Sub-domain: szl.wordpress.org (or szl-pl.wordpress.org if really necessary)
    Site Title: Ślōnskŏ gŏdka
    Site Description: WordPress po ślōnsku
    Admin Username(s): gkkulik
    Admin Email: gregorykkulik at gmail.com

     
  • Alvaro Gois dos Santos 8:43 pm on May 19, 2015 Permalink |
    alvarogois
    Tags: AO90, ISO, Portuguese Language Orthographic Agreement, , request, variants   

    Hi Polyglots,

    I’m a validator of the Portuguese (pt_PT) translation team. We’re facing a major issue with our translation. Some of you may have heard of the Portuguese Language Orthographic Agreement of 1990 (AO90). Well, it’s being implemented for 5 years now, with huge resistance in Portugal and several other Portuguese language countries. It’s mainly a political decision, with little respect for history and some basic rules. Nevertheless, it’s being used byimposed to public institutions.

    A while back we had an internal discussion in the Portuguese WordPress Community regarding the adoption of the AO90. The vast majority said no. But now the question arises again, and it seems unfare, even if we still have a strong resistance, that there’s no alternative for those who want or need to have WordPress in accordance to AO90.

    Therefore, what I need to discuss with you is the possibility of having variants for the Portuguese language, despite Portuguese in Portugal having only one norm. Me, @ze-fontainhas and several other members of the Portuguese Community have long discussed this possibility and how to implement a solution. Since there are no variants in the Portuguese language in Portugal, there are no ISO codes to identify possible variants. Anyway, it’s something we have to address and we wanted the Polyglots to help us.

    Does anyone have any idea how we can deal with this?

    Thanks.

     
    • TacoVerdo 1:48 pm on May 20, 2015 Permalink | Log in to Reply

      It sounds like this is quite like the situation the Germans have with default vs formal language. They have two projects on translate.wordpress.org.

      Could that be a solution for you as well?

    • Alvaro Gois dos Santos 2:42 pm on May 20, 2015 Permalink | Log in to Reply

      Hi Taco,

      Thanks for replying.

      As a matter of fact, we already have two similar projects on translate.wordpress.org, for formal (default) and informal Portuguese.

      But this isn’t enough, since it’s only an infrastructure for collab translation management, not actually a way for everyone to add the alternative version to WordPress.

      Unless there’s an easy way to get those alternatve language files from the repository. Is there?

      I came across a plugin (WPTB) to change WordPress language from within the admin, but, as WordPress core itself already does, it only loads the default language packs. In a situation were we have no variants, no ISO codes that identify the alternative language files, we cannot load the pack from the repo.

    • Torsten Landsiedel 10:40 am on May 21, 2015 Permalink | Log in to Reply

      Here is the trac ticket for that:
      https://core.trac.wordpress.org/ticket/28303

      The whole German community is hoping for a solution!

      @ocean90: You said, we have to think about a core solution. Is someone working on that already? Can we help?

      • Alvaro Gois dos Santos 10:45 am on May 21, 2015 Permalink | Log in to Reply

        Do you have any experience with a solution that overrides the default packages, but using the same locale with packages on an alternative repo?

        We’ll probably try a solution like that for the Portuguese Orthographic Agreement version. It’s not perfect but can be accessible, if it works…

    • Angelika Reisiger 7:12 pm on May 21, 2015 Permalink | Log in to Reply

      This is a huge problem for a lot of countries. After a short research I found this wikipedia article:
      https://de.wikipedia.org/wiki/H%C3%B6flichkeitsform#Die_H.C3.B6flichkeitsform_in_anderen_Sprachen

      They don’t list all countries with formal and informal language, but here are a few:
      France, Finland, Germany, Portugal, Hungary, Luxembourg, Serbian, Montenegro, Bosnia, Herzegovina, Croatia, Russia, Nederlands, Poland, Japan, China

      You could also read:
      https://en.wikipedia.org/wiki/Honorific

      All these countries only can use an informal (and rude) address to the visitors of their WordPress Website. Even, if they install the formal language – after the next wp-update will override the informal language.

      Please, take this problem seriously, cause it is a serious problem for all the WordPress Admins in such countries. Can we help?

    • Alvaro Gois dos Santos 9:04 pm on May 21, 2015 Permalink | Log in to Reply

      As to the formal vs. informal, that’s also a problem for us in Portugal, as you mention, though we have the opposite situation, our default language is formal and we have an informal GlotPress branch which is not accessible for the average user.

      What we’re trying to achieve, using a plugin, is a way to override the default language files for new ones, managed by the Portuguese Community. Possibly in an alternative GlotPress or Github repo.

      Why? Because there’re no variants in the Portuguese language (Portugal), hence we’ve to use the same ISO code so that other translations don’t break.

      I’ll post our findings here, Angelika.

    • Alvaro Gois dos Santos 10:41 am on May 25, 2015 Permalink | Log in to Reply

      @tacoverdo, @zodiac1978, @la-geek: update on language variants. We’re now testing a plugin solution that will enable local communities to ship language variants with their version of the plugin. So far it seems the best way to have a community driven solution that takes advantage of already existing translations, without imposing any variant.

      As to the specifity of Portuguese language translations, our goal is to avoid dispersing translation resources.

      I’ll be updating this soon 😉

      • Torsten Landsiedel 10:53 am on May 25, 2015 Permalink | Log in to Reply

        I would really prefer a core solution (as @nacin promised me @ WordCamp Europe in Sofia one year ago 😉 – but a community driven plugin workaround would be great until this is fixed. Please keep us updated! If we can help / beta-test, please ping me/us as well!

        • Alvaro Gois dos Santos 10:58 am on May 25, 2015 Permalink | Log in to Reply

          Thanks! I would have to agree with you as to a core solution, truth is we have an immediate demand.

          And a core solution won’t be that easy, I suppose, due to the ISO codes regarding locales and the possibility of disrupting plugin and theme translations.

        • Andrew Nacin 2:13 am on May 27, 2015 Permalink | Log in to Reply

          It’ll happen! I know @ocean90 has been looking into it, and I have some ideas. There’s some movement happening now on user locales (https://core.trac.wordpress.org/ticket/29783) and I suspect these will both move forward together in some way.

          It isn’t too hard to do, we just have to change how we key things and introduce a slight tweak to how we store locales in the DB and on the filesystem. So something like pt_PT_informal. Not a hard problem and won’t disrupt anything. Just takes time.

    • Angelika Reisiger 3:55 pm on May 26, 2015 Permalink | Log in to Reply

      Thanks @alvarogois for the heads up! Yeah, a core solution would be the best one – of course. But your efforts to build a plugin are really great and very appreciated. Do you need any help with testing in other language – here german formal?

      • Alvaro Gois dos Santos 4:17 pm on May 26, 2015 Permalink | Log in to Reply

        Hi @la-geek. We already have a plugin in test mode :)

        We’re facing some issues with server memory.

        I believe we’ll have a version for beta testing soon.

        It’s not the perfect solution but can be a temporary one.

        In it’s current form, the plugin installs two variants of the Portuguese (pt_PT) language, namely, Portuguese Orthographic Agreement (1990) and Portuguese Informal. After plugin installation, user goes to options > general and has two more options below the site language, one for frontend and the other for backend. It’ll only work if the exact same locale is defined, in this case Portuguese (Portugal), because the plugin overrides the locale’s default, admin and network admin language files. My guess is that this is the only way plugins’ and themes’ translations won’t break.

        To make it work with other languages – if we maintain the current architecture –, it has to be edited to work with your locale.

        I thought of a larger scale infrastructure, one where you could have a group of WordPress language variants. But I sense a lot of issues.

        In Portugal we have a small community, relatively close to one another. We almost know everyone who’s involved translating WordPress. But in other countries is not like that. It would be impossible to validate the accuracy of variants in an 100% open environment. I’m not sure how to do it.

        As soon as we get to beta I’ll post it here for everyone who wants to give it a try (and help making it better 😉 ) .

    • Alvaro Gois dos Santos 12:38 pm on May 28, 2015 Permalink | Log in to Reply

      Update: we now have a working plugin we called PT Variants available from WordPress.org (way faster than we thought…) and GitHub.

      It installs two variants of the Portuguese (pt_PT) language, namely, Portuguese Orthographic Agreement (1990) and Portuguese Informal. After plugin installation, user goes to options > general and has two more options below the site language, one for frontend and the other for backend. It’ll only work if the exact same locale is defined, in this case Portuguese (Portugal), because the plugin overrides the locale’s default, admin and network admin language files.

      To make it work with other languages it has to be edited to work with your locale.

    • Angelika Reisiger 4:27 pm on May 31, 2015 Permalink | Log in to Reply

      I had subscribed here for follow-ups, but did not receive any email :(.

      Does this plugin fetch the language files from https://translate.wordpress.org/languages/… ?
      I am not sure, but I don’t find this in pt-variants.php, so I guess, the files shall be uploaded manually?

      • Alvaro Gois dos Santos 8:47 am on June 1, 2015 Permalink | Log in to Reply

        Hi @la-geek. In fact, we’ve considered the possibility even of having a custom repo for language variants, one that could be used for various countries. But I believe it could be a problem to manage several different and concurrent versions for the same locales.

        We also had the matter of urgency. Therefore, we decided to include the existing variants. It allows us to validate the files.

        That doesn’t mean we’re not interested in a more general approach. Any ideas on that?

        What do you think of the plugin as it is now, have you tested it yet?

    • Angelika Reisiger 5:19 pm on June 1, 2015 Permalink | Log in to Reply

      Hi Alvaro, it is not so trivial to test this plugin. There are no “ready to go” german informal language files. They must be exported (from polyglot) and renamed. Second the plugin must be forked and edited for the german purposes.

      I will try this, but I don’t know, how successful I will be :). Could you please confirm, that the test procedure is as follows:

      Upload the language files, Install the plugin, change your preferred language variant (formal or informal)
      and then – how to trigger the process, that overrides/updates the language files normally? Could this be achieved with the installation of an older plugin or theme and after I click on update in WP Back end, the overriding process of language files starts?

      So I can test, if your plugin works and prevent the override of language files?

      • Alvaro Gois dos Santos 5:32 pm on June 1, 2015 Permalink | Log in to Reply

        Hi Angelika. The default language files are just override, their aren’t deleted.

        You’ll have to compile the variant you want to test. Make sure you have the same locale extension to your WordPress default install as this is essential.

        You’ll have to fork the plugin and edit the pt-variants.php so that it recognizes your exact variant (lines 35, 78 and 79).

        I’ll ask Marco Pereirinha to make this process more clear here. He’s the actually code-ninja.

    • Angelika Reisiger 5:40 pm on June 1, 2015 Permalink | Log in to Reply

      Hi Alvero,

      how I can test, if the plugin works? I must start a procedure to test it <- this is my question, how to start this.

      Next question, after I looked into the plugin:
      you have two different language files:
      pt_PT-AO
      pt_PT-INF

      Are these new names? So that means, I have to rename and upload both language files (formal and informal)?

      From de_DE (what is the normal name for german language file) to

      de_DE-FO (for formal variant)

      and rename the informal language file to
      de_DE-INF (informal variant)

      Of course I have to edit the pt-variants.php on lines 79 and 80, so that it will work.

    • Alvaro Gois dos Santos 5:43 pm on June 1, 2015 Permalink | Log in to Reply

      You’ll only need one file, we’ve introduced 2 variants because we have Orthographical Agreement version and Informal version. Our WordPress default pt_PT is Formal.

      So, I’d go with de_DE-FO and change the file references in the pt-variants.php file, as I mentioned above.

      • Angelika Reisiger 5:46 pm on June 1, 2015 Permalink | Log in to Reply

        So you have three variants in portugese language? formal, informal and OA? One of them ist default?

        How to test, if this plugin works and if it is prevented before overridings?

        • Alvaro Gois dos Santos 5:54 pm on June 1, 2015 Permalink | Log in to Reply

          Ja, default with WordPress pt_PT install is Formal.

          pt_PT-AO is Orthographic Agreement variant
          pt_PT-INF is Informal version

          If you fork the plugin and edit the lines mentioned above, and include your own version of de_DE-FO, you should see the difference. I’m guessing you already have those formal files for your own installs, don’t you?

          • Angelika Reisiger 5:58 pm on June 1, 2015 Permalink | Log in to Reply

            Oh, therefore I was confused. I thought, with this plugin you can switch between informal and formal language :)

            But now I see, that the plugin works (and is only needed), if you want to use another variant of language – instead of the default language. No need to switch.

            Okay, so far so good :)

            • Alvaro Gois dos Santos 6:02 pm on June 1, 2015 Permalink

              Yes, it just overrides the default language files with a custom variant, using the same locale.

              So, you only need it if you want to use a variant to the default language in your install.

              We’ve done it so that anyone could activate a pt_PT-AO variant without having to go through FTP and copy over the original files.

        • Alvaro Gois dos Santos 5:56 pm on June 1, 2015 Permalink | Log in to Reply

          If you only want to test the concept, you could even just change pt_PT for de_DE. You would have your dashboard in Portuguese!

          • Angelika Reisiger 6:03 pm on June 1, 2015 Permalink | Log in to Reply

            In the actual version it is only useful for portugese language. There are no options, to use it in other languages. What are your future plans?

            Will you develop the plugin to fit the needs of other languages and extend the line 76, the array and upload all the other language files?

            I don’t think so :). So, how can we (german atm) benefit of this plugin? The only way – I see – is to fork it and change all strings, that are needed for german purposes.

            Or will there be another way to globalize this plugin?

            • Alvaro Gois dos Santos 6:26 pm on June 1, 2015 Permalink

              We had a two issues: urgency and proof of concept.

              The way I see it, to globalize it, it should load variants for other languages or be packed for specific languages.

              As I mentioned earlier, I thought of a larger scale infrastructure, one where you could have a group of WordPress language variants. But I sense a lot of issues.

              In Portugal we have a small community, relatively close to one another. We almost know everyone who’s involved translating WordPress. But I can’t say the same for other countries. It would be impossible to validate the accuracy of variants in an 100% open environment. I’m not sure how to do it.

              What are your ideas on this?

    • Angelika Reisiger 6:33 pm on June 1, 2015 Permalink | Log in to Reply

      The official translated files are all hosted and maintained on translate.wordpress.org (also the other variants of languages – at least in german case). There are validators (like you) who proof the language strings. What are your concerns?

      The problem I see is the mainenance of these language files. It would be perfect, if the plugin would fetch the files from translate.wordpress.org. But they must be renamed, that the next issue. I don’t know :(

      • Alvaro Gois dos Santos 6:55 pm on June 1, 2015 Permalink | Log in to Reply

        OK, if it could read from the translate.wordpress.org repo there would be no problem, except for the files’ names.

        I could even agree with a plugin where you would only have access to variants for the locale actually loaded by WordPress. So, one could choose the locale (default language), like pt_PT or de_DE, and, after that, an option to load variants from the repo.

        That would be the the best UX, I guess. But it implicates a change on both translate.wordpress.org and WordPress itself. Maybe in the way @nacin points out up there.

  • hienzquynh 6:04 am on May 11, 2015 Permalink |
    hienzquynh
    Tags: , request, ,   

    Dear admin,

    I finished translating the entire bbPress 2.5.x Vietnamese language pack in a .PO file. Now that I would like to upload, it seems as though the option to uploading is not available for me as a contributor. Can you either let me join the bbPress Validator team (temporarily) and / or let me know the assigned Vietnamese validator to whom I can send the .PO file to? Entering the translations one string at a time online (more than 1,000 strings) is not practical nor doable for me since I am on and off the Net very frequently due to my job. Since there is currently no bbPress Vietnamese translation, this .PO file is perfect to upload all at once.

    Thank you so much!
    Brian

    P.S: I am thinking of translating other components such as BuddyPress or WordPress and many others in due time. Will I need to put out requests similar to this request every time when I need help in uploading the .PO to the appropriate component(s)?

     
  • fgienr 8:37 pm on May 7, 2015 Permalink |
    fgienr • fr-ca.wordpress.org editor
    Tags: fr_CA, request   

    There is no validator for the French (Canada) project. I would like to get this status in Rosetta, for the work to get done.

     
  • Matilde 4:28 pm on May 4, 2015 Permalink |
    mrosero
    Tags: request   

    New Locale Request

    Locale: es
    Country code: cr
    Plural forms: nplurals=2; plural=(n != 1);
    Language native name: Español de Costa Rica
    Sub-domain: es_cr
    Site Title: Español de Costa Rica
    Site Description: WordPress a lo tico
    Admin Username(s): mrosero
    Admin Email address: mrosero@gmail.com

     
    • Petya Raykovska 10:03 am on June 8, 2015 Permalink | Log in to Reply

      Hello Matilde!

      Thanks for requesting the new locale and sorry for the delayed answer. We will work on it this and contact you very soon with the details of getting started.

      Kind regards,
      Petya

  • romanbon 11:34 am on April 28, 2015 Permalink |
    romanbon
    Tags: request   

    Hi! I think that “Russian (Ukraine)” locale have to be removed. There are separate Russian and Ukrainian locales and “ru_UA” looks like nonsense.

     
    • Petya Raykovska 12:43 pm on April 28, 2015 Permalink | Log in to Reply

      Thanks for your request, @romanbon,

      Let me quickly investigate why the locale was created, might be some kind of a legacy thing. Will update as soon as I know more.

      Cheers!
      Petya

  • Gonahkar 10:15 am on April 22, 2015 Permalink |
    Gonahkar • fa.wordpress.org editor
    Tags: , request   

    Download stats API 

    We want to show our package download stats on our site (http://wp-persian.com) but there is no clean way to do it.
    Would you please provide an API to get download counter for locale languages?

     
  • Thejesh GN 12:34 pm on April 15, 2015 Permalink |
    thejeshgn • kn.wordpress.org validator
    Tags: request   

    Restarted working on Kannada transalation again. How can I add myself to
    https://make.wordpress.org/polyglots/teams/?locale=kn

     
  • daniluk4000 11:28 am on April 14, 2015 Permalink |
    daniluk4000
    Tags: request,   

    Please check Russian translate of https://translate.wordpress.org/projects/rosetta and https://translate.wordpress.org/projects/rosetta/apps

     
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