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 for general updates, status reports, and debates.

We’d love for you to help out.

Translate WordPress

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.

Weekly Meetings

We a weekly meeting on Slack in #polyglots, Wednesdays at 10:00 UTC. If you have any questions, bring them to the weekly chat!

Posting here

In order to post to this site, you will need to log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow our tag policy when posting.

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Siobhan 1:23 pm on July 28, 2015 Permalink |
    Tags: , subtitles   

    Subtitles for WordPress 4.3 

    Hi polyglotters!

    The WordPress 4.2 video was the first one that we created subtitles for. It was great to be able to provide subtitles, although I think we had varying degrees of success with the overall workflow. We’d like to provide subtitles again for WordPress 4.3.

    I’d like to refine the workflow and make it a better and smoother experience. You can find the workflow that we used for 4.2 here.

    In brief, what we did was either:
    1. Translate through a web interface, or
    2. Translate the XML file directly

    The files were then emailed to me.

    I would be okay with using the same approach again this time but not everyone found the experience to be smooth. So if you have feedback and a suggestion for a better workflow that we can implement, please let me know on this thread.

    Some dates for your diary:

    • the final cut of the video will be made available by 12th August for translation
    • I will need to receive subtitles by 15th August.
    • Xavier Borderie 2:19 pm on July 28, 2015 Permalink | Log in to Reply

      I am unsure about the web interface. It was not ideal, being small and prone to crashes (I had at least one, IIRC).
      A file is nice, but it’s hard to share, and hard to adapt to local words. That, and translators who are not used to XML might break the file unknowingly.

      How about using https://amara.org/ ?

      • Siobhan 3:17 pm on July 28, 2015 Permalink | Log in to Reply

        The problem with using Amara is that the video becomes public before we actually launch, and it’s nice to launch the video at the same time as the release. In the workflow we used last time the video was accessible but only to people with a link.

        • Xavier Borderie 3:36 pm on July 28, 2015 Permalink | Log in to Reply

          Understood. Amara indeed doesn’t seem to have a private way of subtitling videos. You could always try an audi-only video, in order to keep the style/effects private, but that would certainly leave the release’s jazzperson available in the audio — and that’s kind of the only thing we want to keep for the final reveal :)

          • Siobhan 4:13 pm on July 28, 2015 Permalink | Log in to Reply

            I could leave the jazzer out of the audio. Just have “jazzer” and then I can go through the subtitles and manually update them.

            • Samuel Sidler 8:18 pm on July 28, 2015 Permalink

              I like both of these ideas. :)

              I wonder if there are ever reasons why you’d need to see the video to the captions well, though. Timing and such.

    • Alvaro Gois dos Santos 2:26 pm on July 28, 2015 Permalink | Log in to Reply

      Sixty strings or so? I’d bet on translating the XML file directly (Portuguese). It’s probably not the best way for every language, I guess.

      So, when will we have the final XML for translation?

    • Adrian Pop 2:52 pm on July 28, 2015 Permalink | Log in to Reply

      If the player will be the same as for 4.2 Is not worth translating in Romanian because the UI for selecting a subtitle does not allow scrolling. Therefore the Romanian subtitles are not visible or selectable :(
      see: http://snag.gy/lmLSl.jpg

      • Siobhan 3:14 pm on July 28, 2015 Permalink | Log in to Reply

        I believe this is being fixed but @samuelsidler can confirm.

      • Samuel Sidler 8:20 pm on July 28, 2015 Permalink | Log in to Reply

        We will not be using the same video player for this release. Ensuring that all translations can be selected is a high priority in determining which video we ultimately use.

        I can’t promise that the video player in 4.3 will be perfect, but it will be much, much better.

  • Dominik Schilling (ocean90) 7:47 pm on July 26, 2015 Permalink |
    ocean90 • de.wordpress.org editor
    Tags: , ,   

    translate.wordpress.org: BuddyPress and bbPress are now part of the Plugins tab 

    Hey everyone,

    we’ve moved the BuddyPress and bbPress projects to the plugins tab in your locale overview, means they are now listed at https://translate.wordpress.org/projects/wp-plugins. The stable and development projects are moved 1:1 to the new path.
    Projects for older versions are archived and can be accessed at the old URLs, https://translate.wordpress.org/projects/bbpress/ and https://translate.wordpress.org/projects/buddypress/.

    If you have Translation Editors for both of the projects please update their permissions. It’s now possible to add Translation Editors to sub-projects like BuddyPress or bbPress. 🎁 (If you found something broken please report it at the comments or in #1101.)

  • Dominik Schilling (ocean90) 11:52 am on July 23, 2015 Permalink |
    ocean90 • de.wordpress.org editor
    Tags: ,   

    WordPress 4.2.3 has been released. It is a security and maintenance release. There are no string changes.

    In order to benefit from the automated release process it could be possible that you have to prepare your locale first.

    Translations must be at 100%

    (This includes wp/4.2.x, wp/4.2.x/admin and wp/4.2.x/admin/network.)

    Update version in readme.html

    • If you have custom changes on i18n.svn.wordpress.org and you are using branches/4.2 to release your package you only have to change the version in readme.html.
    • If you’re using tags/4.2(.2) you have to create a new tag for 4.2.3 first. It’s just a copy of tags/4.2(.2) or trunk and the version change to readme.html.
    • If you have tags/4.2(.2) and branches/4.2, but no tags/4.2.3 the build will use branches/4.2.

    Also released: 4.1.6, 4.0.6, 3.9.7, 3.8.9, and 3.7.9.

  • Petya Raykovska 11:55 am on July 22, 2015 Permalink |
    petya • bg.wordpress.org editor

    Notes from the Polyglots chat on July 22 

    Locale stats

    Releases: 151 locales. 55 locales up to date. 3 locales behind by minor versions. 7 locales behind by one major version. 15locales behind more than one major version. 56 locales have a site but never released. 15 locales don᾿t have a site.

    Translations: 151 locales. 10 locales at 100%. 44 locales have more than 95%. 7 locales have more than 90%. 21 locales have more than 50%. 55 locales have less than 50%.

    We have several new locales and new translation editors and processes are in place to add even more translation editors to the Armenian and Uzbek teams.

    The Development project for 4.3 is already available for translation.

    Weekly #metai18n meeting recap for Polyglots

    Notes from the meta team chat (encouraging everyone that’s not following the channel and is interested in more than translating to join, weekly chats on Tue, 11am UTC).

    Highlights from this week

    • Italian forums are online (win!)
    • Themes are being imported, all should be on translate.wordpress.org by the end of the week
    • Sorting and prioritizing projects is high on the meta team’s list for dev (see next point of the agenda)
    • @ocean90 started testing plugin imports with selected plugins

    Translation Project Sorting Ideas

    @samuelsidler posted some ideas about sorting projects once themes and plugins get imported and the meta team needs our feedback. Ideas include:

    • Prioritizing by popularity: Projects could be organized by how popular they are, that is, how many users and/or downloads they have.
    • Prioritizing by fewest strings remaining: If a project is almost complete – e.g., just a few strings away – it can be considered higher priority.
    • Prioritize by permissions: Show projects you have permissions for first.
    • “Hide” fully translated projects
    • Starring or Favoriting: Giving translators the ability to “favorite” a project and have it raise to the top. A new “tab” for “Favorites” that could be the default if a translator has favorites. Use a user’s favourites from the plugin and theme directories.
    • Sort by waiting: Translation editors should be able to see which projects have waiting strings so they can approve them. Within this view, we should probably prioritize projects based on some of the ideas above.
    • Improved search: Translators should be able to search by author name (theme or plugin) and see a list of their projects, for example.

    More ideas from the Polyglost team:

    • Some polyglots expressed concern about using plugin/theme repo Favourites for translations
    • There was a suggestion for a page for Favourites from the repos and a separate one for Installation Favourites
    • We discussed use cases for TE and Translators in terms of sorting and default views, most people weren’t keen on hiding projects that are 100% translated.

    WordPress 4.3 – soft freeze update and release dates

    • RC1 coming on July 29 together with the soft freeze
    • Discussed some open issues on HTML in strings that couldn’t make it into 4.3
    • There was a mutual agreement to keep bugging @ocean90 for those
    • We’re waiting on the core team to give us the heads up for the date of the hard freeze (aka all strings get frozen including the About page)
    • Release of 4.3 is still scheduled for August 18th

    Open discussion

    • There was a request to post the agenda for the chat on Tuesday. If it makes more sense to people I will try posting on Tuesday after the #metai18n meeting



  • Petya Raykovska 8:58 am on July 22, 2015 Permalink |
    petya • bg.wordpress.org editor  

    Agenda for the Polyglots chat on July 22 

    Dear polyglots,

    Here’s a quick agenda for today’s chat:

    See you on Slack at 10am UTC.


  • Tarei King 10:59 am on July 21, 2015 Permalink |
    tareiking • mri.wordpress.org editor • en-nz.wordpress.org editor
    Tags: en-nz,   

    Kia ora, lets add en_NZ as a locale 

    Requesting an additional locale for New Zealand to be added with the details below:

    Locale: en_NZ
    Country code: NZ
    Plural forms: nplurals=2; plural=(n != 1);
    Language native name: English New Zealand
    Sub-domain: en-nz.wordpress.org
    Site Title: English ( New Zealand )
    Site Description: WordPress in English ( New Zealand)
    Admin Username(s): tareiking, toherangi, ryanhellyer, wealthy, jjripikoi
    Admin Email: ping me on slack for it 😀

    Also, if anyone knows anyone who might be interested, please have them ping me :)

  • daniluk4000 8:10 pm on July 20, 2015 Permalink |
    Tags: , , , theme check   

    Okey completed the Russian translation of Theme Check… 

    Okey, completed the Russian translation of Theme Check. So how it can to be added?

  • Petya Raykovska 12:40 pm on July 15, 2015 Permalink |
    petya • bg.wordpress.org editor

    Notes from the Polyglots chat on July 15th 

    • All TE of locales with language variants, please write a request on make/polyglots for the option to be added for your locale. Requests should include a slug (like `formal`), the english and native name of a variant.
    • Let’s document the different language variant usecases we have now, @alvarogois, @dimadin @gluekpress, could you describe your particular usecase and how you have handled things prior to this?
    • A quick reminder you can translate 4.3 strings in the development project now. The teams page shows the progress of locales on the 4.3 dev branch. This, as mentioned last week, will also give you the opportunity to test translations if you have the beta tester plugin running in your install
    • Themes and Plugins are coming to the repo (https://make.wordpress.org/polyglots/2015/07/14/translating-themes-and-plugins/), minimal requirements for TE to be added as per project validators:
      • Description including projects and locales they’re taking care of
      • Slack name (unless limited by a technical issue)
      • Other means of communication – email, twitter or other social account 
      • Gravatar
    • Plugins and themes who do not want dotorg translations (language packs from translate.wordpress.org) can “opt-out.” The way for them to use their own translations, instead of ones from translate.wordpress.org is to… do nothing. Or, to keep doing what they’re currently doing. Translations that are shipped with themes/plugins take priority to language packs. WordPress will use them first and not download the language pack.

    • We’d love the accessibility team’s input on these requirements – Taco to pint Rian for her opinion
    • The process for plugin/theme authors to request external validators for their plugins/themes to be added is described in https://make.wordpress.org/polyglots/handbook/rosetta/theme-plugin-directories/#requesting-new-translation-editors
    • Handbook updates: In august Petya will organise a handbook sprint for all handbook pages that have been reported to have issues. To help this process along, you can either report issues (slack or make/polyglots blog) or if you want to get involved more, request to be added as an editor to the handbook. The translation sprint will have tasks outlined for everyone who wants to join in to claim and work on. 
    • Polyglots team volunteers – with a lot more people joining the polyglots community, we need all the help we can get to help people with locale requests, questions, new validators orientation, documentation. If you’d be interested in helping out with any of the tasks below, please raise your hand in the comments:
      • Answering people’s requests on the polyglots P2
      • Doing locale research for new locale requests – includes checking the request on the p2 and communicating with the person requesting the new locale, ensuring the ISO-3 codes are correct, adding information about how many people speak the language, double-checking plural forms, creating a ticket on the GlotPress track with all the information needed to add a new locale. (You will be trained by Petya)
      • Monitoring feature requests/bug reports from polyglots and filing those as issues on the meta track




    • Alvaro Gois dos Santos 2:37 pm on July 15, 2015 Permalink | Log in to Reply

      Thanks @petya. As to variant usecases, you want us to describe them here?

      • Petya Raykovska 3:33 pm on July 15, 2015 Permalink | Log in to Reply

        Yes, Alvaro, let’s get them all here and we can work out how to add them to the documentation after.

      • Alvaro Gois dos Santos 9:07 am on July 20, 2015 Permalink | Log in to Reply

        In pt_PT we have 3 language versions: default, which is formal (and old orthography), informal (also old orthography) and the new orthography formal, not yet in GlotPress.

        The Portuguese Language Orthographic Agreement of 1990 (AO90), the new orthography, is 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. There is still hope that this Agreement is rectified, if not disposed, at least to eliminate it’s most absurd flaws.

        A while back we had a 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 was no alternative for those who wanted or needed to have WordPress in accordance to AO90. On the other hand, it’s not fair either to automatically update an orthography (with a new WordPress version) for thousands of users without their consent. That’s why, in the meantime, we came up with a plugin solution for this: PT Variants.

        There’s also the issue of maintaining two versions (three, if we include informal, which has almost been an one-man-project), regarding consistency of terms and available resources. There’s software that can automatically convert old to new orthography, therefore, consistency can be kept in the current form. But the ideal way, IMO, would be to integrate variants in GlotPress in a side-by-side flow. Since only some of the strings actually differ, it would be easier to maintain variants this way, using the default version as a fall-back for not yet translated or equal entries.

        • Samuel Sidler 1:08 pm on July 20, 2015 Permalink | Log in to Reply

          I can see why that feature would be ideal for you. There aren’t very many locales with variants, however. Speaking for the meta team, this isn’t something we’re going to spend time on as there are other, higher-priority things that we need to work on, which affect all (or most) locales.

          If someone from the Portuguese community wants to work on this for GlotPress, I’m sure we would enable it on translate.wordpress.org shortly after the feature was committed to GlotPress.

    • duytrung2121 12:27 pm on July 18, 2015 Permalink | Log in to Reply

      Hello Petya!
      I see bbPress support many language but without Vietnamese, So, can you add Vietnamese to bbPress project to translate? Thank you.

    • Milan Dinić 10:37 am on July 21, 2015 Permalink | Log in to Reply

      Here is description of Serbian case as mentioned in the meeting.

      Why we have this? Wikipedia says that “Serbian is practically the only European standard language with complete synchronic digraphia”. What that means is that both Cyrillic and Latin script are used, one letter from Cyrillic can be transliterated to Latin and vice versa, they are pronounced exactly the same, and that every Serbian speaker understands both.

      Automatic transliteration from Cyrillic to Latin is practically 100% safe. Theoretically you can do that from Latin, but in reality that is not an option because you can use Western words like ‘WordPress’ or typos like c, č, ć (in Cyrillic quite different ц, ч, ћ) etc. That is one of the reasons why texts that should be available on both scripts (like translations) are made in Cyrillic and then automatically transliterated.

      That is what plugin in /dist does, when turned on, simply replaces each letter from Cyrillic to Latin thus enabling Latin translation. It was proposed on mailing list (thats why Finnish guy made it, wasn’t that into WordPress then) more than seven years ago since otherwise we would have another locale to maintain which is completely same, only difference is writing system.

      Since ditching of /dist is announced, I have thought about how to solve this. What shouldn’t be done is starting new locale and treating it as a separate language as it’s really not. Problems are that no human can manage this as there are many projects with same repetitive work done, confusion for users as to where to contribute, many unfinished or duplicated work in both sides, many wasted time and energy, etc.

      I think that @nacin first mentioned idea that I am more toward it, especially when formal variants are introduced. That is doing work on wordpress.org that would make language pack for Latin from Cyrillic translations on the fly.

      So how would this work:

      • Create new code, lets name it sr_RS@Latin for now, that is only exposed through API, so it would appear in dropdowns in WordPress but no separate locale site or GlotPress projects.
      • Create language packs from GlotPress exports as usual. When sr_RS is processed, also create language packs for sr_RS@Latin from the same base using code like in our plugin to automatically transliterate. Save additional data about package if needed for API.

      This way users could switch to that variant and stop shipping plugin with each release while it will still be untouched on older installations so we would have backward compatibility.

      I know that this involves some work on meta side (I would gladly contribute but that part is private, I think), but is far less than having two locales, and it’s the only idea I can get right now. Other proposals are welcome.

  • Petya Raykovska 8:39 am on July 15, 2015 Permalink |
    petya • bg.wordpress.org editor

    Agenda for the Polyglots chat on July 15th 

    Hey everyone,

    Here’s a quick agenda for the chat today. As always, feel free to add things you feel we need to discuss:

    • 4.3 Language variants
    • 4.3: A reminder we can start on the strings
    • Themes and Plugins in the repo – latest developments and what it means for polyglots
    • Adding per project TE – let’s figure out and document best practices
    • The WordCamp Android app needs translators
    • Handbook update sprint – with so many people coming on board, we need this more than ever
    • Expanding the Leadership team – call for volunteersno

    See you in Slack at 10am UTC!



  • daniluk4000 8:08 am on July 15, 2015 Permalink |

    My plugin 

    How can I add my plugin for translation, and whether it is freely available in the future?:

    • Alin Marcu 8:37 am on July 15, 2015 Permalink | Log in to Reply

      From your locale administration screen, go to Users -> Translation Editors and select “Custom – After the user is added you will be redirected to set the projects.” before adding the user.

      • Petya Raykovska 9:18 am on July 15, 2015 Permalink | Log in to Reply

        @deconf I’m not sure that was the question Daniluk4000 was asking :)

        @daniluk4000 all active plugins in the repo will slowly be enrolled to translate.wordpress.org, you, as the plugin author, don’t need to do anything for your plugin to be added.

        It’s a bit early for this to happen to all plugins though. The meta team will start with a few, there are a lot of things to take into consideration for this to scale, so please be patient and follow the #metai18n chats and the polyglots blog for further developments.

    • daniluk4000 8:40 am on July 15, 2015 Permalink | Log in to Reply

      @deconf Im Translation Editor yes but I haven’t admin permissions for add new users and manage_options :)

  • Will Kwon 8:13 pm on July 14, 2015 Permalink |

    WP Android 4.3 

    Hi everyone! We’re shipping WP Android 4.3 on July 20th and we could use some help with some translations. Would you mind helping us out by translating the release notes and the app strings?

    Release notes: https://translate.wordpress.org/projects/apps/android/release-notes
    App Strings: https://translate.wordpress.org/projects/apps/android/dev

    Thanks in advance!

    • Milan Dinić 9:53 am on July 19, 2015 Permalink | Log in to Reply

      I am translation editor for Serbian language (which is at 100% for this project now, BTW) and I want to point at one thing I noticed.

      Since the begging of availability of Serbian language in app (I think two versions back), when you install app from device with Serbian language of Android, app is immediately in Serbian language, like it should be.

      Problem is that release notes are still in English even though they are translated and they can be in Serbian which is proved by other apps (ones from Google most easier to spot).

      I investigated a little and I think that problem might be since there is no Serbian language in this file.

      Could you please look at this before next release? Thanks.

  • Samuel Sidler 6:44 pm on July 14, 2015 Permalink |
    Tags: , meta, ,   

    Translating Themes and Plugins 

    Howdy all you wonderful polyglots!

    We’re getting very, very close to turning on translations for themes and plugins. Within the next few days (or weeks), we’ll start importing active themes and, shortly there after, plugins to translate.wordpress.org.

    The first import might be a bit… painful. There aren’t a lot of sorting options built-in to GlotPress, so importing, say, 1500 themes will make it hard to see which theme is important. We’re working on that. After import, it will be important to use translate.wordpress.org and find “pain points” in the experience. Then… let us know! You can file a ticket on meta trac with an idea for improvement and we’ll work to improve things over time. Or, you can ping me personally (sam on Slack) or even just leave a comment here.

    For themes and plugins with their own, external translation sites, we’re recommending the author post here on make/polyglots with a list of their translation editors and request that they be added to translate.wordpress.org with project-level permission. That means that they’ll only be able to approve translations for the specific theme or plugin, which they can already approve translations for on an external site.

    That might sound a bit complicated, but I wrote up a handbook page with all of the details. Please read through and let us know if you have questions.

    One thing I’m recommending to everyone is to follow a hashtag for your locale. For example, the Swiss German translation editors would follow #de-ch in their WordPress.org profile notifications. Any time, across WordPress.org, someone enters #de-ch, they’ll receive an email notification about it. It’s a great way for anyone “in the know” to ping translation editors and entire teams.

    P.S. If you haven’t already, now is a great time to translate the theme and plugin directory interfaces.

    Related posts: Meta team, Theme team

  • Tarei King 1:34 am on July 13, 2015 Permalink |
    tareiking • mri.wordpress.org editor • en-nz.wordpress.org editor

    I’m looking to get some translation started for NZ Maori. The locale is available (https://glotpress.trac.wordpress.org/browser/trunk/locales/locales.php#L1267), but has no projects to translate

    Is it possible to add projects to https://translate.wordpress.org/locale/mri for translation?

    Strangely it was available last week at https://translate.wordpress.org/locale/mri/default, but not today.

  • Belvar 10:16 am on July 11, 2015 Permalink |
    Belvar • bre.wordpress.org editor
    Tags: ,   

    I see there is a breton translation page ( https://translate.wordpress.org/locale/br ) but no team.
    Would it be possible to create a team for Breton, and to set up a validator ?
    Some people have started translating but there is currently no way to validate their suggestions.
    Thank you

    • Dominik Schilling (ocean90) 8:59 pm on July 13, 2015 Permalink | Log in to Reply

      Hello @Belvar,

      yes, it’s possible to create a team/site for Breton. Are you currently alone? Do you know others who can help you with the translation?

      To create a site I need some details from you. Since the locale exists already I just need the last four points from the list.

    • Belvar 9:10 pm on July 14, 2015 Permalink | Log in to Reply

      We are currently at least two translators :
      Me, @Belvar and @Vardick
      Some other translators may join in the future.

      The site title would be : Brezhoneg
      The site description : Troidigezh WordPress e brezhoneg

      thank you very much

    • Belvar 9:14 pm on July 14, 2015 Permalink | Log in to Reply

      seems like the email addresses were counted as HTML, so here they are :
      “tornoz AT laposte DOT net” for me and “stefan AT stefancarpentier DOT com” for vardick

      • Petya Raykovska 2:50 pm on July 17, 2015 Permalink | Log in to Reply

        Hey @belvar :)

        I’ll get on to creating a site and adding you as the team so you can start translating. Will keep you updated.

      • Petya Raykovska 5:46 pm on July 17, 2015 Permalink | Log in to Reply

        Hey @belvar,

        Both you and @vardick are now editors of https://bre.wordpress.org/

        Here are a few useful places that I’d recommend you check out:

        Please read the Handbook carefully in the part that explains general expectations for translating: https://make.wordpress.org/polyglots/handbook/translating/expectations/

        Setting up the local site is also one of the things you’d want to do: https://make.wordpress.org/polyglots/handbook/rosetta/setting-up-your-local-site/

        I would suggest posting on the local site that you’re looking for people to help out with translations. You can set up the contact form to get to your email address so that local community members can reach you.

        To encourage translators to keep the work on the locale consistent, I would recommend creating a Glossary with common terms.

        Please feel free to post here if you need any help or advice.

        Welcome to the team and happy translating!


      • Petya Raykovska 6:04 pm on July 17, 2015 Permalink | Log in to Reply

        One last request. I noticed both your and @vardick‘s profile on wordpress.org is empty.

        We ask all Translation Editors to have full profiles on w.org, so that translation contributors can contact them and for image purposes also – active contributors should set an example for the rest of the community.

        If you can go ahead and fill your bios, add your emails to gravatar and register on https://make.wordpress.org/chat/ (Slack), that would be ace.

        We also have weekly Polyglots meeting in the Polyglots channel on Slack if you have questions or are interested in participating.

        Have a good night!

  • Anvar Ulugov 8:32 am on July 11, 2015 Permalink |
    Ulugov • uz.wordpress.org editor

    Dear moderators of Uzbek language, please review my translation, I’m waiting to continue.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc