I think i missed the point.
In the original posting it gave some coding of which the important part was;
I don't know how to upload files to the wiki! The wiki is different from the ODFAuthors site. The
ODFAuthors site is used during editing and proofreading so that only members of the team can access
the chapters of the guides. Once the chapters are ready they get uploaded to the wiki. Almost
anyone can read them or download them from the wiki.
Eventually (usually a week or 2 after all the chapters of a guide have been done and the whole
guide put together) the official LibreOffice website puts up links to the chapters and guide that
are on the wiki. Around the same time the guides are given to the Lulu bookstore to sell. Jean
Weber of the Documentation Team sorts out everything in this paragraph but it would be good for
other people to learn how to do all this or even just parts of it.
Getting back to the code on the wiki;
= a space (same as in html and sometimes other bits of html works too but mostly the wiki
language tries to 'simplify')
Sometimes if you try to put a space at the end of a line it gets lost. Also if you have 2 or more
spaces together the wiki reduces it to just 1 space so if you wanted 3 spaces you could break it up
by using the " " thing in the middle, such as " ". For 5 spaces " ". It
is the same in html and just makes the whole thing look a lot more confusing than it really is.
The [[ and ]] marks are to tell the wiki that there is a link in the middle. Inside the first part
is the address you want people to go to when they click on the link. The bit after the | is what
shows on the page. So people only see the "ODT" part but when they click on it they go to
The full address in the example is really
but because it's within the LibreOffice wiki rather than an external link you can choose to use the
I have a bad feeling that if you do want to use the full address and try to access the chapter as
though it was external then you might have to switch to single [ ] marks instead of the double
ones [[ ]]. Also you might need to remove the | and just use a space instead and it's possible
you might need to switch around the 1st and 2nd parts, ie to make it
I was just trying to get the page to read
ODT or PDF
with just the "ODT" and the "PDF" parts being clickable and with things neatly lined up under each
other but it became a bit of a nightmare and the coding is a lot less elegant than i would have
liked. I tried to make it as easy as possible for documenters to be able to work out where to put
their links and things but i am not brilliant at wiki-mark-up.
Different wikis do it different ways so you just have to experiment with them a bit sometimes.
Guides about how to write wiki-mark-up are often different from their implementation so they are
good to get ideas from but then just have to play around and make use of the "Preview" tab near the
top of the editing window.
From: Tom Davies <email@example.com>
To: Sophie Gautier <firstname.lastname@example.org>; "email@example.com"
Sent: Monday, 27 May 2013, 9:30
Subject: Re: [libreoffice-l10n] Uploading LO User Guides
Please could people avoid using spaces and _ in those wiki addresses? It's not really relevant to
Sophie's example because the # and after is a heading within a page rather than part of the page's
Underscores vanish in the default automatic formatting in emails and documents so it makes it
difficult to trouble-shoot when someone has a problem reaching the page. For example these 2
addresses look the same but 1 works and the other doesn't;
https://wiki.documentfoundation.org/Documentation/Publications/fr#Guides utilisateur officiels
If you look really closely you might be lucky enough to see the slight bulges in the 2nd link but
is the one with the bulges always the right one to click?
Spaces often get replaced by %20 which non-geeks find difficult to read and that makes them avoid
reading any of the rest of the url so they end up clicking on blatantly dodgy links in other
places and then being reluctant to click on our legitimate ones.
Over the past couple of weeks we have had a few problems with the % being replaced by something
like %24 which makes the line increasingly complicated
"CamelCase" is better because it doesn't get so badly messed up so easily. At first you will find
it a little awkward to read but even non-geeks manage it and are not scared off by it. The
Of course that link wont really work but is just given as an example of how a wiki address might
be written. The French page is really just simply
Which looks really simple and elegant to me.
From: Sophie Gautier <firstname.lastname@example.org>
Sent: Monday, 27 May 2013, 7:11
Subject: Re: [libreoffice-l10n] Uploading LO User Guides
On 27/05/2013 01:50, Donald Rogers wrote:
Could someone please explain how and where to upload the User Guides ODT
and PDF files for languages other than English? How is it that the files
at https://wiki.documentfoundation.org/Documentation/Publications have
paths such as this:
while the code has: [[Media:GS4001-IntroducingLibreOffice.odt|ODT]]
The documentation using_odfauthors.odt only talks about the English
version. I want to know what the localization teams do.
You can build a wiki area in your language and place the documentation
there. This is what we have done for the FR documentation (see
At the top of most of the pages on the wiki, you have a language code:
https://wiki.documentfoundation.org/Documentation and don't forget to
create a Category for your language.
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy