You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2013/01/03 11:51:17 UTC
Re: [Contribution] Portuguese Translation of Tutorials
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
Re: [Contribution] Portuguese Translation of Tutorials
Posted by Andy Seaborne <an...@apache.org>.
On 08/02/13 10:50, Andy Seaborne wrote:
> On 06/02/13 00:10, Guilherme Jose Carvalho Cavalcanti wrote:
>> Just to say. Everything is "ok". You can publish when you can!
>>
>> Very Thanks and Very Happy to contribute!
>
>
> Will do when I have a moment ... /me feeling mildly guilty at not having
> done so already.
>
> (it'll need publishing using the script interface not the UI because the
> UI can't cope with large changes)
>
> Andy
>
Published - thanks for the nudge.
If you'd like to announce it on users@ that would be great.
Andy
Re: [Contribution] Portuguese Translation of Tutorials
Posted by Andy Seaborne <an...@apache.org>.
On 06/02/13 00:10, Guilherme Jose Carvalho Cavalcanti wrote:
> Just to say. Everything is "ok". You can publish when you can!
>
> Very Thanks and Very Happy to contribute!
Will do when I have a moment ... /me feeling mildly guilty at not having
done so already.
(it'll need publishing using the script interface not the UI because the
UI can't cope with large changes)
Andy
Re: [Contribution] Portuguese Translation of Tutorials
Posted by Guilherme Jose Carvalho Cavalcanti <gj...@cin.ufpe.br>.
Just to say. Everything is "ok". You can publish when you can!
Very Thanks and Very Happy to contribute!
2013/1/19 Guilherme Jose Carvalho Cavalcanti <gj...@cin.ufpe.br>
> I checked e fixed some mistakes. Till now, everything is OK for both
> tutorials that I submitted.
>
> I'm waiting for the other two tutorials, that a friend of mine is
> translating, after that, the translation will be 100% complete.
>
> Then, when I submit and review the others tutorials, I will say to you to
> "publish". :)
>
> Very thanks for the assistance.
>
>
> 2013/1/19 Andy Seaborne <an...@apache.org>
>
>> Guilherme,
>>
>> SPARQL tutorial content applied and on the staging site:
>>
>> http://jena.staging.apache.**org/tutorials/sparql_pt.html<http://jena.staging.apache.org/tutorials/sparql_pt.html>
>>
>> If you could make a quick check that all the content is there, I'd be
>> grateful. I have also checked the SVN logs and it looks complete to me;
>> there was only one slight area of doubt - the #3 change was not there but I
>> think I see it in the cumulative #4 updates.
>>
>> If it looks right, I'll press the "publish" button and it'll go live.
>>
>> Once again, many thanks,
>>
>> Andy
>>
>>
>> On 17/01/13 10:08, Andy Seaborne wrote:
>>
>>> On 16/01/13 02:50, Guilherme Jose Carvalho Cavalcanti wrote:
>>>
>>>> I had no lucky using the JIRA, sorry.
>>>>
>>>
>>> No problem.
>>>
>>>
>>>> But I have sucess using the CMS of apache, and commited a little
>>>> change. If
>>>> this change is ok, i'll submit all the other tutorials.
>>>>
>>>> Thanks and waiting.
>>>>
>>>
>>> OK - new technology alert - I didn't know of this facility in the CMS
>>> site! Let's give it a whizz!
>>>
>>> When I went to the URL, I got what I think is a single diff of both
>>> items so I have committed the diff to the staging site:
>>>
>>> http://jena.staging.apache.**org/tutorials/rdf_api_pt.html<http://jena.staging.apache.org/tutorials/rdf_api_pt.html>
>>>
>>> have a look and let me know if it looks right.
>>>
>>> Many thanks
>>> Andy
>>>
>>>
>>>
>>>> 2013/1/10 Andy Seaborne <an...@apache.org>
>>>>
>>>> On 10/01/13 01:30, Guilherme Jose Carvalho Cavalcanti wrote:
>>>>>
>>>>> Thanks for all the explanation!
>>>>>>
>>>>>> Now, I want to submit my translations. I'm using the *Eclipse with
>>>>>> Subversion plugin*, but in the main page, they only explain how to
>>>>>> submit
>>>>>>
>>>>>> with GIT.
>>>>>>
>>>>>> How do I proceed to submit my contribution - the new .mdtext files?
>>>>>>
>>>>>>
>>>>> Please create a JIRA and attach the new files that need to be added.
>>>>>
>>>>> Additionally, if you have any suggested changes or fixes to the
>>>>> existing
>>>>> material, then a patch against the jena-site tree would be the best
>>>>> way.
>>>>>
>>>>> Andy
>>>>>
>>>>
>>>
>>
>
>
> --
> Guilherme José C. Cavalcanti
> Graduando em Ciência da Computação
> Cin-UFPE
> gjcc@cin.ufpe.br
>
--
Guilherme José C. Cavalcanti
Graduando em Ciência da Computação
Cin-UFPE
gjcc@cin.ufpe.br
Re: [Contribution] Portuguese Translation of Tutorials
Posted by Guilherme Jose Carvalho Cavalcanti <gj...@cin.ufpe.br>.
I checked e fixed some mistakes. Till now, everything is OK for both
tutorials that I submitted.
I'm waiting for the other two tutorials, that a friend of mine is
translating, after that, the translation will be 100% complete.
Then, when I submit and review the others tutorials, I will say to you to
"publish". :)
Very thanks for the assistance.
2013/1/19 Andy Seaborne <an...@apache.org>
> Guilherme,
>
> SPARQL tutorial content applied and on the staging site:
>
> http://jena.staging.apache.**org/tutorials/sparql_pt.html<http://jena.staging.apache.org/tutorials/sparql_pt.html>
>
> If you could make a quick check that all the content is there, I'd be
> grateful. I have also checked the SVN logs and it looks complete to me;
> there was only one slight area of doubt - the #3 change was not there but I
> think I see it in the cumulative #4 updates.
>
> If it looks right, I'll press the "publish" button and it'll go live.
>
> Once again, many thanks,
>
> Andy
>
>
> On 17/01/13 10:08, Andy Seaborne wrote:
>
>> On 16/01/13 02:50, Guilherme Jose Carvalho Cavalcanti wrote:
>>
>>> I had no lucky using the JIRA, sorry.
>>>
>>
>> No problem.
>>
>>
>>> But I have sucess using the CMS of apache, and commited a little
>>> change. If
>>> this change is ok, i'll submit all the other tutorials.
>>>
>>> Thanks and waiting.
>>>
>>
>> OK - new technology alert - I didn't know of this facility in the CMS
>> site! Let's give it a whizz!
>>
>> When I went to the URL, I got what I think is a single diff of both
>> items so I have committed the diff to the staging site:
>>
>> http://jena.staging.apache.**org/tutorials/rdf_api_pt.html<http://jena.staging.apache.org/tutorials/rdf_api_pt.html>
>>
>> have a look and let me know if it looks right.
>>
>> Many thanks
>> Andy
>>
>>
>>
>>> 2013/1/10 Andy Seaborne <an...@apache.org>
>>>
>>> On 10/01/13 01:30, Guilherme Jose Carvalho Cavalcanti wrote:
>>>>
>>>> Thanks for all the explanation!
>>>>>
>>>>> Now, I want to submit my translations. I'm using the *Eclipse with
>>>>> Subversion plugin*, but in the main page, they only explain how to
>>>>> submit
>>>>>
>>>>> with GIT.
>>>>>
>>>>> How do I proceed to submit my contribution - the new .mdtext files?
>>>>>
>>>>>
>>>> Please create a JIRA and attach the new files that need to be added.
>>>>
>>>> Additionally, if you have any suggested changes or fixes to the existing
>>>> material, then a patch against the jena-site tree would be the best way.
>>>>
>>>> Andy
>>>>
>>>
>>
>
--
Guilherme José C. Cavalcanti
Graduando em Ciência da Computação
Cin-UFPE
gjcc@cin.ufpe.br
Re: [Contribution] Portuguese Translation of Tutorials
Posted by Andy Seaborne <an...@apache.org>.
Guilherme,
SPARQL tutorial content applied and on the staging site:
http://jena.staging.apache.org/tutorials/sparql_pt.html
If you could make a quick check that all the content is there, I'd be
grateful. I have also checked the SVN logs and it looks complete to me;
there was only one slight area of doubt - the #3 change was not there
but I think I see it in the cumulative #4 updates.
If it looks right, I'll press the "publish" button and it'll go live.
Once again, many thanks,
Andy
On 17/01/13 10:08, Andy Seaborne wrote:
> On 16/01/13 02:50, Guilherme Jose Carvalho Cavalcanti wrote:
>> I had no lucky using the JIRA, sorry.
>
> No problem.
>
>>
>> But I have sucess using the CMS of apache, and commited a little
>> change. If
>> this change is ok, i'll submit all the other tutorials.
>>
>> Thanks and waiting.
>
> OK - new technology alert - I didn't know of this facility in the CMS
> site! Let's give it a whizz!
>
> When I went to the URL, I got what I think is a single diff of both
> items so I have committed the diff to the staging site:
>
> http://jena.staging.apache.org/tutorials/rdf_api_pt.html
>
> have a look and let me know if it looks right.
>
> Many thanks
> Andy
>
>
>>
>> 2013/1/10 Andy Seaborne <an...@apache.org>
>>
>>> On 10/01/13 01:30, Guilherme Jose Carvalho Cavalcanti wrote:
>>>
>>>> Thanks for all the explanation!
>>>>
>>>> Now, I want to submit my translations. I'm using the *Eclipse with
>>>> Subversion plugin*, but in the main page, they only explain how to
>>>> submit
>>>>
>>>> with GIT.
>>>>
>>>> How do I proceed to submit my contribution - the new .mdtext files?
>>>>
>>>
>>> Please create a JIRA and attach the new files that need to be added.
>>>
>>> Additionally, if you have any suggested changes or fixes to the existing
>>> material, then a patch against the jena-site tree would be the best way.
>>>
>>> Andy
>
Re: [Contribution] Portuguese Translation of Tutorials
Posted by Andy Seaborne <an...@apache.org>.
On 16/01/13 02:50, Guilherme Jose Carvalho Cavalcanti wrote:
> I had no lucky using the JIRA, sorry.
No problem.
>
> But I have sucess using the CMS of apache, and commited a little change. If
> this change is ok, i'll submit all the other tutorials.
>
> Thanks and waiting.
OK - new technology alert - I didn't know of this facility in the CMS
site! Let's give it a whizz!
When I went to the URL, I got what I think is a single diff of both
items so I have committed the diff to the staging site:
http://jena.staging.apache.org/tutorials/rdf_api_pt.html
have a look and let me know if it looks right.
Many thanks
Andy
>
> 2013/1/10 Andy Seaborne <an...@apache.org>
>
>> On 10/01/13 01:30, Guilherme Jose Carvalho Cavalcanti wrote:
>>
>>> Thanks for all the explanation!
>>>
>>> Now, I want to submit my translations. I'm using the *Eclipse with
>>> Subversion plugin*, but in the main page, they only explain how to submit
>>>
>>> with GIT.
>>>
>>> How do I proceed to submit my contribution - the new .mdtext files?
>>>
>>
>> Please create a JIRA and attach the new files that need to be added.
>>
>> Additionally, if you have any suggested changes or fixes to the existing
>> material, then a patch against the jena-site tree would be the best way.
>>
>> Andy
Re: [Contribution] Portuguese Translation of Tutorials
Posted by Guilherme Jose Carvalho Cavalcanti <gj...@cin.ufpe.br>.
I had no lucky using the JIRA, sorry.
But I have sucess using the CMS of apache, and commited a little change. If
this change is ok, i'll submit all the other tutorials.
Thanks and waiting.
2013/1/10 Andy Seaborne <an...@apache.org>
> On 10/01/13 01:30, Guilherme Jose Carvalho Cavalcanti wrote:
>
>> Thanks for all the explanation!
>>
>> Now, I want to submit my translations. I'm using the *Eclipse with
>> Subversion plugin*, but in the main page, they only explain how to submit
>>
>> with GIT.
>>
>> How do I proceed to submit my contribution - the new .mdtext files?
>>
>
> Please create a JIRA and attach the new files that need to be added.
>
> Additionally, if you have any suggested changes or fixes to the existing
> material, then a patch against the jena-site tree would be the best way.
>
> Andy
>
>
>
>> 2013/1/3 Andy Seaborne <an...@apache.org>
>>
>> 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<http://www.apache.org/dev/cms.**html><
>>> http://www.apache.org/dev/**cms.html<http://www.apache.org/dev/cms.html>
>>> >
>>>
>>>
>>> and our use is described:
>>> https://cwiki.apache.org/****confluence/display/JENA/****ProcessWebSite<https://cwiki.apache.org/**confluence/display/JENA/**ProcessWebSite>
>>> <https://cwiki.**apache.org/confluence/display/**JENA/ProcessWebSite<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/ <http://jena.staging.apache.**org/<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)<https://cms.**
>>> apache.org/redirect?uri='+**escape(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<http://www.apache.org/dev/**cmsref.html#walkthrough>
>>> <http:/**/www.apache.org/dev/cmsref.**html#walkthrough<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/<https://svn.apache.org/repos/**asf/jena/site/trunk/>
>>> <https://**svn.apache.org/repos/asf/jena/**site/trunk/<https://svn.apache.org/repos/asf/jena/site/trunk/>
>>> >
>>>
>>>
>>> CMS knows to map this to jena.apache.org
>>>
>>>
>>>
>>
>>
>
--
Guilherme José C. Cavalcanti
Graduando em Ciência da Computação
Cin-UFPE
gjcc@cin.ufpe.br
Re: [Contribution] Portuguese Translation of Tutorials
Posted by Andy Seaborne <an...@apache.org>.
On 10/01/13 01:30, Guilherme Jose Carvalho Cavalcanti wrote:
> Thanks for all the explanation!
>
> Now, I want to submit my translations. I'm using the *Eclipse with
> Subversion plugin*, but in the main page, they only explain how to submit
> with GIT.
>
> How do I proceed to submit my contribution - the new .mdtext files?
Please create a JIRA and attach the new files that need to be added.
Additionally, if you have any suggested changes or fixes to the existing
material, then a patch against the jena-site tree would be the best way.
Andy
>
> 2013/1/3 Andy Seaborne <an...@apache.org>
>
>> 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 <http://www.apache.org/dev/cms.html>
>>
>> and our use is described:
>> https://cwiki.apache.org/**confluence/display/JENA/**ProcessWebSite<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/ <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)<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<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/<https://svn.apache.org/repos/asf/jena/site/trunk/>
>>
>> CMS knows to map this to jena.apache.org
>>
>>
>
>
Re: [Contribution] Portuguese Translation of Tutorials
Posted by Guilherme Jose Carvalho Cavalcanti <gj...@cin.ufpe.br>.
Thanks for all the explanation!
Now, I want to submit my translations. I'm using the *Eclipse with
Subversion plugin*, but in the main page, they only explain how to submit
with GIT.
How do I proceed to submit my contribution - the new .mdtext files?
2013/1/3 Andy Seaborne <an...@apache.org>
> 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 <http://www.apache.org/dev/cms.html>
>
> and our use is described:
> https://cwiki.apache.org/**confluence/display/JENA/**ProcessWebSite<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/ <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)<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<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/<https://svn.apache.org/repos/asf/jena/site/trunk/>
>
> CMS knows to map this to jena.apache.org
>
>
--
Guilherme José C. Cavalcanti
Graduando em Ciência da Computação
Cin-UFPE
gjcc@cin.ufpe.br