WordPress.org

Ready to get started?Download WordPress

Translate WordPress

Welcome to the official blog of the translators team for the WordPress open source project.

This is where we discuss all things related to translating WordPress. Follow our progress with general updates, status reports, and the occasional debate. We’d love for you to help out.

Do you want to contribute?

You can help translating WordPress to your language at any time. Just log in to the translation platform with your WordPress.org account, and suggest translations. If you want to help in managing and validating translations, please make sure to get in touch with the existing language team first.

Don’t see your language?

Request support for it by following this guide. We’ll have you up and running in no time.

Posting here

In order to post to this site, you will need to log in with your wordpress.org account. Note that your very first post may take a while to show up, as it is moderated; don’t create duplicates. Also, make sure to follow our tag policy when posting.

Archives

Looking for the archives of the old mailing list? They are right here. Use Google to search them, with the “site:” parameter.

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Wacław Jacek 6:08 am on April 24, 2014 Permalink | Log in to leave a Comment
    waclawjacek • pl.wordpress.org editor  

    What’s the current status of the 3.9.x branch at translate.wordpress.org? Should I build 3.9 from the “3.9.x” branch or from “Development”?

     
  • Maxime 4:56 am on April 24, 2014 Permalink | Log in to leave a Comment
    mbiais
    Tags: ,   

    Hi polyglots,

    We’re about to release WordPress Android 2.8 and we need you to translate the release notes:

    • New blog detail view in the reader
    • Statistics performance improvements
    • Samsung Multi-Window is now supported
    • Better UI design on small tablets for the Notifications and Comments screen
    • New translations: Turkish, Traditional Chinese (partial) and English (United Kingdom)
    • Other minor improvements

    Thank you!

     
    • drssay 5:30 am on April 24, 2014 Permalink | Log in to Reply

      ko_KR
      • 리더 화면에서 새로운 블로그 자세히보기 화면 구성
      • 통계 성능 향상
      • 삼성 멀티윈도 지원 추가
      • 알림, 댓글 화면에서 소형 테블릿을 위한 UI 디자인 강화
      • 새로운 번역 : 터키어, 중국어(부분지원), 영어(영국)
      • 기타 소소한 향상

  • sendhil 3:45 pm on April 23, 2014 Permalink | Log in to leave a Comment
    sendhil  

    Hey folks – we’re getting ready to release WPiOS 4.0.3 and could use your help translating some strings. Would you mind jumping in over at http://translate.wordpress.org/projects/ios/dev and helping out?

    Thanks!

     
  • Wacław Jacek 1:57 pm on April 23, 2014 Permalink | Log in to leave a Comment
    waclawjacek • pl.wordpress.org editor
    Tags:   

    Please remove user kuba’s validator role on the Polish site.

     
  • Stephen Edgar 10:59 am on April 23, 2014 Permalink | Log in to leave a Comment
    netweb • en-au.wordpress.org editor
    Tags: ,   

    As there are currently three separate discussions regarding GlotPress enhancements I’ll post this here as it probably should have been posted already.

    https://make.wordpress.org/community/2014/04/21/gsoc-students-accepted/

    Arian Allenson M. Valdez (@secretmapper) — Working on GlotPress UI and profiles with Yoav Farhi (@yoavf) and Marko Heijnen (@markoheijnen) as mentors

    Secretmapper will post updates to http://blog.glotpress.org/

    Now is probably be a great time to get more involved and help shape the direction of GlotPress

    https://glotpress.trac.wordpress.org/

     
  • Gary Jones 10:22 am on April 23, 2014 Permalink | Log in to leave a Comment
    GaryJ • en-gb.wordpress.org validator
    Tags: ,   

    Something that would really help the English variants is to have a feature that can copy all of the original strings for untranslated as the translated string, and leaves them as Waiting status.

    Being able to check and bulk accept these strings (fixing variations where necessary) would be considerably quicker than going through each string one by one to click on Copy original and accepting.

    ~95%+ of strings are going to be identical anyway between US English and British, Canadian and Australian etc. English, so I think it’s sensible to go with the assumption that strings match, and change where necessary, than assume the US English is going to be wrong (as with all other non-English variant languages).

     
    • Peter Westwood 10:31 am on April 23, 2014 Permalink | Log in to Reply

      I sort of disagree :)

      I think it would be better to extend GlotPress (and possibly WordPress) to better support the hierarchical relationship between different variants of a language.

      There are similar issues when you try and use GlotPress to have translations of both formal and informal versions of another language other than English and it would I think be better if we could document the relationship between languages and then share the translations better.

      The only reason we are doing this copying and accepting is a hack to make it easier to find new strings to confirm for translation or not.

      I think Wikipedia has a solution they use to solve this that it would be worth investigating.

      • Gary Jones 10:38 am on April 23, 2014 Permalink | Log in to Reply

        I’m new to this so I’m only saying what I perceive on a practical level. I’m open and more than happy to see something more generic and functional if it involves significantly fewer “click, , ” for those 95% unchanged strings.

    • Stephen Edgar 10:49 am on April 23, 2014 Permalink | Log in to Reply

      I think this is part of the idea behind the Glossary and being able to share that Glossary between projects per https://glotpress.trac.wordpress.org/ticket/97#comment:64

      No doubt only between single locale projects for starters and then maybe something to allow the sharing between locales down the road.

    • Marko Heijnen 11:11 am on April 23, 2014 Permalink | Log in to Reply

      This should not be implemented because it’s an exception and not a rule. Also you can also only translate the strings that are needed and skip the rest.

      • Gary Jones 1:20 pm on April 23, 2014 Permalink | Log in to Reply

        From a technical standpoint, you’re probably right, but it’s much easier to see that a language is now 99% complete (because some new strings have been added late in the cycle) when it was previously 100% complete, than having to look through 95% of strings again in case new ones happen to contain a spelling that needs to be changed. Being able to mark off those that don’t need changing (i.e. by just copying the original) is pragmatically more convenient for accuracy purposes.

        If I didn’t make it clear, my intent would be to only have this feature enabled for English variants, but then as Peter said, variants in other languages may be based on a certain base translation with only a few changes needed.

        • Ze Fontainhas 2:22 pm on April 23, 2014 Permalink | Log in to Reply

          The reasoning is valid for any language that belongs to a macro language, really, not to mention the ones which can additionally have “non-regional” variants, such as formal and informal, and so on.

          Even if a language does not belong to a macro language group, it could still be the case that the difference from one variant to the next is small enough for a copy feature to make sense.

          tl:dr I’m not sure it’s an actual, bona-fide, exception.

    • Ze Fontainhas 6:34 pm on April 23, 2014 Permalink | Log in to Reply

      Marking as “not request”. Also, this debate should move to the GlotPress blog

  • Emre Erkan 10:11 am on April 23, 2014 Permalink | Log in to leave a Comment
    wordpress-tr • tr.wordpress.org editor
    Tags: , ,   

    First of all, thanks for glossary. It’s a life saving functionality.

    I’m currently validating lots of project and trying to maintain order between them. Glossary is a very helpful tool to accomplish this but it’s project specific. Is there a way to use a common glossary for selected projects or for all of them?

    Please don’t say import/export. It’s not functional when you try to keep all glossaries from all projects updated. For example when translating or validating a project, you see a term which needs to be put in glossary. You can’t add it to just that project if it’s a very general term. You have to put it to all glossaries. Yoı choose a projects glossary as primary glossary and update it, export it and import it every project you’re validating.

    Possible solutions;

    • A single glossary for all projects
    • Import functionality betweeen glossaries
    • Inheritance (When you create a glossary you choose a parent and with this it contains all the terms of parent glossary)

    TL;DR -> title ^ ^

     
  • Emre Erkan 9:44 am on April 23, 2014 Permalink | Log in to leave a Comment
    wordpress-tr • tr.wordpress.org editor
    Tags: ,   

    Is it possible to make GlotPress dashboard a little bit more useful? Like showing active projects and their statuses to validator like this: http://imgur.com/Bh2Kg1x

    It’s hard to track all the projects. I have to check every project to see if there is new or waiting translations. Just WordPress Core has 6 active projects (3 themes, WordPress, Administration and Network). There is mobile projects, plugins etc. It’ll be a handy feature if implemented.

     
  • Mushviq Abdulla 5:19 pm on April 22, 2014 Permalink | Log in to leave a Comment
    muhsinmushviq • az.wordpress.org editor  

    Hi everyone! I have a problem with adding new users to your site az.wordpress.org. Need help.

     
  • Slava UA 7:41 pm on April 21, 2014 Permalink | Log in to leave a Comment
    slaFFik • ru.wordpress.org validator
    Tags:   

    Is it possible to tag the translation of BuddyPress here? http://translate.wordpress.org/projects/buddypress
    BuddyPress 2.0 released, it’s not development version anymore. And to avoid problems with getting the translation automatically from GlotPress there should definitely be some tags/versions diversification.

     
  • Rafa Poveda 12:24 pm on April 21, 2014 Permalink | Log in to leave a Comment
    bi0xid • es.wordpress.org editor  

    Hello there.

    If you create a beta or RC version in your local site, it automagically goes to the Beta & RC versions place when distributed. If you do the same with an alpha, it goes to the main page and take the main place. I’ve just tested it with 4.0-alpha.

    Can you make the alphas go to the Beta & RC versions place too to avoid errors?

    Thanks.

     
    • samuelsidler 1:57 pm on April 21, 2014 Permalink | Log in to Reply

      We don’t formerly ship alphas, just betas and RCs. That is, the “alpha” version number is just trunk prior to beta and RC. There is no need to package trunk versions, and, in fact, it might be confusing for you to package them given that core doesn’t ship them as actual releases.

      • Sergey Biryukov 2:18 pm on April 21, 2014 Permalink | Log in to Reply

        I think Rafael’s concern here is that it’s too easy to build an alpha version by mistake, and it replaces the stable version on the home page. This was an issue with some localized packages a few days ago.

        • Rafa Poveda 2:29 pm on April 21, 2014 Permalink | Log in to Reply

          That’s the point. Thank you, Sergey :).

          I understand that there is no use in shipping alphas, and that we have the beta-tester plugin if we want to use them (and Vagrant –all hail Vagrant and VVV–).

          It’s only the concern that if it’s possible to have the alphas shipped to the beta place, it can avoid problems.

          Thanks again.

        • Stephen Edgar 10:39 pm on April 21, 2014 Permalink | Log in to Reply

          Yes, as I noted here:

          b) Some error checking to the build tools so that the ‘WordPress Version’ number we enter in this form field explicitly matches the version listed in `/wp-includes/version.php` against the tag/project/branch/revision/HEAD we are compiling against.

          It would be nice if something like this could be adopted as part of the i18n build process.

  • Rafa Poveda 12:20 pm on April 21, 2014 Permalink | Log in to leave a Comment
    bi0xid • es.wordpress.org editor
    Tags: ,   

    Hello there.

    Project 3.9 and 3.9.x does not exist. If I need to change any string in the translation of version 3.9, I cannot do it because it makes a 4.0-alpha release.

    It’s not a blocker, you can still build 3.9 via SVN using revision 27986. But if it’s going to be a 3.9.1 version soon, maybe it’s a good idea to have them.

     
  • Emre Erkan 9:14 am on April 21, 2014 Permalink | Log in to leave a Comment
    wordpress-tr • tr.wordpress.org editor
    Tags: , ,   

    Hi Android team,

    tr_TR is ready for action! ping @mbiais

     
    • Gary Jones 9:53 am on April 21, 2014 Permalink | Log in to Reply

      en_GB is also ready.

      I can’t see a language option in the settings – so is this something that is detected and set automatically based on the phone settings? Will en_GB get selected instead of en_US if English (United Kingdom) is set within Android?

      • Maxime 11:50 pm on April 21, 2014 Permalink | Log in to Reply

        Yes, exactly, if the selected system language is `English (United Kingdom)` WordPress for Android will be using the en_GB translation.

    • Maxime 11:49 pm on April 21, 2014 Permalink | Log in to Reply

      Thanks, tr_TR and en_GB will be shipped with WordPress for Android 2.8

    • Maxime 11:54 pm on April 21, 2014 Permalink | Log in to Reply

      @wordpress-tr may I ask you to translate the app description and promo text?

      App description:

      WordPress for Android puts the power of publishing in your hands, making it easy to create and consume content. Write, edit, and publish posts to your site, check stats, and get inspired with great posts in the Reader. What’s more? It’s open source.

      WordPress for Android supports WordPress.com and self-hosted WordPress.org sites running WordPress 3.6 or higher.

      Visit the forums to get help with the app: http://android.forums.wordpress.org

      Promo text (max 80 characters, this text is used when the app is featured on the Play Store):

      Write new posts, edit content, and manage comments on your WordPress blog.

      • Emre Erkan 11:13 pm on April 23, 2014 Permalink | Log in to Reply

        Here:

        App description

        Android için WordPress içerik oluşturma ve tüketmeyi kolaylaştırarak yayın gücünü avucunuza taşıyor. Sitenizde yeni yazılar yazın, düzenleyin ve yayınlayın, istatistikleri takip edin, okuyucudaki harika yazılardan ilham alın. Dahası mı? Açık kaynak.

        Android için WordPress uygulaması hem WordPress.com hesaplarını hem de WordPress 3.6 ve üzeri çalıştıran WordPress.org sitelerini destekliyor.

        Forumları ziyaret ederek uygulama ile ilgili yardım alabilirsiniz: http://android.forums.wordpress.org

        Promo Text

        WordPress blogunuzda yeni yazılar yazın, düzenleyin, yorumları kontrol edin.

  • mikehavliczek 3:03 pm on April 19, 2014 Permalink | Log in to leave a Comment
    mikehavliczek
    Tags: ,   

    ‘ello guys. Iam starting to translate bbpress and buddypress to Czech language (looks like nobody else doing this) So can i have a validator rank please?

     
    • pavelevap 8:56 am on April 21, 2014 Permalink | Log in to Reply

      Hi, there are many waiting translations by different users, I can make them live as soon as WP 3.9 localization will be done. Are there any suggested translations for bbPress, which were created by you? Are you using different username for this project? I would be happy to give you validator rights, but I could not find any suggested translations to check quality?

      I also received complete BuddyPress localization from one user in .po file and I will import it after some checks and merging it with current suggested strings in GlotPress.

    • dudlaj 1:28 pm on April 22, 2014 Permalink | Log in to Reply

      Hi,
      I have complete translation of bbPress for czech language. I have finished it during the night. I want to check the strings one more, cause the initial version was translated by someone else. All will be part of files i will send (mo/po). So how will we do this ? I am translating also other plugs – WooCommerce for example (on Transifex). And I like to have the czech version updated – any help with the translation is appreciated :-)
      dUDLAJ

    • mikehavliczek 6:27 pm on April 23, 2014 Permalink | Log in to Reply

      Hey guys, sory for late reply. I wish my day had at least thirty hours right now.
      Pavelevap: we had serious complications on web that day i post a request, so i didnt had a time, but my coleague start with some translations, her nick is MarketaR. so you can check (shes a proffesional czech-english-russian translator)
      Dudlaj: count me in. I dont have much time last days, but i can find hour or two a day for some translations, if you need a help. So tell me what needs to be done.

    • pavelevap 10:06 pm on April 23, 2014 Permalink | Log in to Reply

      Hi, I will be back on Monday and I will check it…

  • Eka Y Saputra 11:57 am on April 18, 2014 Permalink | Log in to leave a Comment
    ekajogja • id.wordpress.org editor
    Tags: ,   

    Tried to build 3.9 package for id_ID, I got this error:

    • missing /tmp/rosettaW81m8m/id_ID/messages/akismet/id_ID.po

    What should I do to fix it? Thx

     
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