Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start russian translation #14

Open
wants to merge 28 commits into
base: master
Choose a base branch
from
Open

Start russian translation #14

wants to merge 28 commits into from

Conversation

mishin
Copy link

@mishin mishin commented Oct 3, 2014

Hi, very good pod, I decide to translate it

@book
Copy link
Owner

book commented Oct 3, 2014

Cool!

I'm interested in translations, and I have emailed the maintainer of perldoc to find out which is the right way to offer POD documentation files in non-English languages.

Depending on the answer, we might need to rename your document.

Obviously, I'll merge your changes when your translation is complete.

@mishin
Copy link
Author

mishin commented Oct 3, 2014

Thanks, for understanding!! It's greate!

@dolmen
Copy link
Contributor

dolmen commented Oct 4, 2014

There is builtin support for translation in perldoc with the -L flag. You just have to use the POD2::<language>:: namespace. MetaCPAN also supports this. See for example the Number::Phone::FR module that has both english and french documentation.

So just move the file to lib/POD2/RU/perlsecret.pod.

@mishin
Copy link
Author

mishin commented Oct 4, 2014

Dolmen, thanks, it's close to truth, I add to DOD2/RU

@dolmen
Copy link
Contributor

dolmen commented Oct 4, 2014

Dolmen, thanks, it's close to truth, I add to DOD2/RU

Close to truth? DOD2/RU? I'm not following you...

@mishin
Copy link
Author

mishin commented Oct 5, 2014

It's joke, are you offended?

@book
Copy link
Owner

book commented Oct 5, 2014

When I emailed Mark Allen (the perldoc maintainer), I had already looked at the -L option.

My worry was that this was more or less reserved for translations of the core Perl docs, and that it might cause CPAN indexing issues if we started to put pod files under POD2/<language_code>. I've also noted that the POD2:: modules seem to contain code that is meant to deal with some specific situations.

Also, it seems weird to duplicate the CPAN tree under the POD2 namespace, but that's personal taste, I guess.

I've told Mark about using the .<language_code>.pod extension, and how perldoc could probably support that. His answer was that it is "a tough question and a difficult problem", but he seems interested in finding a solution.

@mishin
Copy link
Author

mishin commented Oct 6, 2014

Thanks for investigations!

@mishin
Copy link
Author

mishin commented Oct 20, 2014

Hi, so, I'm finished to translate to Russian language.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants