[py-dev] pytest documents with Japanese translation

[holger krekel]

Hi Tetsuya, Ronny,

i created a preliminary http://pytest.org/latest-ja, it is online now!

i tried to fix regendocs - i pushed a commit which 
should handle encoding more correctly.  But there is a new problem.
I think you translated the directive "# content of PATH" which regendoc
uses to create files - so regendoc gets problems there. Not sure
what's the best way to fix it.

I also changed the way docs are versioned: en/conf.py and ja/conf.py
now contain a more fine grained version which can diverge according
to translation/documentation status.  Currently the en/conf.py
has two more examples (i added them the last two days) and the
version 2.2.4.1 whereas the ja/conf.py has 2.2.4.0 which still
strictly relates to the docs at 2.2.4 release time.

Tetsuya, if you want to be able to commit/push to doc/ja/*
i can happily add you.  I'd also like to eventually allow
you to push the japanese docs yourself or have some automated
way. We should also think about creating a Japenese PDF
(see the latestpdf target in the makefile).

best,
holger

On Thu, Jun 07, 2012 at 21:03 +0900, Tetsuya Morimoto wrote:
> Hi Holger, Ronny
> 
> > is there some suggested readng for the workflow changes?
> > (i really didn't investigate further than it exists and uses .po)
> I haven't known Sphinx i18n feature well, either. Sorry, I'm not sure
> we need the workflow changes. Let me look into more detail.
> 
> By the way, I'm happy that the Japanese translation for 2.2.4 will put
> on pytest.org if it isn't much hand work.
> 
> thanks,
> Tetsuya
> 
> On Thu, Jun 7, 2012 at 4:21 PM, Ronny Pfannschmidt
> <Ronny.Pfannschmidt at gmx.de> wrote:
> > 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<holger at 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
> >>>>
> >>>>
> >
>