You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by FR web forum <oo...@free.fr> on 2012/04/04 22:58:00 UTC
[WWW] Tutorial to put online
Bonjour,
Actually, I refresh our french website pages.
I would like to add some new tutorials for our users.
But I don't know how can I upload it.
Should I use an FTP or another way?
Thank you for help
Re: [WWW] Translating branding and navigation
Posted by Dave Fisher <da...@comcast.net>.
Hi Zoltan,
HU is now enabled for translated branding and topnav.
Regards,
Dave
On Apr 12, 2012, at 11:21 AM, Reizinger Zoltán wrote:
> Hi,
> Please make hu next.
> Thanks,
> Zoltan
>
> 2012.04.11 17:47 időpontban Dave Fisher ezt írta:
>> Hi -
>>
>> es, de, nl, fi, pt-br, ru, and ja are now setup for committers to
>> make translations to brand.mdtext and topnav.mdtext.
>>
>> I still have the question about Chinese / zh split regarding
>> traditional / simplified (Taiwan / Mainland)
>>
>> Next languages? cs, hu? Please respond for the next NL set.
>>
>> brand.mdtext
>> ===========
>> home: home
>> search: search
>> name: Apache OpenOffice (incubating)
>> tagline: (incubating) | The Free and Open Productivity Suite
>> logo: AOO_logos/OOo_Website_v2_copy.png
>> domain: www.openoffice.org
>> divid: bannera
>>
>> topnav.mdtext
>> ============
>> divid: topnava
>>
>> - [Product][m0]
>> - [Download][m1]
>> - [Support][m2]
>> - [Extend][m3]
>> - [Develop][m4]
>> - [Focus Areas][m5]
>> - [Native Language][m6]
>>
>>
>> [m0]: /product/index.html
>> "Apache OpenOffice product description"
>> [m1]: /download/index.html
>> "Download OpenOffice.org"
>> [m2]: /support/index.html
>> "Find Support for OpenOffice.org"
>> [m3]: /extensions/index.html
>> "Extensions and Templates for OpenOffice"
>> [m4]: http://incubator.apache.org/openofficeorg/get-involved.html
>> "Get involved in Apache OpenOffice (incubating)"
>> [m5]: /projects/accepted.html
>> "Apache OpenOffice development focus areas"
>> [m6]: /projects/native-lang.html
>> "Apache OpenOffice in your Native Language"
>>
>> Regards,
>> Dave
>>
>> On Apr 7, 2012, at 1:55 PM, Dave Fisher wrote:
>>
>>> Hi Andrea,
>>>
>>> On Apr 7, 2012, at 11:48 AM, Andrea Pescetti wrote:
>>>
>>>> On 05/04/2012 Dave Fisher wrote:
>>>>> Here is what you would do to effect all of the FR site at once for
>>>>> translated branding and navigation buttons:
>>>>
>>>> Thanks for the detailed instructions, that should definitely be put on
>>>> the wiki. I tried to apply them to the IT site:
>>>> http://svn.apache.org/viewvc?view=revision&revision=1310806
>>>> Everything seems OK, but I can't see the changes at
>>>> http://ooo-site.staging.apache.org/it/ or
>>>> http://www.openoffice.org/it/
>>>
>>> I think that there was a hiccup with the CMS. Joe asked that you trigger your build again.
>>>
>>> I went ahead and added the files for French. I also made a change to a comment in ooo-site/trunk/lib/view.pm. This is a trick that will cause the staging build to do a full build causing all of the IT and FR sites to be changed to the new SSI.
>>>
>>>
>>>>
>>>>> (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext
>>>>> ... Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext to
>>>>> /fr/topnav.mdtext
>>>>
>>>> I did this, just replacing "fr" -> "it".
>>>>
>>>>> (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext
>>>>
>>>> Here I actually copied content/brand.mdtext to content/it/brand.mdtext
>>>> (which is probably what you meant) and edited accordingly.
>>>>
>>>>> (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext
>>>>
>>>> Same as (2).
>>>>
>>>>> Commit all three changes at once and the whole of the FR part of the
>>>>> site takes these changes at once. O(1) operation.
>>>>
>>>> I committed, the build was triggered and succeeded but I don't see the
>>>> changes.
>>>
>>> The trick with lib/view.pm may be required.
>>>
>>>>
>>>>> If you would like I'll create the mdtext files and then you can
>>>>> translate.
>>>>
>>>> This would probably be helpful to all native-lang projects, since even those not familiar with SVN could simply submit the translated version of their mdtext files.
>>>
>>> Yes, but I want to wait until we do a couple and make sure all the proper details are covered.
>>>
>>> We may be adding a news.mdtext and index.mdtext for the main index page, but that will be a separate thread of work.
>>>
>>> And it is not a reason to wait. I'll look into doing it for many NLs this week.
>>>
>>> Here is a list of the next NLs to setup:
>>>
>>> es, de, nl, fi, pt-br, ru, ja
>>>
>>> This scheme only goes a single directory level deep. Is a single translation viable for both zh_cn and zh_tw? If not then the two sites will need to be separated. I want to be careful how that is done.
>>>
>>> Regards,
>>> Dave
>>>
>>>>
>>>> Regards,
>>>> Andrea.
>>>
>
Re: [WWW] Translating branding and navigation
Posted by Reizinger Zoltán <zr...@hdsnet.hu>.
Hi,
Please make hu next.
Thanks,
Zoltan
2012.04.11 17:47 időpontban Dave Fisher ezt írta:
> Hi -
>
> es, de, nl, fi, pt-br, ru, and ja are now setup for committers to
> make translations to brand.mdtext and topnav.mdtext.
>
> I still have the question about Chinese / zh split regarding
> traditional / simplified (Taiwan / Mainland)
>
> Next languages? cs, hu? Please respond for the next NL set.
>
> brand.mdtext
> ===========
> home: home
> search: search
> name: Apache OpenOffice (incubating)
> tagline: (incubating) | The Free and Open Productivity Suite
> logo: AOO_logos/OOo_Website_v2_copy.png
> domain: www.openoffice.org
> divid: bannera
>
> topnav.mdtext
> ============
> divid: topnava
>
> - [Product][m0]
> - [Download][m1]
> - [Support][m2]
> - [Extend][m3]
> - [Develop][m4]
> - [Focus Areas][m5]
> - [Native Language][m6]
>
>
> [m0]: /product/index.html
> "Apache OpenOffice product description"
> [m1]: /download/index.html
> "Download OpenOffice.org"
> [m2]: /support/index.html
> "Find Support for OpenOffice.org"
> [m3]: /extensions/index.html
> "Extensions and Templates for OpenOffice"
> [m4]: http://incubator.apache.org/openofficeorg/get-involved.html
> "Get involved in Apache OpenOffice (incubating)"
> [m5]: /projects/accepted.html
> "Apache OpenOffice development focus areas"
> [m6]: /projects/native-lang.html
> "Apache OpenOffice in your Native Language"
>
> Regards,
> Dave
>
> On Apr 7, 2012, at 1:55 PM, Dave Fisher wrote:
>
>> Hi Andrea,
>>
>> On Apr 7, 2012, at 11:48 AM, Andrea Pescetti wrote:
>>
>>> On 05/04/2012 Dave Fisher wrote:
>>>> Here is what you would do to effect all of the FR site at once for
>>>> translated branding and navigation buttons:
>>>
>>> Thanks for the detailed instructions, that should definitely be put
>>> on
>>> the wiki. I tried to apply them to the IT site:
>>> http://svn.apache.org/viewvc?view=revision&revision=1310806
>>> Everything seems OK, but I can't see the changes at
>>> http://ooo-site.staging.apache.org/it/ or
>>> http://www.openoffice.org/it/
>>
>> I think that there was a hiccup with the CMS. Joe asked that you
>> trigger your build again.
>>
>> I went ahead and added the files for French. I also made a change to
>> a comment in ooo-site/trunk/lib/view.pm. This is a trick that will
>> cause the staging build to do a full build causing all of the IT and
>> FR sites to be changed to the new SSI.
>>
>>
>>>
>>>> (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext
>>>> ... Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext
>>>> to
>>>> /fr/topnav.mdtext
>>>
>>> I did this, just replacing "fr" -> "it".
>>>
>>>> (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext
>>>
>>> Here I actually copied content/brand.mdtext to
>>> content/it/brand.mdtext
>>> (which is probably what you meant) and edited accordingly.
>>>
>>>> (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext
>>>
>>> Same as (2).
>>>
>>>> Commit all three changes at once and the whole of the FR part of
>>>> the
>>>> site takes these changes at once. O(1) operation.
>>>
>>> I committed, the build was triggered and succeeded but I don't see
>>> the
>>> changes.
>>
>> The trick with lib/view.pm may be required.
>>
>>>
>>>> If you would like I'll create the mdtext files and then you can
>>>> translate.
>>>
>>> This would probably be helpful to all native-lang projects, since
>>> even those not familiar with SVN could simply submit the translated
>>> version of their mdtext files.
>>
>> Yes, but I want to wait until we do a couple and make sure all the
>> proper details are covered.
>>
>> We may be adding a news.mdtext and index.mdtext for the main index
>> page, but that will be a separate thread of work.
>>
>> And it is not a reason to wait. I'll look into doing it for many NLs
>> this week.
>>
>> Here is a list of the next NLs to setup:
>>
>> es, de, nl, fi, pt-br, ru, ja
>>
>> This scheme only goes a single directory level deep. Is a single
>> translation viable for both zh_cn and zh_tw? If not then the two sites
>> will need to be separated. I want to be careful how that is done.
>>
>> Regards,
>> Dave
>>
>>>
>>> Regards,
>>> Andrea.
>>
Re: [WWW] Translating branding and navigation
Posted by Andrea Pescetti <pe...@apache.org>.
On 12/04/2012 Rob Weir wrote:
> On Wed, Apr 11, 2012 at 11:47 AM, Dave Fisher wrote:
>> es, de, nl, fi, pt-br, ru, and ja are now setup for committers to
>> make translations to brand.mdtext and topnav.mdtext. ...
> Dave, I speak English and I have no idea what you are talking about
> here.
The information provided by Dave is still very useful. I was able to
edit the links in the Italian website thanks to his instructions, and
having all files already in place for the other localizations will save
a significant part of the localization work. That said, I agree we
should aim at streamlining this further.
> Would something like this work instead:
> 1) Have an ODF text document (or spreadhseet) that has a table
> listing the strings in the standard webpage template, English in one
> column, translations to go in another column. Poor man's Pootle.
It could work, but it seems a bit rigid. For example, the Italian
website has different main links: we don't link to the Native Languages
since we already link to the English website; we prefer to link to both
Extensions and Templates instead of the Extensions intermediate page;
when a resource is available in Italian, we link to the Italian version.
All you need is actually a list of links and texts to display for them.
And this can even be provided by e-mail or the wiki for those who are
scared of BugZilla.
Regards,
Andrea.
Re: [WWW] Translating branding and navigation
Posted by Rob Weir <ro...@apache.org>.
On Wed, Apr 11, 2012 at 11:47 AM, Dave Fisher <da...@comcast.net> wrote:
> Hi -
>
> es, de, nl, fi, pt-br, ru, and ja are now setup for committers to make translations to brand.mdtext and topnav.mdtext.
>
> I still have the question about Chinese / zh split regarding traditional / simplified (Taiwan / Mainland)
>
> Next languages? cs, hu? Please respond for the next NL set.
>
> brand.mdtext
> ===========
> home: home
> search: search
> name: Apache OpenOffice (incubating)
> tagline: (incubating) | The Free and Open Productivity Suite
> logo: AOO_logos/OOo_Website_v2_copy.png
> domain: www.openoffice.org
> divid: bannera
>
> topnav.mdtext
> ============
> divid: topnava
>
> - [Product][m0]
> - [Download][m1]
> - [Support][m2]
> - [Extend][m3]
> - [Develop][m4]
> - [Focus Areas][m5]
> - [Native Language][m6]
>
>
> [m0]: /product/index.html "Apache OpenOffice product description"
> [m1]: /download/index.html "Download OpenOffice.org"
> [m2]: /support/index.html "Find Support for OpenOffice.org"
> [m3]: /extensions/index.html "Extensions and Templates for OpenOffice"
> [m4]: http://incubator.apache.org/openofficeorg/get-involved.html "Get involved in Apache OpenOffice (incubating)"
> [m5]: /projects/accepted.html "Apache OpenOffice development focus areas"
> [m6]: /projects/native-lang.html "Apache OpenOffice in your Native Language"
>
Dave, I speak English and I have no idea what you are talking about here.
We need to *radically simplify* how the web pages are translated.
No MDText. No Apache CMS. No command line. No markup. No angle brackets.
These are translators, not web designers. Your instructions might
help programmers translate a website, but that will only help us with
a handful of the 100+ languages OpenOffice supports.
Would something like this work instead:
1) Have an ODF text document (or spreadhseet) that has a table listing
the strings in the standard webpage template, English in one column,
translations to go in another column. Poor man's Pootle.
2) Translators fill out the translations and submit them as a patch.
3) Volunteers then cut & paste them into the actual mdtext files and
check them in. Or it wold be simple enough to automate this using the
ODF Toolkit.
Make sense? We need to get to the point where knowing Albanian is
sufficient to translate the Albanian page. Requiring someone to know
Albanian, MDText and the Apache CMS is asking for a combination of
skills that may not readily be available.
-Rob
> Regards,
> Dave
>
> On Apr 7, 2012, at 1:55 PM, Dave Fisher wrote:
>
>> Hi Andrea,
>>
>> On Apr 7, 2012, at 11:48 AM, Andrea Pescetti wrote:
>>
>>> On 05/04/2012 Dave Fisher wrote:
>>>> Here is what you would do to effect all of the FR site at once for
>>>> translated branding and navigation buttons:
>>>
>>> Thanks for the detailed instructions, that should definitely be put on
>>> the wiki. I tried to apply them to the IT site:
>>> http://svn.apache.org/viewvc?view=revision&revision=1310806
>>> Everything seems OK, but I can't see the changes at
>>> http://ooo-site.staging.apache.org/it/ or
>>> http://www.openoffice.org/it/
>>
>> I think that there was a hiccup with the CMS. Joe asked that you trigger your build again.
>>
>> I went ahead and added the files for French. I also made a change to a comment in ooo-site/trunk/lib/view.pm. This is a trick that will cause the staging build to do a full build causing all of the IT and FR sites to be changed to the new SSI.
>>
>>
>>>
>>>> (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext
>>>> ... Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext to
>>>> /fr/topnav.mdtext
>>>
>>> I did this, just replacing "fr" -> "it".
>>>
>>>> (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext
>>>
>>> Here I actually copied content/brand.mdtext to content/it/brand.mdtext
>>> (which is probably what you meant) and edited accordingly.
>>>
>>>> (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext
>>>
>>> Same as (2).
>>>
>>>> Commit all three changes at once and the whole of the FR part of the
>>>> site takes these changes at once. O(1) operation.
>>>
>>> I committed, the build was triggered and succeeded but I don't see the
>>> changes.
>>
>> The trick with lib/view.pm may be required.
>>
>>>
>>>> If you would like I'll create the mdtext files and then you can
>>>> translate.
>>>
>>> This would probably be helpful to all native-lang projects, since even those not familiar with SVN could simply submit the translated version of their mdtext files.
>>
>> Yes, but I want to wait until we do a couple and make sure all the proper details are covered.
>>
>> We may be adding a news.mdtext and index.mdtext for the main index page, but that will be a separate thread of work.
>>
>> And it is not a reason to wait. I'll look into doing it for many NLs this week.
>>
>> Here is a list of the next NLs to setup:
>>
>> es, de, nl, fi, pt-br, ru, ja
>>
>> This scheme only goes a single directory level deep. Is a single translation viable for both zh_cn and zh_tw? If not then the two sites will need to be separated. I want to be careful how that is done.
>>
>> Regards,
>> Dave
>>
>>>
>>> Regards,
>>> Andrea.
>>
>
Re: [WWW] Translating branding and navigation
Posted by Dave Fisher <da...@comcast.net>.
Hi -
es, de, nl, fi, pt-br, ru, and ja are now setup for committers to make translations to brand.mdtext and topnav.mdtext.
I still have the question about Chinese / zh split regarding traditional / simplified (Taiwan / Mainland)
Next languages? cs, hu? Please respond for the next NL set.
brand.mdtext
===========
home: home
search: search
name: Apache OpenOffice (incubating)
tagline: (incubating) | The Free and Open Productivity Suite
logo: AOO_logos/OOo_Website_v2_copy.png
domain: www.openoffice.org
divid: bannera
topnav.mdtext
============
divid: topnava
- [Product][m0]
- [Download][m1]
- [Support][m2]
- [Extend][m3]
- [Develop][m4]
- [Focus Areas][m5]
- [Native Language][m6]
[m0]: /product/index.html "Apache OpenOffice product description"
[m1]: /download/index.html "Download OpenOffice.org"
[m2]: /support/index.html "Find Support for OpenOffice.org"
[m3]: /extensions/index.html "Extensions and Templates for OpenOffice"
[m4]: http://incubator.apache.org/openofficeorg/get-involved.html "Get involved in Apache OpenOffice (incubating)"
[m5]: /projects/accepted.html "Apache OpenOffice development focus areas"
[m6]: /projects/native-lang.html "Apache OpenOffice in your Native Language"
Regards,
Dave
On Apr 7, 2012, at 1:55 PM, Dave Fisher wrote:
> Hi Andrea,
>
> On Apr 7, 2012, at 11:48 AM, Andrea Pescetti wrote:
>
>> On 05/04/2012 Dave Fisher wrote:
>>> Here is what you would do to effect all of the FR site at once for
>>> translated branding and navigation buttons:
>>
>> Thanks for the detailed instructions, that should definitely be put on
>> the wiki. I tried to apply them to the IT site:
>> http://svn.apache.org/viewvc?view=revision&revision=1310806
>> Everything seems OK, but I can't see the changes at
>> http://ooo-site.staging.apache.org/it/ or
>> http://www.openoffice.org/it/
>
> I think that there was a hiccup with the CMS. Joe asked that you trigger your build again.
>
> I went ahead and added the files for French. I also made a change to a comment in ooo-site/trunk/lib/view.pm. This is a trick that will cause the staging build to do a full build causing all of the IT and FR sites to be changed to the new SSI.
>
>
>>
>>> (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext
>>> ... Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext to
>>> /fr/topnav.mdtext
>>
>> I did this, just replacing "fr" -> "it".
>>
>>> (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext
>>
>> Here I actually copied content/brand.mdtext to content/it/brand.mdtext
>> (which is probably what you meant) and edited accordingly.
>>
>>> (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext
>>
>> Same as (2).
>>
>>> Commit all three changes at once and the whole of the FR part of the
>>> site takes these changes at once. O(1) operation.
>>
>> I committed, the build was triggered and succeeded but I don't see the
>> changes.
>
> The trick with lib/view.pm may be required.
>
>>
>>> If you would like I'll create the mdtext files and then you can
>>> translate.
>>
>> This would probably be helpful to all native-lang projects, since even those not familiar with SVN could simply submit the translated version of their mdtext files.
>
> Yes, but I want to wait until we do a couple and make sure all the proper details are covered.
>
> We may be adding a news.mdtext and index.mdtext for the main index page, but that will be a separate thread of work.
>
> And it is not a reason to wait. I'll look into doing it for many NLs this week.
>
> Here is a list of the next NLs to setup:
>
> es, de, nl, fi, pt-br, ru, ja
>
> This scheme only goes a single directory level deep. Is a single translation viable for both zh_cn and zh_tw? If not then the two sites will need to be separated. I want to be careful how that is done.
>
> Regards,
> Dave
>
>>
>> Regards,
>> Andrea.
>
Re: [WWW] Tutorial to put online - Translating branding and navigation
Posted by Dave Fisher <da...@comcast.net>.
Hi Andrea,
On Apr 7, 2012, at 11:48 AM, Andrea Pescetti wrote:
> On 05/04/2012 Dave Fisher wrote:
>> Here is what you would do to effect all of the FR site at once for
>> translated branding and navigation buttons:
>
> Thanks for the detailed instructions, that should definitely be put on
> the wiki. I tried to apply them to the IT site:
> http://svn.apache.org/viewvc?view=revision&revision=1310806
> Everything seems OK, but I can't see the changes at
> http://ooo-site.staging.apache.org/it/ or
> http://www.openoffice.org/it/
I think that there was a hiccup with the CMS. Joe asked that you trigger your build again.
I went ahead and added the files for French. I also made a change to a comment in ooo-site/trunk/lib/view.pm. This is a trick that will cause the staging build to do a full build causing all of the IT and FR sites to be changed to the new SSI.
>
>> (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext
>> ... Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext to
>> /fr/topnav.mdtext
>
> I did this, just replacing "fr" -> "it".
>
>> (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext
>
> Here I actually copied content/brand.mdtext to content/it/brand.mdtext
> (which is probably what you meant) and edited accordingly.
>
>> (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext
>
> Same as (2).
>
>> Commit all three changes at once and the whole of the FR part of the
>> site takes these changes at once. O(1) operation.
>
> I committed, the build was triggered and succeeded but I don't see the
> changes.
The trick with lib/view.pm may be required.
>
>> If you would like I'll create the mdtext files and then you can
>> translate.
>
> This would probably be helpful to all native-lang projects, since even those not familiar with SVN could simply submit the translated version of their mdtext files.
Yes, but I want to wait until we do a couple and make sure all the proper details are covered.
We may be adding a news.mdtext and index.mdtext for the main index page, but that will be a separate thread of work.
And it is not a reason to wait. I'll look into doing it for many NLs this week.
Here is a list of the next NLs to setup:
es, de, nl, fi, pt-br, ru, ja
This scheme only goes a single directory level deep. Is a single translation viable for both zh_cn and zh_tw? If not then the two sites will need to be separated. I want to be careful how that is done.
Regards,
Dave
>
> Regards,
> Andrea.
Re: [WWW] Tutorial to put online - Translating branding and navigation
Posted by Andrea Pescetti <pe...@apache.org>.
On 05/04/2012 Dave Fisher wrote:
> Here is what you would do to effect all of the FR site at once for
> translated branding and navigation buttons:
Thanks for the detailed instructions, that should definitely be put on
the wiki. I tried to apply them to the IT site:
http://svn.apache.org/viewvc?view=revision&revision=1310806
Everything seems OK, but I can't see the changes at
http://ooo-site.staging.apache.org/it/ or
http://www.openoffice.org/it/
> (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext
> ... Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext to
> /fr/topnav.mdtext
I did this, just replacing "fr" -> "it".
> (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext
Here I actually copied content/brand.mdtext to content/it/brand.mdtext
(which is probably what you meant) and edited accordingly.
> (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext
Same as (2).
> Commit all three changes at once and the whole of the FR part of the
> site takes these changes at once. O(1) operation.
I committed, the build was triggered and succeeded but I don't see the
changes.
> If you would like I'll create the mdtext files and then you can
> translate.
This would probably be helpful to all native-lang projects, since even
those not familiar with SVN could simply submit the translated version
of their mdtext files.
Regards,
Andrea.
Re: [WWW] Tutorial to put online
Posted by FR web forum <oo...@free.fr>.
>Would you like help with either of these?
No, it will be fine.
>Sorry if this is different from your preferred method.
>I will think about how we can accommodate use of editors
>like BlueGriffon with the Apache CMS.
Don't worry, I can adapt.
Regards
Re: [WWW] Tutorial to put online
Posted by Dave Fisher <da...@comcast.net>.
Hi -
On Apr 5, 2012, at 11:40 AM, FR web forum wrote:
>> What type of file are you wanting to upload and where do
>> you want to put it in the tree?
> PDF, ODF and perhaps ZIP files.
> Put in Documentation directory with other tutorials.
(A) You should be able to add these files to the svn using your client program.
or
(B) Personally I work from the command line with a checked out copy of the web trunk. In that mode -
- copy the files to the directory.
- svn add the files.
- svn commit the changes.
Would you like help with either of these?
>
>> Mine regards the way you are using index.xhtml to bypass index.html
>> to translate the navigation. You are working against the site design.
> Sorry, I don't want it.
> I use BlueGriffon editor and xhtml is its default extension.
> I will fix it ASAP.
Are you editing directly from the page on the website? If so, I can see the trouble, and more coming. This may not be a viable way to edit. Let me explain.
The html source in the ooo-site repository is html from the legacy project. It is content without the Apache project's banner and navigation. To properly edit the site you must either:
(1) Use the Apache CMS Bookmarklet.
or
(2) Checkout a local copy of the ooo-site svn and work locally.
Sorry if this is different from your preferred method. I will think about how we can accommodate use of editors like BlueGriffon with the Apache CMS.
>
>> Here is what you would do to effect all of the FR site at once for
>> translated branding and navigation buttons:
> Very much thanks for your detailled explanations.
> I'll follow it for make conform our webpages to your standards.
Thanks. I am happy. I have been waiting for someone to use it.
Regards,
Dave
>
Re: [WWW] Tutorial to put online
Posted by FR web forum <oo...@free.fr>.
>What type of file are you wanting to upload and where do
>you want to put it in the tree?
PDF, ODF and perhaps ZIP files.
Put in Documentation directory with other tutorials.
>Mine regards the way you are using index.xhtml to bypass index.html
>to translate the navigation. You are working against the site design.
Sorry, I don't want it.
I use BlueGriffon editor and xhtml is its default extension.
I will fix it ASAP.
>Here is what you would do to effect all of the FR site at once for
>translated branding and navigation buttons:
Very much thanks for your detailled explanations.
I'll follow it for make conform our webpages to your standards.
Re: [WWW] Tutorial to put online
Posted by Dave Fisher <da...@comcast.net>.
Hi -
What type of file are you wanting to upload and where do you want to put it in the tree?
Also, both Joe and I have been watching the commits and have some advice.
Joe's advice is to look at http://ooo-site.staging.apache.org/fr/ to avoid publishing too often.
Mine regards the way you are using index.xhtml to bypass index.html to translate the navigation. You are working against the site design.
Here is what you would do to effect all of the FR site at once for translated branding and navigation buttons:
(1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext
doctype: /doctype.html
brand: /brand.html
footer: /footer.html
topnav: /topnav.html
home: home
Change /brand.mdtext to /fr/brand.html
Change /topnav.mdtext to /fr/topnav.mdtext
(2) Copy /trunk/content/brand.mdtext from content/brand.mdtext
home: home
search: search
name: Apache OpenOffice (incubating)
tagline: (incubating) | The Free and Open Productivity Suite
logo: AOO_logos/AOO_orb1_new.jpg
domain: www.openoffice.org
divid: bannera
Translate the first four parameters.
(3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext
divid: topnava
- [Product][m0]
- [Download][m1]
- [Support][m2]
- [Extend][m3]
- [Develop][m4]
- [Focus Areas][m5]
- [Native Language][m6]
[m0]: /product/index.html "Apache OpenOffice product description"
[m1]: /download/index.html "Download OpenOffice.org"
[m2]: /support/index.html "Find Support for OpenOffice.org"
[m3]: /extensions/index.html "Extensions and Templates for OpenOffice"
[m4]: http://incubator.apache.org/openofficeorg/get-involved.html "Get involved in Apache OpenOffice (incubating)"
[m5]: /projects/accepted.html "Apache OpenOffice development focus areas"
[m6]: /projects/native-lang.html "Apache OpenOffice in your Native Language"
Translate and modify as you require.
Commit all three changes at once and the whole of the FR part of the site takes these changes at once. O(1) operation.
If you would like I'll create the mdtext files and then you can translate.
On Apr 4, 2012, at 1:58 PM, FR web forum wrote:
> Bonjour,
> Actually, I refresh our french website pages.
> I would like to add some new tutorials for our users.
> But I don't know how can I upload it.
> Should I use an FTP or another way?
> Thank you for help