Hi Dennis,Thanks for your reply. I like this feature, if implemented will
save a lot of time to maintain these release-plan wiki.Althrough I am new to wiki language, I
will try to study your
experiment, and try to improve it.Thanks a lot!Kevin Suo------ Original Message ------From:
Dennis RoczekSent: Sat, 16 Aug 2014 17:52:00 +0200To: Suo Kunlong, Libreoffice WebsiteCc:
Libreoffice Ln10Subject: RE: [libreoffice-website] WIKI: how to use
{{Release-plan-one-line-interval}} template
Hi Kevin,
well at the moment this is a test and a proof of concept. My initial idea behind these translations
and templates were that only the English page has to be updated and then all corresponding language
pages get updated automatically.
If you do want to see the actual status of this experiment,
watchhttps://wiki.documentfoundation.org/User:Dennisroczek/releaseplanAs you can see, not every
stuff is working correctly. Feel free to improve the situation as I don't know when I will enough
time to finish this experiment. At least I can say, that this is theoretical working but needs the
last bugs resolved before rolling out.
To answer your question: the dateformat template doesn't have any effect on the zh-hans releaseplan
page as this parameter is never called. This is another reason why I started this experiment
:-)
Regards,
Dennis Roczek-----Original Message-----
From: Kevin Suo [mailto:suokunlong@gmail.com]
Sent: Saturday, August 16, 2014 5:18 PM
To: LibreOffice Website
Cc: Libreoffice ln10
Subject: [libreoffice-website] WIKI: how to use {{Release-plan-one-line-
interval}} template
Hi all,could someone guide me how to use the
{{Release-plan-one-line-interval}} wiki template to show the release
weeks and dates in localized format?I want to create this
page:https://wiki.documentfoundation.org/WikiAction/edit/ReleasePlan/zh-
hansI copied the english wiki source
from:https://wiki.documentfoundation.org/WikiAction/edit/ReleasePlanIsee this page uses
Release-plan-one-line-interval template, for
example:{{Release-plan-one-line-interval | 2013 | 47 | 2014 | 5 |
[[ReleasePlan/4.2#4.2.0 release|4.2.0]]}}and I see the "Release-plan-one-
line-interval" uses template "Week",
"String-Week", "Date" and "Dateformat" to show week and dates.So, I
added zh-hans to Template:String-Week, so now it looks like:{{#switch:
{{{1|}}} | de = Kalenderwoche | zh-hans = 周: | en | #default = Week}}and I
also added zh-hans to Template:Dateformat, so now it looks
like:{{#switch: {{{1|}}} | de = iso | pt-br = jnY | zh-hans = iso | en | #default
= smdy}}But
on:https://wiki.documentfoundation.org/WikiAction/edit/ReleasePlan/zh-
hansthe weeks and dates are still in english format:Week 47 , Nov 18, 2013 -
Nov 24, 2013I want it to show:周:47 , 2013-11-18 - 2013-11-24Did I do sth
wrong, or I missed sth?Thanks for your help!Kevin Suo
--
To unsubscribe e-mail
to:website+unsubscribe@global.libreoffice.orgProblems?http://www.libreoffice.org/get-help/mailing-lists/how-to-
unsubscribe/
Posting guidelines + more:http://wiki.documentfoundation.org/NetiquetteList
archive:http://listarchives.libreoffice.org/global/website/All messages sent to this list will be
publicly archived and cannot be deleted
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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
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.