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.

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?


> On Dec 17, 2015, at 2:30 AM, Rogelio Gudino <[email protected]> wrote:
> 
> Don’t mind at all! However, I did decide to go with a different strategy.
> 
> 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).
> 
> The benefits of this approach:
> 
> 1. Keeping the styling and formatting of the original ePub.
> 2. Pinpoint the exact changes of the English ePub every time it gets updated.
> 
> Thanks,
> Rogelio Gudino
> 
> On Wed, Dec 16, 2015 at 2:34 PM, Vinicius Vendramini <[email protected] 
> <mailto:[email protected]>> wrote:
> 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.
> 
> I’m creating a repo for a Portuguese (Brazil) translation: 
> https://github.com/vinivendra/the-swift-programming-language-portuguese-br 
> <https://github.com/vinivendra/the-swift-programming-language-portuguese-br>
> I’ll probably copy some of the structure you already created, for 
> practicality as well as standardization. Hope you don’t mind :)
> 
> Cheers!
> 
>> On Dec 16, 2015, at 4:23 PM, Rogelio Gudino <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> 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.
>> 
>> Based on this article http://nshipster.com/colophon/ 
>> <http://nshipster.com/colophon/> , 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.
>> 
>> Here’s the repo I made for Spanish (Mexico) 
>> https://github.com/Cananito/the-swift-programming-language-spanish-mx 
>> <https://github.com/Cananito/the-swift-programming-language-spanish-mx>
>> 
>> Thanks,
>> Rogelio Gudino
>> 
>> On Wed, Dec 16, 2015 at 11:31 AM, Vinicius Vendramini via swift-dev 
>> <[email protected] <mailto:[email protected]>> wrote:
>> 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.
>> 
>> 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.)
>> 
>> 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 :)
>> 
>> PS: Swift.org <http://swift.org/> recommends looking at an existing Chinese 
>> translation project (The Swift Programming Language (Chinese translation, 
>> GitHub project) 
>> <https://github.com/numbbbbb/the-swift-programming-language-in-chinese>), 
>> but since I have absolutely no knowledge of Chinese it’s really hard to 
>> navigate and understand that repository.
>> 
>> 
>> _______________________________________________
>> swift-dev mailing list
>> [email protected] <mailto:[email protected]>
>> https://lists.swift.org/mailman/listinfo/swift-dev 
>> <https://lists.swift.org/mailman/listinfo/swift-dev>
>> 
>> 
> 
> 

_______________________________________________
swift-dev mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-dev

Reply via email to