 Okay, let's start. Good morning everyone. My name is Mayo and I'm one of Japanese translation editor. Today I'm going to talk about WordPress localization. I choose this topic for Singapore. I don't speak English. It sounds weird, but I choose it because in the past work camps I saw a lot of talk about localization and internationalization and they always say internationalization is important, but I'm always wondering, maybe English people don't understand my situation. So I choose this topic this time. So let's see how many of you speak English as first language. Can you? Yes. Okay, so how many of you speak only English? Ah, okay. And how many of you speak any other language besides English? Ah, a lot. Yes, okay. Okay, so today for first I'll talk about how it works, what WordPress translation is, because some of you might not see, never try WordPress translation. By the way, how many of you only try English version of WordPress? Ah, a lot. Thank you. I was expecting that. So then after we will see the situation about localization from my point of view as Japanese. And then I'll talk about how you can collaborate with community of translators. So let's start about how it works. Maybe you have seen this screen when you install your WordPress from WordPress point point zero, you can select language which you want to use it during the installation process. When you select the language besides English, WordPress will download language file from WordPress.AllServer into the language folder which placed on the therapy content directory. WordPress uses Getex function as internationalization functions. It was not only developed for WordPress, but it's created by GNU operating system. So let's see how Getex call translation strings. So it is Japanese version of WordPress dashboard. And the red line, it says, welcome to WordPress. So and this is a source code of the screen. And you can see it's between the opening tag and the closing tag of H2. And we call function GetText using PHP. So this is source code. And this is a content of language file. WordPress downloaded from .all repository. So it makes pair of original string and translated one. So this is a translation editor of WordPress core named GloPress. It works on the web browser. So we can collaborate to working for translation strings online. We are currently working for WordPress 4.9. It's scheduled next month. So we started working from three weeks ago. And we check new string every day. And we add new translation. Then every day, new translation file generate and send it to WordPress who use beta version. And when we finish translation or update string, it happens. And the language file settings are not only translation, but they have a lot of settings for language or countries. For example, default time zone. So language file, a specific file. Not only language, but location. Like Japanese language code is only JA. But if you use for example English in US, language code should be EN under the word US. So because English is used by many countries. So language file also has localized settings. Like time zone and data and time format, news source, news of, you know, if you so see dashboard, WordPress news appeared. And translation file also defined the source of news. And also content count system. Do you know that if you use content editor or WordPress, you can see the word count. But you know, Japanese don't split words by space. We don't need, we don't use space. So we have to count by character. So language file also has that kind of settings. So this is about WordPress core translation. But WordPress localization is not only about core. So I'll talk about local community. And I'm a Japanese. So I'll talk from my point of view. And so here are three facts of Japanese and WordPress. Fact one, did you know first version of translated version of WordPress is what Japanese? Yes. So we started translated version over 10 years ago. Fact two, 80% of website which use Japanese version, no, no, no, no, sorry. It was wrong. It was wrong. I wanted to say 80% of website which use CMS and which use Japanese language are a bit with WordPress. So I wanted to say a lot of people in Japan use WordPress. WordPress is strong. And a lot of WordPress developers, including me, haven't read English articles. Yeah, I became WordPress developer without reading English articles. Yes, because we have translated version of Codex. Codex is WordPress documentation. So we can see it's reference of, it is reference of function gets post meta and it's translated. And we have a lot of pages. So I didn't read English article to become WordPress developer. And we also have a lot of three. This is Amazon, Japanese version of Amazon. And we have a lot of Japanese books. It's excluded Kindle, but we have 341 books on Amazon in Japan. And I think I think in this room we have author of first book and second book. And we also have support forum. So, and the screen is too small, but first one, first one was updated nine hours ago. And third one is ten hours ago. So it's very active. So if you have program about WordPress, you can ask in our language. So, yeah, now I speak English because I wanted to come here. But yeah, I didn't read any English article to become WordPress developer. And if I have some program, maybe I saw some error message on my dashboard. It's Japanese, but I can copy it and paste it on Google. And I can find some answer from this forum or blog post written in Japanese. Yes. And this year or last year, I really surprised one, another language translation editor of WordPress said they don't translate error message because engineer can read English and they need to use Google. I was so surprised and shocked. Yeah, if WordPress showed me some English error message, maybe I cannot become WordPress developer because I didn't speak Japanese or no English. Sorry. Yeah, it was shocked. So next, I'll talk about collaborate with community. So I already say we use Glopress for translate WordPress core and we also use it for plug-in theme and content of WordPress.org, like plug-in repository forum. And we are working as a team. So this is the member of Japanese translation editors. And we use currently, we also use Slack and we also have Google group and we discuss if we have some problem or something in negotiation. And so we can keep quality. We have translation guideline for Japanese version of WordPress. We have a lot of way of write and it's very hard to explain in English, but we need guideline. We speak Japanese. All of Japanese can speak Japanese I hope, but we need guideline. Like English also has a lot of way to write. And so WordPress elements screen need to use the same format. So if you put some string suggestion or word Glopress because everyone can put suggestion, so you can. But if the string is not on the format, that editors will edit. So this is a system to keep quality. And we also grow new contributors. We have, we always have made up and we invite new contributors like who submit translation suggestions. And we also have global polyglot team. This is a photo from Contributor Day of World Camp Europe last year. There are a lot of people. And so all of them speaks some language beside English. And all of us have some problem with our language. Japanese has Japanese problem and another language has another specific problem. So we can help, we always help each other. Like we also have place to communication. This is make.org. This is our home to discuss something. And we also have Slack channel polyglot and we have weekly meeting. So if we have problem, we can help each other. So we have strong connection. So if you have some project of WordPress, like if you are author of plugin, if you are author of theme, or if you create some product with WordPress, and if you want to ask someone to use it, maybe you can consider localization. And you can ask community member to help translation. Because sometimes I can translate WordPress plugin themes. So sometimes when I go to work camp and I meet some theme author, and they ask me to translate their theme. And I saw their source code. And sometimes I cannot, we have problem to translate because of original string. So that time we can talk because I have knowledge of WordPress translation. So it's easy, but sometimes I already told you, everyone can suggest translation, but sometimes people use Google translate and just put it. And they never understand Japanese. But we don't want to check all of strings in that case. So, and if, even though you hire some professional translator, maybe they should understand guideline I already show you. So easiest way is you ask polyglot community member first, then work together. And one more tip, if you put source code on GitHub, it's easier to collaborate. Sometimes on WordPress or repository, I find some string error for translation. And I ask them to fix, but they don't answer. But if you have source code on GitHub, it's easier to send pull request. Okay. So thank you. I'm Maya and I'm also polyglot team member and community member. And tomorrow we have contributor day. And if you have any question about polyglot and community team, ask me. Thank you. Okay. Thank you, Mario. Do we have any questions for her? Anybody from the floor? So, if you have a WordPress plugin or a product or something, what's the best way to get it translated into Japanese? Best way? Yeah, the best way to get it translated. If you don't speak Japanese. If I don't speak Japanese and I have a WordPress plugin or a WordPress team or a product or something and I want to get it translated into Japanese, what's the best way to do that? Of course, you can ask me. And yeah, sometimes, you know, they're a long queue for translation approve. But I already told you, sometimes people use Google translate and I don't want to review. We don't want to review all. So you have to remember they're a long queue. So sometimes people ask us to translate by like hire us. And it also works. Yeah. So sometimes we our branch here collaborate together and we get money from that. And I use PayPal account to correct money. And now I'm saving money for go another work camp. So you can help contributor. Any more questions for Mario? Hi, my name is Stan. Thank you very much for sharing today. I have a question. Is there any tool or plugins that you would recommend that can identify the origin from where your users are coming and then set the language according to the users? So for example, if someone visits my website from Japan, it will be automatically displayed in Japanese or from Russia than Russian and so on. Is there any plugin or tool that you would recommend for that? So you want to switch language? Yes, the website automatically identifies where the person... Do you want to say something? Or anyone else? Really? Cool. There are several ways you can do it. You can use a language switcher. What I usually do when people want multi-lingual sites is I use multi-site and then have individual sites translated. It's a bit of a pain to do it that way, but the geo plugin for the different domain mapper for multi-site allows you so you can have a .co.jp and then use the geo locator plugin to say anyone coming from Japan, load the .co.jp website, which would automatically be Japanese. I think Polyglot allows you to do with the geo plugin, but it wouldn't be difficult to do geo location stuff because there's already a plugin that does that for domain mapping. So it would be very easy for you to then just say instead of doing domain mapping, do language switch. So if something doesn't exist, I could probably write you something. So come talk to me. Cool, thank you. Any question? Don't be shy to ask. Hello. Thank you for the talk. I have a client who they wanted a multi-lingual site, but they did not want to pay for a multi-lingual site. And we're Australian. And so what we ended up doing was we used Google translate plugin. Google translate. Is that okay? It depends, but in most of cases I don't think so. It's a scientific website about marine ecology. How do you think? How do you think Japanese guys is easy? Google translation is, as my opinion, Google translation is very good for Western and European languages between English to French or French to English. I think I guess it's okay and very natural, but English to Japanese is very horrible. So if you want to do business in Japan, you shouldn't use Google translation. It looks like very stupid. Beautiful design and stupid language. It's very horrible. So Japanese people think, okay, they don't have business in Japan. They realize. Did we have a problem? Yeah. Actually, I'm just going to add to that the reason why Western languages are okay with Google translate because of the grammatical thing which I'm not going to get into. But the grammar is easier for Google to translate automatically by algorithm. And also because the Western languages are like the major languages, it got translated first. I'm from Manila, Philippines. So like Japanese, our grammar from English is so different. Like it's the reverse. So before when you translate to Tagalog, my language, it's ugly. It's like, no, I'm not going to use that. It's so cringy. But the thing is Google does also have a volunteer pool. So Filipinos started translating and now it's a little more acceptable, but it still has to be tweaked. That said, for example, if you are looking for doing business in Japan, if you really have to, if you want to use Google translate, you have to depend on the Google translators from Japan if they want to do it. So if you're very specific to a certain country, maybe it would be better to just make a multilingual side. It really depends on what the client wants. They have to put money where they want it. I thought I just wanted to add something. Because languages, I run a translation company and I used to work for a company that worked for Google. And for their own products, they do not use their own Google translate to translate their own products. So yeah. Google relies on professional translators for their own business. They do not rely on Google translate for their own business. What was the question? The comment. Thank you.