[xwiki-devs] [VOTE] Dynamically registered wiki translations
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" * 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. 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
On Thu, Oct 25, 2012 at 5:07 PM, Thomas Mortagne <[email protected]> wrote:
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" * 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.
I have other fields in mind for later (on demand, translation message syntax, etc.) but this is a 4.3 proposal here.
WDYT ?
+1 Thanks, Marius
Here is my +1. -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Thomas, On Thu, Oct 25, 2012 at 5:07 PM, Thomas Mortagne <[email protected]>wrote:
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" * 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.
I have other fields in mind for later (on demand, translation message syntax, etc.) but this is a 4.3 proposal here.
WDYT ?
Big +1. Workspaces will be very happy when this becomes available :) Thanks, Eduard
Here is my +1. -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi, On Oct 25, 2012, at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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
On Thu, Oct 25, 2012 at 4:43 PM, Vincent Massol <[email protected]> wrote:
Hi,
On Oct 25, 2012, at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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).
It was actually in case later we are able to put translation in an object as mentioned by Jerome. This way we are safe.
* 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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On 10/25/2012 04:47 PM, Thomas Mortagne wrote:
On Thu, Oct 25, 2012 at 4:43 PM, Vincent Massol <[email protected]> wrote:
Hi,
On Oct 25, 2012, at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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). It was actually in case later we are able to put translation in an object as mentioned by Jerome. This way we are safe.
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
* 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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jean-Vincent Drean, XWiki.
On Oct 25, 2012, at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
Well the wording we have now is "visibility". This is what we have for wiki macros… So if you want to change that I'm ok but we need to try to be consistent across the board :) Thanks -Vincent
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.
On Thu, Oct 25, 2012 at 6:11 PM, Vincent Massol <[email protected]> wrote:
On Oct 25, 2012, at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
Well the wording we have now is "visibility". This is what we have for wiki macros…
So if you want to change that I'm ok but we need to try to be consistent across the board :)
Since I'm willing to remove this from wiki macros when they'll be wiki components, the consistency issue would be temporary
Thanks -Vincent
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.
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jean-Vincent Drean, XWiki.
Hi +1 for translation, would like to help in Hindi translations -arvind On Fri, Oct 26, 2012 at 6:33 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 6:11 PM, Vincent Massol <[email protected]> wrote:
On Oct 25, 2012, at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
Well the wording we have now is "visibility". This is what we have for wiki macros…
So if you want to change that I'm ok but we need to try to be consistent across the board :)
Since I'm willing to remove this from wiki macros when they'll be wiki components, the consistency issue would be temporary
Thanks -Vincent
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.
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jean-Vincent Drean, XWiki. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Fri, Oct 26, 2012 at 3:06 PM, Arvind Gupta <[email protected]> wrote:
Hi +1 for translation, would like to help in Hindi translations
Not that you can already help translation XWiki on http://l10n.xwiki.org.
-arvind
On Fri, Oct 26, 2012 at 6:33 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 6:11 PM, Vincent Massol <[email protected]> wrote:
On Oct 25, 2012, at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
Well the wording we have now is "visibility". This is what we have for wiki macros…
So if you want to change that I'm ok but we need to try to be consistent across the board :)
Since I'm willing to remove this from wiki macros when they'll be wiki components, the consistency issue would be temporary
Thanks -Vincent
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.
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jean-Vincent Drean, XWiki. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 On Fri, Oct 26, 2012 at 3:03 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 6:11 PM, Vincent Massol <[email protected]> wrote:
On Oct 25, 2012, at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
Well the wording we have now is "visibility". This is what we have for wiki macros…
So if you want to change that I'm ok but we need to try to be consistent across the board :)
Since I'm willing to remove this from wiki macros when they'll be wiki components, the consistency issue would be temporary
Thanks -Vincent
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.
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jean-Vincent Drean, XWiki. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
On Thu, Oct 25, 2012 at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
OK for scope, I proposed "visibility" it to follow wiki macros but I don't like it much either.
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 _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jean-Vincent Drean, XWiki. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Oct 29, 2012, at 5:33 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Oct 25, 2012 at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
OK for scope, I proposed "visibility" it to follow wiki macros but I don't like it much either.
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
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
Even if it's a detail let me elaborate a bit :) For me visibility implies that the "object" _is here_ but it is not visible (my opinion might be biased because of the visibility CSS property). On the other side this definition sounds good to me: "In computer programming, a scope is the context within a computer program in which a variable name or other identifier is valid and can be used, or within which a declaration has effect." [1] The general definition fits too: "extent or range of view, outlook, application, operation, effectiveness, etc.". About the consistency issue, as I said I'm committed to make wiki macros extend WikiComponents in the near future. [1] : http://en.wikipedia.org/wiki/Scope_(programming) [2] : http://dictionary.reference.com/browse/scope On Fri, Nov 9, 2012 at 11:53 AM, Vincent Massol <[email protected]> wrote:
On Oct 29, 2012, at 5:33 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Oct 25, 2012 at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
OK for scope, I proposed "visibility" it to follow wiki macros but I don't like it much either.
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
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
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jean-Vincent Drean, XWiki.
On Fri, Nov 9, 2012 at 11:53 AM, Vincent Massol <[email protected]> wrote:
On Oct 29, 2012, at 5:33 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Oct 25, 2012 at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
OK for scope, I proposed "visibility" it to follow wiki macros but I don't like it much either.
I prefer "visibility" because it's easier to understand IMO. "scope" is like saying "stuff".
I don't agree with you, scope generally means "context" (when talking about a software at least) which is exactly what we are talking about here a lot more than visibility.
But it's a detail… Again all I'd like is consistency which is now broken...
Thanks -Vincent
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
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Nov 10, 2012, at 1:16 PM, Thomas Mortagne <[email protected]> wrote:
On Fri, Nov 9, 2012 at 11:53 AM, Vincent Massol <[email protected]> wrote:
On Oct 29, 2012, at 5:33 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Oct 25, 2012 at 6:07 PM, Jean-Vincent Drean <[email protected]> wrote:
On Thu, Oct 25, 2012 at 4:07 PM, Thomas Mortagne <[email protected]> wrote:
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".
OK for scope, I proposed "visibility" it to follow wiki macros but I don't like it much either.
I prefer "visibility" because it's easier to understand IMO. "scope" is like saying "stuff".
I don't agree with you, scope generally means "context" (when talking about a software at least) which is exactly what we are talking about here a lot more than visibility.
You're proving my point :) "Context" has a lot of meanings and is very fuzzy, especially for a user. It can mean anything... Again we're not talking about the best terminology from a development point of view here but for an end-user UI. "visibility" is exactly how the user thinks about it: is my component going to be visible in the farm, in the wiki, etc). He doesn't care how technically it's done and whether there's an underlying notion of some context, etc. Thanks -Vincent
But it's a detail… Again all I'd like is consistency which is now broken...
Thanks -Vincent
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
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Thomas, On 10/25/2012 04:07 PM, Thomas Mortagne wrote:
Hi devs,
Following the discussion about general architecture of the new localization module
Still haven't read it, I marked it as important.
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" * 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.
This is to preserve backwards compat, right? Because I think it's important to be able to write an application which can be installed in versions < 4.3 and not have to have 2 translation documents.
I have other fields in mind for later (on demand, translation message syntax, etc.) but this is a 4.3 proposal here.
We should keep in mind backwards compat for these too. Otherwise sounds correct to me, +1. Thanks, Anca
WDYT ?
Here is my +1.
On Fri, Oct 26, 2012 at 2:48 PM, Anca Luca <[email protected]> wrote:
Hi Thomas,
On 10/25/2012 04:07 PM, Thomas Mortagne wrote:
Hi devs,
Following the discussion about general architecture of the new localization module
Still haven't read it, I marked it as important.
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" * 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.
This is to preserve backwards compat, right?
Not really, just don't have the time to design and vote a new syntax so for the first version only the current syntax will be supported.
Because I think it's important to be able to write an application which can be installed in versions < 4.3 and not have to have 2 translation documents.
The idea if that you would have a field (or you would directly use the document field I'm not sure yet) where you would indicate the syntax of the translation message and it would default on the current one when nothing is set. So there will be no backward compatibility issue.
I have other fields in mind for later (on demand, translation message syntax, etc.) but this is a 4.3 proposal here.
We should keep in mind backwards compat for these too.
Otherwise sounds correct to me, +1.
Thanks, Anca
WDYT ?
Here is my +1.
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On 10/26/2012 03:06 PM, Thomas Mortagne wrote:
On Fri, Oct 26, 2012 at 2:48 PM, Anca Luca <[email protected]> wrote:
Hi Thomas,
On 10/25/2012 04:07 PM, Thomas Mortagne wrote:
Hi devs,
Following the discussion about general architecture of the new localization module
Still haven't read it, I marked it as important.
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" * 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.
This is to preserve backwards compat, right? Not really, just don't have the time to design and vote a new syntax so for the first version only the current syntax will be supported.
Because I think it's important to be able to write an application which can be installed in versions < 4.3 and not have to have 2 translation documents. The idea if that you would have a field (or you would directly use the document field I'm not sure yet) where you would indicate the syntax of the translation message and it would default on the current one when nothing is set. So there will be no backward compatibility issue.
Yes, I understand, if it doesn't impact the format of the document itself, it should be fine. Thanks, Anca
I have other fields in mind for later (on demand, translation message syntax, etc.) but this is a 4.3 proposal here.
We should keep in mind backwards compat for these too.
Otherwise sounds correct to me, +1.
Thanks, Anca
WDYT ?
Here is my +1.
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (9)
-
Anca Luca -
Arvind Gupta -
Denis Gervalle -
Eduard Moraru -
Jean-Vincent Drean -
Jerome Velociter -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol