On 29/12/12 23:37, Guilherme Cavalcanti wrote:
Hi!
My progress with the translation is so good, but a have a question.
The SVN only contains the makrdown files, but in these markdown files there
are references to html files properly, like this
*[Alternatives](sparql_union.html)* in the *sparql.mdtext* in the SPARQL
tutorials for example.
I can do the entire translation in the markdown files, but I think that I
will need these html files, because I will put the translated text in new
files, example:
The original one (english) is: *sparql_union.mdtext *and *sparql_union.html
*I will create (portuguese)*: **sparql_union_pt.mdtext *and *
sparql_union_pt.html*
But I don't know where is this .html files, even if I will need them.
The HTML files are automatically generated - they aren't checked in to
the site SVN. Actually, if there are any .html checked into site SVN
then they just get copied over (e.g. the javadoc).
We use the Apache CMS system:
http://www.apache.org/dev/cms.html
and our use is described:
https://cwiki.apache.org/confluence/display/JENA/ProcessWebSite
In brief, when a svn commit is done to the SVN area [1], the buildbot
runs shortly afterwards and converts all the markdown into the html
files. So the markdown author knows the link to [Page](page.html) needs
to have .html on the end not .mdtext bit the conbtent comes from
page.mdtext.
This first stage builds the staging site:
http://jena.staging.apache.org/
where you can check the markdown has done what you expect.
Then if the site looks good, the site can be published, which is a perl
script a committer has to run.
There is also a rather niffty in-browser way to make small changes if
you have commit rights with a bookmarlet of:
javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))
and you can publish that way as well. But it does not work at any scale
for, say, when changing all the javadoc to a new version.
What might be useful to you is that is an offline way to produce the
site. The CMS documentation has some details
http://www.apache.org/dev/cmsref.html#walkthrough
but I thought there was an easier way to do this - hopefully Ian can
clarify this (Ian set up the site mechanisms up originally).
Andy
[1] i.e our working copy of the markdown and other content assets:
https://svn.apache.org/repos/asf/jena/site/trunk/
CMS knows to map this to jena.apache.org
