25 Oct
2012
25 Oct
'12
6:12 p.m.
On 10/25/2012 04:47 PM, Thomas Mortagne wrote:
On Thu, Oct 25, 2012 at 4:43 PM, Vincent Massol
<vincent(a)massol.net> wrote:
Note there is always the possibility to use "XWiki.TranslationSetClass"
or something like this later on for objects with translations (which is
also more correct, since there is not just one translation).
Jerome
Hi,
On Oct 25, 2012, at 4:07 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote:
It was actually in case later we are able to put translation in an
object as mentioned by Jerome. This way we are safe. Hi devs,
Following the discussion about general architecture of the new
localization module
I still haven't read it… I'm late sorry….
here is a more detailed proposal for the
dynamically registered wiki translations pages.
Here is how I propose to indicate that a document contains key=value
pair translations:
* put an object of class "XWiki.TranslationDocumentClass"
I'd prefer
simply XWiki.TranslationClass (no need to mention document IMO since they're all about
documents). * set the
"visibility" field to "Global", "Current wiki",
"Current user"
As for the content of the document it will stay the same as in
preferences based documents for now.
Using syntax = plain/1.0 ;)
I have other fields in mind for later (on demand,
translation message
syntax, etc.) but this is a 4.3 proposal here.
WDYT ?
Here is my +1.
+1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs