Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Translation initiative coordiantion? #1

Open
kberov opened this Issue · 2 comments

3 participants

@kberov

Hi Italian team.
I just noticed that you are translating the book. You created a folder translations in which you put the files.
How will you generate the book in different formats later?

I started translating it in Bulgarian some months ago.
I took another approach. I created a folder sections_bg right beside sections and started putting files there, then translating them.
I also modified (hacked) the build_chapters.pl and build_html.pl scripts to accept a language parameter.
How do you think? Could we cooperate to unify the way the book is generated in different languages?
See the bottom of my README: https://github.com/kberov/modern_perl_book/blob/master/README

I also see that the book is being translated in Chinese, but there they translate the same files.

I think in order to support further editions and translations we should coordinate some how...

@dada
Collaborator

hello!

at the moment, we are basically doing a "cp translations/italian/* sections" in order to build the output files. suboptimal, I know :-)

some coordination would indeed be very nice, as far as I know we don't have any strong preference. something like your "hack" seems to be a good working solution. I will discuss the matter with the others involved in the Italian translation project and we'll let you know.

thanks for sharing!

cheers,
Aldo

@chromatic

The way I wrote Pod::PseudoPod::Book, each repository can have its own configuration file. One of the configuration options is the location of the individual *.pod sections. Obviously this makes maintaining parallel sections easy.

The drawback is that I haven't finished testing or documenting Pod::PseudoPod::Book (or Pod::PseudoPod::DOM), nor have I released them to the CPAN. The good news is that I've used them on three books so far (including Modern Perl 2012), and they work wonderfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.