Hi Holger, Tetsuya is there some suggested readng for the workflow changes? (i really didn't investigate further than it exists and uses .po)
we might also want to investgate something like transifex for making it easy for translators to translate the docs -- Ronny On 06/07/2012 02:09 AM, Tetsuya Morimoto wrote: > Hi Holger, Ronny > > In my opinion, I agree with Ronny's idea (use Sphinx i18n feature), > because of its maintainability. > > However, we need to change some operations for documentation workflow > if we started to use Sphinx i18n feature. I don't know you want it or > not, in this time. > > Though I haven't used Sphinx i18n feature, I'm willing to investigate > the functionality and make the documentation workflow if you want. > > thanks, > Tetsuya > > On Wed, Jun 6, 2012 at 9:35 PM, holger krekel<hol...@merlinux.eu> wrote: >> Hello Ronny, >> >> On Wed, Jun 06, 2012 at 13:59 +0200, Ronny Pfannschmidt wrote: >>> Hi Holger, Tetsuya >>> >>> while taking a look i noticed that sphinx has a integrated >>> translation system based on .po files >>> >>> see http://sphinx.pocoo.org/latest/intl.html >>> >>> im under the impression that this way is more maintainable than he >>> current way due to using standard tools to manage translated strings >>> >>> i'd like to suggest some investigation in its usefullness >> >> I am happy to consider using it - not sure i get to try it myself >> any time soon and wonder specifically if a two-language situation with >> not so often changing docs warrants using the above system. >> >> Tetsuya, what do you think? Can you imagine investigating a bit? >> >> best, >> holger >> >>> -- ronny >>> >>> _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
