<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">Le 24 mars 2017 à 18:28, Jeff Kelley via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">One of the things that struck me from today’s Apple press release about Swift Playgrounds being localized in more languages is this screenshot:</div><div class=""><br class=""></div><div class=""><span id="cid:4E5A7475-A760-469E-A915-125574AAC56B"><cn_playgrounds_looping.jpeg></span></div><div class=""><br class=""></div><div class="">All of the UI is fully localized for Chinese, <i class="">except</i> the actual code. As far as I know, almost every major programming language and major platform framework is primarily English; it’s become the <i class="">de facto </i>language for developers. But does that have to be the case?</div><div class=""><br class=""></div><div class="">Imagine a world where alongside our Swift frameworks, we ship <font face="Menlo" class="">.strings</font> files that contain translations of our APIs to other languages. From some other screenshots we see that Swift Playgrounds is providing translations of method names to explain them, here providing “avanzar” for “<font face="Menlo" class="">moveForward()</font>”.</div><div class=""><br class=""></div><div class=""><span id="cid:9D276CBF-C25F-4942-A868-F0775B651711"><sp_playgrounds_stepping.jpeg></span></div><div class=""><br class=""></div><div class="">A scenario where Swift supported localized frameworks might see a <font face="Menlo" class="">.strings</font> file with a format like this:</div><div class=""><br class=""></div><div class=""><font face="Menlo" class="">"moveForward()": "avanzar()"</font></div><div class=""><br class=""></div><div class="">Then, in Swift code, whether through an IDE, some metadata in a comment in the Swift file, or file extension (think “<font face="Menlo" class="">Foo.es.swift</font>”), a developer who selects Spanish could simply write <font face="Menlo" class="">avanzar()</font> and understand it in her native language. In fact, if the IDE is the layer that handles language selection, two developers who don’t even speak the same language could collaborate on code, and names from the framework would appear to each in their native language!</div><div class=""><br class=""></div><div class="">Comments and locally-defined names are of course still a barrier, but this isn’t new. I know that “mazu” means “first” in Japanese thanks to some code I worked on with an old coworker.</div><div class=""><br class=""></div><div class="">This is obviously out of scope for Swift 4, and would require significant effort to support, both technically in Swift itself and for those shipping Swift frameworks, both inside and outside of Apple, to provided localized names, so I wanted to throw this out to see if the community is even interested.</div><div class=""><br class=""></div><div class="">There’s just something about the idea of kids all over the world using Swift Playgrounds completely in their own language that makes me think this could help Swift achieve its stated goal of world dominance.</div></div></div></div></blockquote><br class=""></div><div>This has already been done for a couple of languages and it always result in the same very nasty effect: It fragment the community. Trying to search for a method name or a compiler error message in google will returns only the results in your language. </div><div><br class=""></div><div>This is incredibly frustrating, especially when your language is not English. I hate having to work with localized IDE and toolchain for that reason. Extending the localization to the language itself will just make the problem worse.</div><div><br class=""></div><div><br class=""></div></body></html>