9 Nov
2012
9 Nov
'12
11:53 a.m.
On Oct 29, 2012, at 5:33 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote:
On Thu, Oct 25, 2012 at 6:07 PM, Jean-Vincent Drean
<jv(a)xwiki.com> wrote:
I prefer "visibility" because it's easier to understand IMO.
"scope" is like saying "stuff".
But it's a detail… Again all I'd like is consistency which is now broken...
Thanks
-Vincent
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
OK for scope, I proposed "visibility" it to follow wiki macros but I
don't like it much either. Hi devs,
Following the discussion about general architecture of the new
localization module 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 would have preferred TranslationClass but I see your point.
* set the "visibility" field to
"Global", "Current wiki", "Current user"
WDYT about scope ? I'm implementing
http://jira.xwiki.org/browse/XWIKI-8234 and I went for scope there
because I think it's more than just "visibility". >> As for the content of the document it will
stay the same as in
>> preferences based documents for now.
>>
>> 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.
>> --
>> Thomas Mortagne