> > I would suggest to make a first build before editing anything and save the > log and console output as reference; translations should not increase the > count of warnings. > > 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. > > This should produce an usable translation without any technical > complication. > > I have already forked cocos2d, made a doc_es branch and cloned a local copy. Can I make test builds at the cloned folder or should I use a copy somewhere else? Not sure if the project ignores the builds.
-- 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.
