<div dir="ltr">I wonder what it would do for reusability. It would be hard to share code between countries written in Spanish or japanense unless the compiler could convert the code to your language. Maybe properties and function calls could be converted over to different languages but I am not sure Swift keywords could be as easily converted which could lead to code with mixed languages due to languages not mapping 1 to 1 on every word. This would be really cool but a LOT of work. I think this is a bigger issue than just adding it into Swift. Taking a look at non-English-based programming languages - <a href="https://en.wikipedia.org/wiki/Non-English-based_programming_languages">https://en.wikipedia.org/wiki/Non-English-based_programming_languages</a> - there are very few, if any, highly used languages on the list. Some languages implemented symbols instead of words so that it is not language based but that would cause breaking changes in Swift :)<div><div><br></div><div>It would be cool to see code in different languages:</div><div><br></div><div>for i in foo {</div><div> print(i)</div><div>}<br><div class="gmail_extra"><br></div><div class="gmail_extra">para i en foo {</div><div class="gmail_extra"> escribir(i)</div><div class="gmail_extra">}</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 24, 2017 at 11:28 AM, Jeff Kelley via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div style="word-wrap:break-word"><div>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><br></div><div><img src="cid:4E5A7475-A760-469E-A915-125574AAC56B"></div><div><br></div><div>All of the UI is fully localized for Chinese, <i>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>de facto </i>language for developers. But does that have to be the case?</div><div><br></div><div>Imagine a world where alongside our Swift frameworks, we ship <font face="Menlo">.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">moveForward()</font>”.</div><div><br></div><div><img src="cid:9D276CBF-C25F-4942-A868-F0775B651711"></div><div><br></div><div>A scenario where Swift supported localized frameworks might see a <font face="Menlo">.strings</font> file with a format like this:</div><div><br></div><div><font face="Menlo">"moveForward()": "avanzar()"</font></div><div><br></div><div>Then, in Swift code, whether through an IDE, some metadata in a comment in the Swift file, or file extension (think “<font face="Menlo">Foo.es.swift</font>”), a developer who selects Spanish could simply write <font face="Menlo">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><br></div><div>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><br></div><div>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><br></div><div>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><br></div><br><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);font-family:helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);font-family:helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);font-family:helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);font-family:helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><span class="gmail-m_2944716445529640384Apple-style-span" style="border-collapse:separate;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;line-height:normal"><div style="word-wrap:break-word"><div>Jeff Kelley</div><div><br></div><div><a href="mailto:SlaunchaMan@gmail.com">SlaunchaMan@gmail.com</a> | <a href="https://twitter.com/SlaunchaMan">@<wbr>SlaunchaMan</a> | <a href="http://jeffkelley.org/">jeffkelley.org</a></div></div></span></div></div></div></div></div>
</div>
<br></div></div><br>______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Joshua Alvarado<div><a href="mailto:alvaradojoshua0@gmail.com">alvaradojoshua0@gmail.com</a></div></div>
</div></div></div></div>