<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=""><div class="">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 class=""><br class=""></div><div class="">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 class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 17, 2015, at 2:30 AM, Rogelio Gudino <<a href="mailto:cananito@gmail.com" class="">cananito@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Don’t mind at all! However, I did decide to go with a different strategy.<div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">The benefits of this approach:</div><div class=""><br class=""></div><div class="">1. Keeping the styling and formatting of the original ePub.</div><div class="">2. Pinpoint the exact changes of the English ePub every time it gets updated.</div><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Rogelio Gudino</div></div></div></div></div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Dec 16, 2015 at 2:34 PM, Vinicius Vendramini <span dir="ltr" class=""><<a href="mailto:vinivendra@gmail.com" target="_blank" class="">vinivendra@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">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 class=""><br class=""></div><div class="">I’m creating a repo for a Portuguese (Brazil) translation: <a href="https://github.com/vinivendra/the-swift-programming-language-portuguese-br" target="_blank" class="">https://github.com/vinivendra/the-swift-programming-language-portuguese-br</a></div><div class="">I’ll probably copy some of the structure you already created, for practicality as well as standardization. Hope you don’t mind :)</div><div class=""><br class=""></div><div class="">Cheers!</div><div class=""><div class="h5"><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 16, 2015, at 4:23 PM, Rogelio Gudino <<a href="mailto:cananito@gmail.com" target="_blank" class="">cananito@gmail.com</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">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 class=""><br class=""></div><div class="">Based on this article <a href="http://nshipster.com/colophon/" target="_blank" class="">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 class=""><br class=""></div><div class="">Here’s the repo I made for Spanish (Mexico) <a href="https://github.com/Cananito/the-swift-programming-language-spanish-mx" target="_blank" class="">https://github.com/Cananito/the-swift-programming-language-spanish-mx</a><br class=""><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Rogelio Gudino</div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Dec 16, 2015 at 11:31 AM, Vinicius Vendramini via swift-dev <span dir="ltr" class=""><<a href="mailto:swift-dev@swift.org" target="_blank" class="">swift-dev@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">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 class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">PS: <a href="http://swift.org/" target="_blank" class="">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" class="">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" class="">
</div>
<br class="">_______________________________________________<br class="">
swift-dev mailing list<br class="">
<a href="mailto:swift-dev@swift.org" target="_blank" class="">swift-dev@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-dev" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></div></div></div></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></body></html>