- core issue: what tooling and workflow could work, both to translation maintainer and cocos committers, not only as an one shoot translation but for maintenance.
- the programing guide, generated from .rst in the repo, should be easier to tackle - the api reference is tougher: sphinx scans the .py docstrings and produces .rst in a first pass, to docgen/api, and then the second pass renders to final format (html). Needs alternative source for the docstrings, and hooking in the sphinx build system to orchestrate the data flow in each language. - .py in master must not be bloated with translations - the english build must be a stock sphinx build (if other lang needs extra or custom extensions, and changes in sphinx broke that, I don't want docs to be showstopper for release) - I have no experience with sphinx and translations, I would ping people from the pyar list (I think I have seen your mail there ?). Specifically Hugo Ruscitti, I think at some time he talked about supporting docstring translation for some project (Pilas ?), Humitos maybe, he is involved in translation projects. Others in that list had done docs translation, so maybe asking also in the list will suggest tooling and workflows. - A look at the link provided by Daniel may be productive In a pinch, I think you should do a preliminary work like - by asking people, have an idea of how hard api docs translations can be - decide the translation scope: only programming guide or the full thing ? - propose a sketch of the tooling and workflow for discussion On Sat, Oct 21, 2017 at 8:39 AM, Alan Etkin <[email protected]> wrote: > I would like contribute to a spanish version of the current online docs > for cocos2d. Any thoughts, pointers or suggestions welcome. I could use > some reference to documentation on the docstring syntax and in particular, > directions on how to deal with the translation of links and some technical > language. > > Alan > > -- > You received this message because you are subscribed to the Google Groups > "cocos2d discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/cocos-discuss. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/cocos-discuss. For more options, visit https://groups.google.com/d/optout.
