Nicholas,
Sounds like you are making steady progress. Well done.
Re getting duplicate images, we had a similar problem with the sphinx
build process, and created a work around by creating symbolic links post
build. Hopefully there is a smarter option with transifex.
The large size of the HTML might be indicative of verbose HTML being
created. I wonder whether transifex has a "compress" option, or
alternatively we could run a compress option over created html afterwards.
Warm regards, Cameron
On 14/1/17 7:59 am, Baka Niko wrote:
Hi everyone,
Jakob send me the link to a recording about
internationalization (i18n), it is 24 min lenght and might interest
people who want to get involved in the translation process. So thanks
Jakob !
https://www.youtube.com/watch?v=Nz8zutA55fI
<https://www.youtube.com/watch?v=Nz8zutA55fI>
During the second viewing, i downloaded the osgeolie docs from github
to get a fresh start.
In the Docs, i added or changed some lines:
import sys, os
# needed to avoid an ascii error during the build of the translations
reload(sys)
sys.setdefaultencoding('utf-8')
...
# General information about the project.
project = u'OSGeo-Live'
copyright = u'OSGeo-Live Contributors'
...
# The short X.Y version.
version = '10.5'
# The full version, including alpha/beta/rc tags.
release = '10.5 alpha'
...
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
language = 'en'
# where do the translation go (should be changed ? or the html index
changed ?)
locale_dirs = ['locale/']
# gettext compact mode (one folder by language)
gettext_compact = True
Then I used the following commands:
tx init # folder initialisation (transifex client is needed)
sphinx-intl update-txconfig-resources --pot-dir _build/locale
--transifex-project-name osgeolive
# configure the project ?
tx pull -l fr # french translation pulling
sphinx-intl build # translation building
make SPHINXOPTS="-Dlanguage=fr" html # html pages building
The last command lauched the building of ALL the languages which have
a folder in the main folder.
The _build folder now contains all the html files from the docs and is
more than 1 GB.
Even the images folder get fatter, passing from 854 files (103 MB) to
1602 (197 MB) when becoming _images and some images gets a copy (but
not all).
I tried to deleted language folders, but the only ones that where
built are the 'en' and 'id' that i left. I expected at least that the
french one will be downloaded since i requested it.
So there is some progress but not enough yet. Any help or suggestion
is welcomed.
Sorry for the long mail,
Best wishes,
Nicolas
2017-01-08 20:18 GMT+01:00 Angelos Tzotsos <[email protected]
<mailto:[email protected]>>:
Hi Jakob,
Thank you for the update, good work!
It would be great to be able to push current translations
automatically, but I am afraid not all of them were up to date, so
it might not be straightforward.
Regarding the Mac and Window installer folders, those used to be
placeholders to actually link to folders with installers during
our iso build process. The installers have been removed since our
10.0 release, so those folders are not needed anymore.
Best,
Angelos
On 01/08/2017 03:11 PM, Jakob Miksch wrote:
Dear list,
a short update regarding the move to Transifex.
I managed push all English source files to Transifex. I solved the
problem (that I mentioned in the last chat) by "hard-coding" the
version number in the conf.py file. Before it was read
automatically.
This apparently caused some problems.
https://github.com/OSGeo/OSGeoLiv
<https://github.com/OSGeo/OSGeoLiv>
e-doc/blob/master/conf.py#L26
The next step is to push all existing translations to
Transifex. Would
be cool to do that automatically as well ...
This is our Transifex repository:
https://www.transifex.com/osgeo/osgeo
<https://www.transifex.com/osgeo/osgeo>
live/dashboard/
And here we can discuss about this topic:
https://wiki.osgeo.org/wiki/T
alk:Live_GIS_Translate
Now, I am thinking about our folder structure. The folder
structure
from this project "QField" looks quite clean and nice:
https://github.c
om/opengisch/QField-docs
I do not understand the purpose of these two folders in our
repository:
"MacInstallers"
(https://github.com/OSGeo/OSGeoLive-doc/tree/master/Mac
<https://github.com/OSGeo/OSGeoLive-doc/tree/master/Mac>
Installers) and "WindowsInstallers"
(https://github.com/OSGeo/OSGeoLive
<https://github.com/OSGeo/OSGeoLive>
-doc/tree/master/WindowsInstallers)
They only link to the documentation within the language folders.
Why do we need these two folders?
Best wishes,
Jakob
_______________________________________________
Live-demo mailing list
[email protected] <mailto:[email protected]>
http://lists.osgeo.org/mailman/listinfo/live-demo
<http://lists.osgeo.org/mailman/listinfo/live-demo>
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
<http://wiki.osgeo.org/wiki/Live_GIS_Disc>
--
Angelos Tzotsos, PhD
OSGeo Charter Member
http://users.ntua.gr/tzotsos
_______________________________________________
Live-demo mailing list
[email protected] <mailto:[email protected]>
http://lists.osgeo.org/mailman/listinfo/live-demo
<http://lists.osgeo.org/mailman/listinfo/live-demo>
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
<http://wiki.osgeo.org/wiki/Live_GIS_Disc>
_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
--
Cameron Shorter
M +61 419 142 254
_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
