Hi Alexander, *;
On Fri, Jan 28, 2011 at 6:43 AM, Alexander Thurgood
<alex.thurgood@gmail.com> wrote:
I am having a bad time trying to understand how to link, and have
published, translations that I am preparing from the English website, so
that they are visible on the French part of the website.
The decision was taken not to have translations on the main-site, i.e.
not to use the translation feature.
But yes, the way would have been to publish the translation on the
main site, then use a subsite virtual page to link it to the NL-site.
But the translations were not really meant to double the content.
Initially I had planned for a common main page, just one page where
all NL-projects would share and translate a common set of pages, and
only have their nl-project's pages for specific information
correspoding to the locale/area/organization.
People weren't using it as such though, and the "show translations"
links for one page that has translation, but no for another one that
lacks translation, etc. made it too confusing for visitors.
So I guess what would be needed is to have a corss-subsite
translation, that then would be one way (always english is the
"master" copy), that then could be used on the subsite directly.
ciao
Christian
--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/website/
*** All posts to this list are publicly archived for eternity ***
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: 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.