WordPress.org

Ready to get started?Download WordPress

Translate WordPress

Updates from October, 2011 Toggle Comment Threads | Keyboard Shortcuts

  • Andrew Nacin 12:06 am on May 22, 2014 Permalink | Log in to leave a Comment
    nacin
    Tags: , ,   

    Internationalization goals for WordPress 4.0

    Hello all. Earlier today I published a post on make/core called Internationalization goals for WordPress 4.0. This of course affects you so I wanted to make sure you saw it and give you the opportunity to provide feedback. I am sure you will have questions as to how this will affect translation teams, which you can ask here if you’d like.

    Let me outline the goals for WordPress 4.0. I’ll then answer what I anticipate will be some frequently asked questions.

    1. The first step installing WordPress should be to choose a language. The rest of the install process would then be in that language.
    2. You should be able to choose/switch a language from the general settings screen, after which the language pack should be downloaded.
    3. You should be able to search from the dashboard for plugins and themes that are available in your language.
    4. All localized packages should be able to be automatically generated and made available immediately as part of the core release process.
    5. Localized packages should only be used for initial downloads from WordPress.org. Instead, language packs should be transparently used for updates.

    Does this mean I will no longer need to create builds and releases?
    That’s the idea. If at time of core release you are 100% translated, then I’d want everything to be packaged up automatically. Ideally, the Rosetta builder will go away entirely.

    The builder will go away? But what about alpha/beta/RC releases?
    We’ll make it possible to build these.

    What if my locale doesn’t make any modifications?
    Once this goes into effect, you won’t be able to make local modifications anymore. The whole process is being simplified. We’ll be retiring the ability to ship a {$locale}.php file or to add files to dist/. Future adjustments will need to go through WordPress core.

    What if my locale currently requires local modifications?
    We’re not going to make the experience worse for your users by preventing you from making these modifications. As I noted in the post, about 14 locales make changes that WordPress core will need to account for first, not including readmes, licenses, and the sample config file. This is going to be similar to my efforts in 3.4 to reduce the number of hacks you needed to make. Once your locale no longer requires modifications, legacy modification support will be disabled for your locale.

    So, how are we going to translate readmes, licenses, and sample config files?
    I don’t know yet. They will either continue to be done in SVN, incorporated into the Rosetta dashboard, or somehow imported into translate.wordpress.org. You won’t need to update the readme with each version, though; we’ll be sure of that.

    Does this mean SVN won’t be needed anymore?
    The idea is to simplify the entire process down to translation. You shouldn’t need to be a developer, or know how to use version control, or be awake to immediately push a build, or be responsible for issues like this.

    What if I want to use SVN still?
    I plan to drop support for building packages directly from SVN. This isn’t just simplifying the process. It will also drastically simplify the complex build system behind Rosetta (yes, the rest of it will be open-sourced) and improve maintainability. If you’re one of the three or so translation teams that make liberal use of SVN, I imagine we can work something out. (After all, GlotPress makes it easy to import PO/MO files.)

    Will this eliminate the double-upgrade annoyances?
    You bet. There will no longer be irrelevant “in English” warnings. Automatic background updates will “just work” without leaving you confused.

    Do language packs mean I can fix a typo post-release?
    Yes! Language packs for core WordPress releases will mean that updating the strings will be separated from updating the software itself. We don’t typically change strings in a point release because it slows you down in shipping a package (which is sometimes a security fix), but we might do that in the future with enough warning. And if you have a typo in a translated string, you could fix it whenever, and the language pack would simply be rebuilt and re-served to installs — no need to wait (or hope) for a point release.

    This post mentions plugins and themes, but when is all of that coming?
    Basic language pack support is live for a few select plugins (bbPress, BuddyPress, Akismet) and I expect to have a wider pilot program ready in the coming weeks. More details to follow, promise.

    Nacin, you forgot about X!
    The post and its comments mention a few things that aren’t going to happen for 4.0, like “Admin in English,” per-user languages, per-post languages. (We need to walk before we can run.) If something is missing that should probably be in 4.0, please mention it. Or if I over-simplified something in that post (as in, it doesn’t look like I accounted for how complex something is going to be to do), please enlighten me.

    Bonus: How can I help build all of this?
    Great question! I’ll be shifting tasks into tickets on both core and meta Tracs in the coming days. If there is something in particular you want to help with, please let me know.

     
    • Remkus de Vries 7:17 am on May 22, 2014 Permalink | Log in to Reply

      Looking good @nacin :) Looking very good. I am super excited about what’s up ahead for what’s closing in on 50% of all WordPress users.

      Basic language pack support is live for a few select plugins (bbPress, BuddyPress, Akismet)…

      I’ve seen bbPress and Akismet being updated and getting odd results. I assume this is fixed now?

      Have you thought about scenarios where a (multi)site will have more than one language active?

      • Rasheed Bydousi 7:34 am on May 22, 2014 Permalink | Log in to Reply

        Fonts in English version looks bad in the Arabic version.
        I hope that we will stay have the option to change the fonts type.

        • Gonahkar 8:04 am on May 31, 2014 Permalink | Log in to Reply

          As @Rasheed mentioned above, some languages look ugly in WP’s default font family.
          We really need to change the default font in Persian language too.

      • Andrew Nacin 4:06 pm on May 22, 2014 Permalink | Log in to Reply

        @defries As of right now, multisite only runs an update check from the main site. However, there is a filter that allows you to request multiple languages from the API. Example usage would be to request all languages used on any site. Due to the distributed nature of multisite this may be tough to do in core, but we have a lot of opportunity to think about that.

        • Remkus de Vries 8:03 am on May 23, 2014 Permalink | Log in to Reply

          There are a lot of multi-lingual sites that fit this multi-site scenario. Would your thinking be that all those sites should add such filter in order to update all them languages?

    • Nashwan Doaqan 8:37 am on May 22, 2014 Permalink | Log in to Reply

      hmm.. Looks Good!! This will make the translation process more easier!

      but..
      1- Is this mean the WordPress package will be without translation files and they will be auto downloaded and generated when the use choose the language from the Installer? if Yes! what if I want to download a local-version to use it offline?

      2- As @Rasheed Bydousi said we shall still have the ability to change the CSS at least! ..

      Thanks for your effort !! ^_^

      • Andrew Nacin 4:14 pm on May 22, 2014 Permalink | Log in to Reply

        The standard WordPress package you download from wordpress.org/download/ will be without translation files. However, the package you download from a locale site, such as ar.wordpress.org, will include those languages, and specifically recommend that language during the selection process.

        This package, of course, will not be used for updates; instead, WordPress would use the separate “language pack” that would consist of just PO and MO files. These packs would also be hypothetically available to download, though it’s just the wp-content/languages folder that you’d be able to find in the main package.

    • Xavier Borderie 9:52 am on May 22, 2014 Permalink | Log in to Reply

      “Do language packs mean I can fix a typo post-release? Yes!”

      Sweet!

    • Andrew Nacin 4:11 pm on May 22, 2014 Permalink | Log in to Reply

      @Rasheed @alex-ye: Once your locale no longer requires modifications and we retire the legacy builder for your locale, you will no longer be able to make CSS modifications. These changes belong in core, not as part of a language pack.

      We handle these issues in one of two ways. One, we adjust the CSS generally to account for longer strings. Two, we have locale-specific rules: https://core.trac.wordpress.org/browser/trunk/src/wp-admin/css/l10n.css. You can open tickets on Trac (under the i18n component) and any CSS problems can and will be addressed in the next version. We’ve been doing this since version 3.4 and it has been working out well, which is why we are now moving to retiring the local modifications.

      Already, RTL uses Tahoma, except for Hebrew, which uses Arial instead. Some locales also make adjustments to avoid rendering italics. If Tahoma for Arabic is not good, please open a ticket.

  • Remkus de Vries 8:41 am on May 9, 2014 Permalink | Log in to leave a Comment
    DeFries • nl.wordpress.org editor • fy.wordpress.org editor
    Tags: automatic updates,   

    Hi @nacin

    I just saw the bbPress translations being updated while updating to WordPress 3.9.1 which made me very happy. When I then updated a multi-site instance to 3.9.1 (with also bbPress activated in the network) there were no updates of the bbPress language files.

    Any idea why I would have two different outcomes?

     
    • Ze Fontainhas 8:47 am on May 9, 2014 Permalink | Log in to Reply

      Not sure I get it. Why would a WordPress update change bbPress’ language files? Remember that before bbPress releases a new version, you can always export those from Translate and update bbPress. Or am I seeing this wrong?

    • Marko Heijnen 7:08 pm on May 9, 2014 Permalink | Log in to Reply

      I saw the same. I also seeing the issue that it was downloading the dev version and not the 2.5.x one.

      • Stephen Edgar 10:47 am on May 10, 2014 Permalink | Log in to Reply

        Boom! This is awesome, I hadn’t noticed this and have just now been playing :)

        I had an en_US (default) multisite test setup and switched it to en_AU and I got the translations for Akismet, bbPress & BuddyPress

        So multisite worked for me and not for @DeFries

        After close inspection of the headers in the bbPress .po file I believe the translations are via GlotPress’ bbPress 2.5.x tag though @markoheijnen got the /dev translations.

        No doubt this will need more testing as running bbPress /trunk I’d expect to get the /dev translations (even if they are only partially translated )

        Massive thanks @nacin and please thank anyone else involved we are not aware of :)

        If there is a Trac ticket to track this let me know and I’ll test the daylights out of all the permutations and combinations :)

        @vanillalounge Automatic Translations Updates #FTW http://make.wordpress.org/core/2013/09/24/automatic-core-updates/

        p.s. This is one of the primary reasons I created the en_AU translations to make sure we have bbPress and BuddyPress deliver automatic translations.

        • Remkus de Vries 11:48 am on May 10, 2014 Permalink | Log in to Reply

          Indeed, major props to anyone involved in getting these updates working. REALLY happy with it and I trust these bugs will be ironed out. Someday ;)

  • Nick Weisser 12:59 pm on May 4, 2014 Permalink | Log in to leave a Comment
    openstream • gsw.wordpress.org validator • de-ch.wordpress.org editor
    Tags: ,   

    Hey Remkus, I’d like to request a new Rosetta site de-ch.wordpress.org. I’ve imported the formal translations for Swiss German on translate.wordpress.org. Please let me know what the next steps would be. Nick

     
    • Kevin Kyburz (@swissky) 8:29 am on May 5, 2014 Permalink | Log in to Reply

      the formal version can indeed run over gsw.wordpress.org. de-ch.wordpress.org I had already discussed at WordCamp Europe with Ze

    • Kevin Kyburz (@swissky) 8:33 am on May 5, 2014 Permalink | Log in to Reply

    • openstream 10:40 am on May 5, 2014 Permalink | Log in to Reply

      I have just imported the formal one for the admin section in dev, too. But for some reason http://translate.wordpress.org/projects/wp/3.9.x/admin is still only showing a blank page.

      Regarding Rosetta page: I think the ZIP should contain the formal Swiss version of the .po files. If someone then installs WordPress from the official Swiss German ZIP he/she will also see the Swiss German blog postings on the admin dashboard widgets.

    • Ze Fontainhas 1:29 pm on May 5, 2014 Permalink | Log in to Reply

      This is getting confusing, real fast. For the sake of clarity:

      What is the purpose of gsw and de_CH? Please see http://www.ethnologue.com/country/CH/languages for disambiguation. Is it that de_CH is significantly different from both de_DE and gsw? I’m asking because there is no mention in Ethnologue of a version of Swiss German somewehere between Standard German and Schwyzerdütsch. Might this be just a matter of formal vs. informal variants of gsw?

      the formal de_CH version would most like be more used than the informal one currently available and thus would deserve a proper site.

      I’m not so sure. Other languages have variants (pt_PT and de_DE, at least), and those do not usually warrant a separate site. Remember that an additional site requires additional maintenance. Granted there is the question of packaging releases, which isn’t variant-aware, but maybe @nacin has plans or can recommend a sensible approach to this.

      for some reason http://translate.wordpress.org/projects/wp/3.9.x/admin is still only showing a blank page.

      Looks like a bug to to me, but there’s been some activity on the GP repo lately, maybe @yoavf or @markoheijnen can take a look.

      • Remkus de Vries 4:29 pm on May 5, 2014 Permalink | Log in to Reply

        I’m not so sure. Other languages have variants (pt_PT and de_DE, at least), and those do not usually warrant a separate site. Remember that an additional site requires additional maintenance. Granted there is the question of packaging releases, which isn’t variant-aware, but maybe @nacin has plans or can recommend a sensible approach to this.

        The “treating it as a separate site” came from the wish to do proper releases and the expectation the formal version would actually find itself on more installations than the informal.

        Looks like a bug to to me, but there’s been some activity on the GP repo lately, maybe @yoavf or @markoheijnen can take a look.

        Regarding the bug, I’m guessing it has something to do with copying dev to 3.9 project in GlotPress?

      • Andrew Nacin 4:42 pm on May 5, 2014 Permalink | Log in to Reply

        I do indeed have near-term (4.0) plans to fix up all release packaging, including locale variants.

      • Nick Weisser 5:03 pm on May 5, 2014 Permalink | Log in to Reply

        Although occasionally you will find websites or books published in spoken Swiss German (ISO code gsw), most publications including newspapers are written in de_CH, i.e. formal German with de_CH spelling which slightly differs from the de_DE spelling. As far as I understand de.wordpress.org is de_DE. For Austria the difference between de_DE and de_AT might be neglectable, but I’m sure there are people who will also disagree with that :-)

        I’m maintaining the de_CH language pack for Magento and think it absolutely makes sense to have a separate language pack for de_CH, because not only the spelling is different (ss instead of ß), but also some of the words are different, e.g. Kanton instead of Bundesland.

        When building an e-commerce website based on WordPress there’s one more aspect that comes into play, i.e. number formatting. You need to configure the de_CH locale in a Swiss store, because floating numbers like 1.25 are formatted the same way as in the US, whereas in Germany and Austria they are formatted with a comma, i.e. 1,25.

        I’m not sure how other countries with more than one official language handle this (Switzerland has 4 official languages), but another reason for having our own Rosetta site is the country specific blog postings which are pulled into the “WordPress News” section of the admin dashboard of Swiss German (de_CH) WordPress installations.

        If I install the regular German ZIP package of WordPress I see German “WordPress Nachrichten” in the dashboard with events in Hamburg that are not necessarily relevant for Swiss WordPress users. So either the Swiss WordPress community would have to post their stuff on blog.wpde.org (as de.wordpress.org has no blog postings) or on ch.wordpress.org.

        So in conclusion the best thing for Switzerland would actually be the Rosetta site ch.wordpress.org for all 4 official languages where you can download 4 different ZIP archives, one for each language. If that does not make sense, the 2nd best option would be de-ch.wordpress.org and if that does not make sense either, we would probably have to create our own “inofficial” domain where we gather the ZIP archives for all 4 official languages and can provide a Swiss WordPress news blog, too.

        • Ze Fontainhas 5:58 pm on May 5, 2014 Permalink | Log in to Reply

          This argument makes a lot more sense, thank you for that. We’ll implement de_CH, but I’ll still need it in the proper request format.

          Some notes:

          For Austria the difference between de_DE and de_AT might be neglectable,

          It’s not, and never, ever say this to an Austrian, much less a Viennese :)

          the Rosetta site ch.wordpress.org for all 4 official languages where you can download 4 different ZIP archives, one for each language

          This is not doable right now, the best we can do is offer a de-ch.wordpress.org. Not only can we not do “country” Rosetta sites, nor can we do “meta-language” Rosetta sites (think a new fr, de or pt Rosetta site, that would list all variants of a language). That said, the necessity is clear (even if the priority mightn’t be) and I’m all for discussing what it would take to have those available.

    • Nick Weisser 7:15 am on May 6, 2014 Permalink | Log in to Reply

      Thanks a lot, Ze. I saw that you already added it to https://glotpress.trac.wordpress.org/browser/trunk/locales/locales.php

      For French there is French (France), French (Canada), etc. so it could also be named German (Switzerland). Anyway, very glad we can now start building the Rosetta page. Very much appreciated!

  • Stephen Edgar 11:49 pm on February 13, 2014 Permalink | Log in to leave a Comment
    netweb • en-au.wordpress.org editor
    Tags: , , docs, ,   

    IRC Chat Summary 13 FEB 2014 (Logs)

     
    • Stephen Edgar 12:25 am on February 14, 2014 Permalink | Log in to Reply

      Regarding the Handbook, @nbachiyski do you have any updates or need some more helpers?

    • Trifon 12:31 pm on February 17, 2014 Permalink | Log in to Reply

      I couldn’t find the current branches for bbPress (2.5.x) and BuddyPress (1.9.x). Does the Development branch represent it, or is that for future versions only? And if so, is it still up to date due to the branches seeming to lag behind with the current versions?

      Also, is @defries still active as validator for nl_NL? As I saw multiple translated strings for BuddyPress and bbPress which still require validation.

      • Remkus de Vries 7:55 pm on February 17, 2014 Permalink | Log in to Reply

        No need to hijack this thread, but yes, I am still a validator and approved all that needed approving last friday. I’ll make my rounds again this Friday :)

      • Stephen Edgar 10:41 pm on February 17, 2014 Permalink | Log in to Reply

        There are indeed some bbPress v2.6 and BuddyPress v2.0 strings now in the /dev branches, not many but a few. This should be fixed pretty soon so we just have wait until it is.

    • Stephen Edgar 1:06 am on February 28, 2014 Permalink | Log in to Reply

      bbPress v2.x Theme for International Support Forums https://meta.trac.wordpress.org/ticket/376

      • Ze Fontainhas 1:33 am on February 28, 2014 Permalink | Log in to Reply

        I shiver in anticipation.

        • Stephen Edgar 1:45 am on February 28, 2014 Permalink | Log in to Reply

          Ha… I have much of the ‘base’ theme done and am now just tidying it up an starting to commit it to the repo.

          Getting the full functionality of the multisite bits, international domains and legacy code from legacy bbPress are still to come though I have a pretty good understanding of the code behind it all now.

  • Wacław Jacek 2:40 pm on January 6, 2014 Permalink | Log in to leave a Comment
    waclawjacek • pl.wordpress.org editor  

    Can I please request the creation of a 3.8.x branch on GlotPress so that I can release the Polish translation with just the 3.8 strings and no new ones?

     
  • Petya Raykovska 10:43 pm on December 3, 2013 Permalink | Log in to leave a Comment
    petya
    Tags: Discussion, Plans, Todo, WordCamp London   

    Hi everyone,

    Better late than never! Here my notes from the Polyglots discussion with @nacin, @defries, @markoheijnen, @coachbirgit and some other wonderful people at WordCamp London.

    Pretty much all of these are things we agreed on.

    • Having official teams based on the .org user roles that are official on a page on polyglots.wordpress.org as a point of contact for people wishing to contribute. Editors and administrators get there by default.
    • Contact form inquiries in the local .org sites being transformed into support questions on the local forum
    • Two levels of rights for per project validation – more strict for WordPress projects and the other for plugins, themes…
    • Plugin translation – a validator for a certain language to be able validate as well as the plugin author & existing contributors to that particular plugin

    And some other issues that were discussed:

    • Per project validation – should there be a separate user role to grant per project validation rights
    • Fuzzy matching – strings in a related project
    • The problem with lost strings – Ex. If you move a string from administration to main or network admin, the translation gets lost

    Cheers!
    Petya

     
  • Ze Fontainhas 2:57 pm on October 7, 2013 Permalink | Log in to leave a Comment
    vanillalounge • pt.wordpress.org editor  

    All pending rosetta deploys have been processed. Thank you for your patience.

     
  • Isaac Keyet 12:16 am on September 30, 2013 Permalink | Log in to leave a Comment
    isaackeyet • sv.wordpress.org validator
    Tags: , , validation   

    Validation request! There are a few languages in the WP for iOS and Android projects that are waiting for a validator to take a look.

    iOS

    Finnish, Tamil, Slovak, Irish, Arabic, Persian, and Greek all also have pending strings but are at a low overall translation level. Help needed!

    Android

    Georgian, Slovenian, Slovak, Finnish, Norwegian (Bokmål), Bulgarian, Czech, Arabic, Persian, Burmese, Uzbek, Azerbaijani, and Mongolian too have pending strings (some have lots!) but are far from a 100% overall. More translation help needed.

     
    • Naoko Takano 12:34 am on September 30, 2013 Permalink | Log in to Reply

      Moderated Android in Japanese & added some more translations. Thanks!

    • vestimir 9:49 am on September 30, 2013 Permalink | Log in to Reply

      I’ll try to help with the Bulgarian translation. Can you add Bulgarian translation for the iOS project?

      • Isaac Keyet 2:06 pm on September 30, 2013 Permalink | Log in to Reply

        That’d be great! We’re just trying to get the translations as close to core WP as possible and only make exceptions where it’s absolutely needed due to width constraints.

        I’ll see if we can add Bulgarian to iOS shortly, we just want to make sure we keep as many languages at 100% at all times otherwise it’s (of course) not a very good experience.

        • Kenan Dervisevic 2:45 pm on October 1, 2013 Permalink | Log in to Reply

          @isaackeyet Is it possible to publish a localization in a language that isn’t supported by iPhone and Apple? If so, I would gladly help in making WP for iOS available in my language (Bosnian) too.

          • Isaac Keyet 2:52 pm on October 1, 2013 Permalink | Log in to Reply

            Unfortunately not, and it looks like neither Bulgarian nor Bosnian are currently supported by Apple unfortunately :( Sorry guys! If you keep translating at least we’ll be ready once they enable it, but since there’s a lot of upkeep maybe best to simply hold off.

        • vestimir 10:54 am on October 2, 2013 Permalink | Log in to Reply

          Hey, I am ready to submit translations. I downloaded a PO-file from the translation site. How do I import it back? Do I have to clone a repo or something?

          • vestimir 8:19 am on October 4, 2013 Permalink | Log in to Reply

            @isaackeyet can you direct me to the validator for the Bulgarian translation, so I can send him a PO file with the translations I made?

            • Petya Raykovska 12:35 pm on October 6, 2013 Permalink

              I’m gonna talk to Mario and Nikolay and take care of projects for WordPress for iOS and Android to be set up shortly, Vesti. And I will take care of the Android project translation.

            • vestimir 11:28 am on October 7, 2013 Permalink

              10x Petya. I spoke with Ze and he pointed me to make a validator request, so I posted one yesterday here.

    • Nashwan Doaqan 10:45 am on October 1, 2013 Permalink | Log in to Reply

      Arabic on progress…

    • shooh 1:56 pm on October 4, 2013 Permalink | Log in to Reply

      Hello @isaackeyet
      We need help with “RTL issue” in Uzbek translation, please: http://android.trac.wordpress.org/ticket/516

      • Isaac Keyet 4:21 pm on October 8, 2013 Permalink | Log in to Reply

        To respond to your comment on that trac ticket a validator would be the one approving suggested strings. You should seek out the Uzbek translation community to see if you can get help with that (not a bad idea to stay in sync with them anyway).

    • SeriousOwl 3:50 pm on October 8, 2013 Permalink | Log in to Reply

      I can help with Indonesian :D

      • Isaac Keyet 4:19 pm on October 8, 2013 Permalink | Log in to Reply

        That’s great! The iOS and Android projects are already 100%, but with each update of course additional help is needed for new/updated strings. You can also look into the Windows Phone and BlackBerry projects (also in GlotPress).

    • Isaac Keyet 4:05 am on October 9, 2013 Permalink | Log in to Reply

      @vanillalounge, can we get Maxime Biais added to Polyglots? His username is “mbiais” and he’ll be helping us on the French side moving forward.

    • mshastchi 3:31 pm on October 11, 2013 Permalink | Log in to Reply

      The persian WordPress team officially stated that they do NOT have any plan to translate any other WordPress project except for WordPress itself, so it is needed that some new validators come into work to translate other projects. I want to contribute to translation of WordPress Apps in particular (I also like bbPress).

      • Isaac Keyet 4:23 pm on October 11, 2013 Permalink | Log in to Reply

        Persian is currently unsupported by Apple’s iOS itself, I’m a little unsure about Android but it might be a good idea to get in there.

        • Nazarzadeh 12:58 pm on October 13, 2013 Permalink | Log in to Reply

          There’s a LOT of Persian app’s for both Android and iOS, don’t worry if we translate it, it will work.

        • vmahdavimehr 11:48 am on October 14, 2013 Permalink | Log in to Reply

          i also can help with the Persian translation, i also can be a validator but not sure about the regulations and stuff

        • mshastchi 8:40 am on October 23, 2013 Permalink | Log in to Reply

          Still waiting for answer!

          • Isaac Keyet 9:46 pm on October 30, 2013 Permalink | Log in to Reply

            @vanillalounge or @defries are you able to help?

            • Ze Fontainhas 2:25 am on October 31, 2013 Permalink

              It’s really a decision of the Persian team, we shouldn’t be going over their heads… This has probably to do with the fact that we do not yet support validators per project (i.e. a validator is a validator on every project), and maybe they can be talked into opening new validator slots for projects other than WordPress itself. Maybe @mshastchi can ask them to take a look at this thread and take a stance?

            • mshastchi 9:31 am on October 31, 2013 Permalink

              I’ve contacted them but no answer! but now with WordPress 3.7 they (he) are back again! They (he) want help for translation of 3.7 and then they will decide.

  • Ze Fontainhas 1:39 pm on May 28, 2013 Permalink | Log in to leave a Comment
    vanillalounge • pt.wordpress.org editor  

    Could we try to schedule a polyglots chat this Thursday or Friday (if not too late in the evening)? I’d love to have @catiakitahara, @defries, @nacin and anyone who wants to contribute. My suggestion is that we decide a course of action for the handbook and for the global/worldwide page, but we can adapt if anyone feels there are more pressing matters.

     
  • Ze Fontainhas 5:04 pm on October 3, 2011 Permalink | Log in to leave a Comment
    vanillalounge • pt.wordpress.org editor
    Tags: , ,   

    This might be more interesting for @defries right now, but will probably be for others too, in time ;)

    http://translate.wordpress.org/projects/wordcamp-theme

     
  • Ze Fontainhas 11:09 am on October 3, 2011 Permalink | Log in to leave a Comment
    vanillalounge • pt.wordpress.org editor
    Tags:   

    If you are planning on running your own instance of GlotPress (see StudioPress‘ and Yoast‘s), take a look at this very helpful guide, written by @defries. Also interesting for those looking to submit patches.

     
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