[haiku-doc] Re: Another try at user guide translations
- From: Vincent Duvert <vincent.duvert@xxxxxxx>
- To: haiku-doc@xxxxxxxxxxxxx
- Date: Wed, 23 Sep 2009 18:25:52 +0200
OK, I'm back on the translate tool :)
Sorry for the long delay, I was focused on other projects... But well,
although there are still some things to check, I think that we could
start translating very soon.
I have some proposals/critics about the current page layout (you can
see the result in the attached zip), and would like to get a consensus
before we make further steps because editing the HTML code of all the
pages will be more difficult after importing them ;-)
- I made some changes to the current layout in order to allow the max/
min-width trick without using a background image.
I also tried to put the "USER GUIDE" text from the logo to the page
itself, to avoid having a different image for each language. It works
quite well, although the the text is not displayed identically in all
browsers. Let me know what you think of this.
- The main document title is in a <div class="title">, and the
sections titles are <h1>. What about changing this to <h1> and <h2>
respectively ? (and <h2> to <h3>, and so on).
- The " " entities found in the headers/footers could be replaced
with real non-breakable spaces. This would be nicer IMHO.
- I decided to change my export code so it won't require the <!--
NAVIGATION(...) --> comment anymore, but will work directly on the
HTML code. So for instance, it will replace something this:
<div class="nav">
<div><span>
« <a href="filetypes.html">Filetypes</a>
:: <a href="contents.html" class="uplink">Contents</a>
:: <a href="index.html">Index</a> »
</span></div>
</div>
with this:
[HTML code for the language selection menu]
<div class="nav">
<div><span>
« <a href="filetypes.html">Types de fichiers</a>
:: <a href="contents.html" class="uplink">Contenu</a>
:: <a href="index.html">Indexation</a> »
</span></div>
</div>
And finally: how will we make the switch to release mode ? I guess we
could stay on translate.haikuzone.net (and maybe change its name to documentation.haikuzone.net
since it will also be used to edit the documentation). In any case,
it would be nice to have some sort of automated DB backup, in case
something goes wrong ;-)
About the export process: Do we need something other than generating
the documentation files and sending them to an SVN repository ? The
translate tool could probably also create an optional package.
Vincent
Other related posts:
