<div dir="ltr"><div>Yeah I’m starting to have conflicting ideas about this. On the one hand the reader still needs to learn a decent amount of English to have a better idea of what the standard library’s structs/classes/functions do, so might as well keep all the code in English. On the other hand, they don’t have to translate as much code while reading the book.</div><div><br></div><div>The one thing I am translating for sure is the content of all string values.</div><div><br></div>Rogelio Gudino</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 17, 2015 at 3:54 PM, Vinicius Vendramini <span dir="ltr"><<a href="mailto:vinivendra@gmail.com" target="_blank">vinivendra@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>This sounds like a good idea, especially for the second benefit. I’m just gonna keep translating text for now, but I'll have to think of a solution for that later.</div><div><br></div><div>Something else: I’ve been translating most parts of the code, such as variable and function names. The resulting code is a bit weird (I can’t translate keywords and types, for instance) but I think it makes it easier for non-english speakers to grasp the code’s goals and therefore understand how it works. Also, it helps that we finally have a language in which I can actually write translated names with decent accents, not some dumbed down version, thanks to UTF-8 support. Have you thought about this?</div><div><div class="h5"><div><br></div><br><div><blockquote type="cite"><div>On Dec 17, 2015, at 2:30 AM, Rogelio Gudino <<a href="mailto:cananito@gmail.com" target="_blank">cananito@gmail.com</a>> wrote:</div><br><div><div dir="ltr">Don’t mind at all! However, I did decide to go with a different strategy.<div><br></div><div>What I’ll try to do now is extract the content (mostly HTML) out of the English ePub, do translation work directly on it, and finally re-package the content into an ePub (generate-epub.sh).</div><div><br></div><div>The benefits of this approach:</div><div><br></div><div>1. Keeping the styling and formatting of the original ePub.</div><div>2. Pinpoint the exact changes of the English ePub every time it gets updated.</div><div><div><div><div><div><div><br></div><div>Thanks,</div><div>Rogelio Gudino</div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 16, 2015 at 2:34 PM, Vinicius Vendramini <span dir="ltr"><<a href="mailto:vinivendra@gmail.com" target="_blank">vinivendra@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Sounds like a great approach. In any case, I guess the important part is actually writing the translation - the resulting format is only relevant once there is actual text to use with it.<div><br></div><div>I’m creating a repo for a Portuguese (Brazil) translation: <a href="https://github.com/vinivendra/the-swift-programming-language-portuguese-br" target="_blank">https://github.com/vinivendra/the-swift-programming-language-portuguese-br</a></div><div>I’ll probably copy some of the structure you already created, for practicality as well as standardization. Hope you don’t mind :)</div><div><br></div><div>Cheers!</div><div><div><div><br><div><blockquote type="cite"><div>On Dec 16, 2015, at 4:23 PM, Rogelio Gudino <<a href="mailto:cananito@gmail.com" target="_blank">cananito@gmail.com</a>> wrote:</div><br><div><div dir="ltr">I just started to look into this myself since I’m interested in doing the Spanish translation. The first approach I’ll be trying is doing everything in Markdown and compile it to ePub using Pandoc.<div><br></div><div>Based on this article <a href="http://nshipster.com/colophon/" target="_blank">http://nshipster.com/colophon/</a> , Pandoc may be a bit painful to use, but I’m only interested in translating if it can be done collaboratively through GitHub, so I’ll still give it a shot.</div><div><br></div><div>Here’s the repo I made for Spanish (Mexico) <a href="https://github.com/Cananito/the-swift-programming-language-spanish-mx" target="_blank">https://github.com/Cananito/the-swift-programming-language-spanish-mx</a><br><div><br></div><div>Thanks,</div><div>Rogelio Gudino</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 16, 2015 at 11:31 AM, Vinicius Vendramini via swift-dev <span dir="ltr"><<a href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">I just saw a tweet from Chris Lattner talking about translating the Swift Programming Language ebook. This is a project I’d be very interested in; however, I don’t really know where to start.<div><br></div><div>Is there some kind of git repository, containing the original book, that I can clone? If not, does someone have any ideas on how to start a new book, imitating the original’s style? (Maybe using iBooks Author? I have no idea.)</div><div><br></div><div>I thought this thread could end up being kind of a central starting point for any other translations that come up, so I’m searching for the best solutions here :)</div><div><br></div><div>PS: <a href="http://swift.org/" target="_blank">Swift.org</a> recommends looking at an existing Chinese translation project (<a href="https://github.com/numbbbbb/the-swift-programming-language-in-chinese" target="_blank">The Swift Programming Language (Chinese translation, GitHub project)</a>), but since I have absolutely no knowledge of Chinese it’s really hard to navigate and understand that repository.</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=GKFo6G8P4XmMRbBa7icuYS-2B4DUKBH7m2ySt2rzCkjKHq7uK-2BtonewvIv8rfM2OkmDwJRYi4XGQNo-2FGJhRyytZK881cYydEsHivGMPOOaEBxTKNG3t1lj4QmElTZ5-2BKun8umGJiaD-2Fo-2BBJTUN2TgqAoapep2mfUlBhmhyUwH3-2F8fdGMt6VpFBE6mNUBql-2F-2BfgqRnlLcAFguLTHkTuX0GbZgxmXZ2L2wwbN51tEeVTCbc-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important">
</div>
<br>_______________________________________________<br>
swift-dev mailing list<br>
<a href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-dev</a><br>
<br></blockquote></div><br></div>
</div></blockquote></div><br></div></div></div></div></blockquote></div><br></div>
</div></blockquote></div><br></div></div></div></blockquote></div><br></div>