You should have a look at how the Portuguese translation is set up:
https://github.com/andrioni/julia-doc-pt_br

(seems like it started from a copy of the julia/doc subdirectory)


On Wed, Mar 5, 2014 at 9:40 AM, Ismael VC <ismael.vc1...@gmail.com> wrote:

> Hello everyone!
>
> I'm just at some steps from actually starting the julia documentation
> translation into spanish, I have been studying the tools I'm going to need
> and use (sphinx, lokalize, pology, dictionaries, spell-checkers,
> glossaries, git, github, etc.) and I would like to have some advice into
> how to proceed.
>
> I had been adviced before that instead of making pull requests to the
> juila repo, I should had a separate repo (julia-es) for this purpose, and
> then it could be linked to the julia repo as juliadoc is.
>
> The current rapo layout I'm experimenting with looks like this:
>
> Devel (regular dir)
> |
> |---- julia (my own fork of julia that I cloned and which I keep up to
> date)
> |
> |-----julia-es (where I'm meant for the translations to reside a clone of:
> of https://github.com/Ismael-VC/julia-es )
>
> This is the current setup I have for sphinx: https://gist.github.com/
> Ismael-VC/9349109
>
> Notice I can't use: /home/ismaelvc/Devel/julia/doc/ as the root path:
>
> Enter the root path for documentation.
> > Root path for the documentation [.]: /home/ismaelvc/Devel/julia/doc/
>  Error: an existing conf.py has been found in the selected root path.
> sphinx-quickstart will not overwrite existing Sphinx projects.
>  > Please enter a new root path (or just Enter to exit): .
>
>
> I have accepted all options, because I cannot forsee what I'm going to end
> up needing in the long run.
>
> Also I want to use julia's files as templates into my own repo, like the
> conf.py inside julia/doc, etc. and just change what I need , but also I
> want to follow any modification done in the originals, how could I do this?
> currently I can only think on diffing them manually.
>
> I'd love to see not only the manual, but all of julia's documentation
> translated into spanish, including the stirngs from "help()", warnings,
> errors, info, etc. So I'm commiting in long term and I would like to take
> into account all of this before proceeding any further into the actual
> translations of the strings.
>
> ismaelvc@toybox ~/D/julia-es (setup)> ln -s ~/Devel/julia/doc/manual/*
> ~/Devel/julia-es/source/
>
>
>
>
> ismaelvc@toybox ~/D/julia-es (setup)> sphinx-build -b gettext source/
> manual-es/
> Running Sphinx v1.2.1
> loading pickled environment... done
> building [gettext]: targets for 0 template files
> building [gettext]: targets for 30 source files that are out of date
> updating environment: 0 added, 0 changed, 0 removed
> looking for now-outdated files... none found
> preparing documents... done
> writing output... [100%] variables-and-scoping
> /home/ismaelvc/Devel/julia-es/source/arrays.rst:618: WARNING: undefined
> label: stdlib-sparse (if the link has no caption the label must precede a
> section header)
> /home/ismaelvc/Devel/julia-es/source/linear-algebra.rst:12: WARNING:
> undefined label: stdlib-linalg (if the link has no caption the label must
> precede a section header)
> /home/ismaelvc/Devel/julia-es/source/packages.rst:13: WARNING: undefined
> label: available-packages (if the link has no caption the label must
> precede a section header)
> /home/ismaelvc/Devel/julia-es/source/performance-tips.rst:457: WARNING:
> undefined label: stdlib-profiling (if the link has no caption the label
> must precede a section header)
> writing message catalogs... [100%] metaprogramming
> build succeeded, 4 warnings.
> ismaelvc@toybox ~/D/julia-es (setup)>
>
> But my current layout doesn't take into account, anything more than the
> manual, I'm having troubles thinking how to order all the files I need, so
> I don't have to cahnge the layout in the future, and I can just start
> focusing in the actual translation.
>
> This is the current repo layout, in my setup branch: https://github.com/
> Ismael-VC/julia-es/tree/setup
>
> Am I ready to start, what do you think? I don't think so! :)
>
> http://postimg.org/image/p1mqgjl83/
>
> Thanks in advance!
>
>
> Ismael Venegas Castelló
>

Reply via email to