> > > Then I'd suggest to start with reduced scope and low tech. > How about > - you fork los-cocos/cocos in gitbub > - create a branch doc_es , translate in that branch the files in > docgen/programming_guide (meaning you edit the existing files, not copies; > that will allow to build the docs without changing any code) > - In that branch don't edit anything outside docgen/programming_guide > > Yes, that was more or less what I was thinking on. I think I was confusing when I talked mistakenly about "docstring syntax" in my first message. I meant I needed help with the tools used for creating the cocos2d docs.
> > Then you translate small sections and rebuild, if they are new warnings or > errors fix that before continuing to translate. Also look if the relevant > html page looks good. > How much text per rebuild? Is it ok to translate a whole file before rebuilding? -- 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.
