26 Nov
2008
26 Nov
'08
1:52 p.m.
Hello,
I'd like to work on translations of default XE pages (pages that are not
internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
In order to do things correctly I'd like to now the syntax I should use
for the $msg.get values.
What we have in a page like XWiki.XWikiUserSheet is :
"platform.core.profile.firstname" for the firstname
1 ) Should I use the same syntax ("platform.core.tags.title" for the
title of Main.Tags - if i keep my example) ?
2 ) Or should we use more scalable values (tomorrow we will have a core
and applications on it : should we consider the Panels as an application
and have something like "application.panel.panelname.element" ?).
3 ) Maybe that we also can use things like the fullname of a page in the
value (to quickly identify it) and having something like :
"appplication.panel.Panels.Search.title"
I'm waiting for your advices on this (1 / 2 / 3 or another proposal).
Thanks,
Thomas Eveilleau
26 Nov
26 Nov
2:21 p.m.
New subject: [xwiki-devs] Translations : syntax to use (msg.get values) to internationalize pages
Hi,
On Wed, Nov 26, 2008 at 1:52 PM, Thomas Eveilleau <thomas(a)xwiki.com> wrote:
Hello,
I'd like to work on translations of default XE pages (pages that are not
internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
In order to do things correctly I'd like to now the syntax I should use
for the $msg.get values.
What we have in a page like XWiki.XWikiUserSheet is :
"platform.core.profile.firstname" for the firstname
1 ) Should I use the same syntax ("platform.core.tags.title" for the
title of Main.Tags - if i keep my example) ?
2 ) Or should we use more scalable values (tomorrow we will have a core
and applications on it : should we consider the Panels as an application
and have something like "application.panel.panelname.element" ?).
3 ) Maybe that we also can use things like the fullname of a page in the
value (to quickly identify it) and having something like :
"appplication.panel.Panels.Search.title"
I'm waiting for your advices on this (1 / 2 / 3 or another proposal).
Proposal 3) looks good to me since it would be quite helpful to know on what
part of the interface a message is located when translating it to other
languages.
Guillaume
Thanks,
Thomas Eveilleau
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc
http://blog.xwiki.com/
2:42 p.m.
New subject: [xwiki-devs] Translations : syntax to use (msg.get values) to internationalize pages
Hi there,
On Nov 26, 2008, at 2:21 PM, Guillaume Lerouge wrote:
Hi,
On Wed, Nov 26, 2008 at 1:52 PM, Thomas Eveilleau <thomas(a)xwiki.com>
wrote:
I'll let Sergiu answer first since he's the one who has thought the
most about this.
However 3) doesn't sound so good to me:
* text not very reusable for other locations
* subject to document name change so high risk of being dis-synchronized
* For applications resource bundles should go in wiki pages and thus
the namespace is already done by the application space
The main resource bundles should only be for templates/skins.
Everything application-related should go in Document Resource Bundles
IMO:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplica…
Thanks
-Vincent
Hello,
I'd like to work on translations of default XE pages (pages that
are not
internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
In order to do things correctly I'd like to now the syntax I should
use
for the $msg.get values.
What we have in a page like XWiki.XWikiUserSheet is :
"platform.core.profile.firstname" for the firstname
1 ) Should I use the same syntax ("platform.core.tags.title" for
the
title of Main.Tags - if i keep my example) ?
2 ) Or should we use more scalable values (tomorrow we will have a
core
and applications on it : should we consider the Panels as an
application
and have something like "application.panel.panelname.element" ?).
3 ) Maybe that we also can use things like the fullname of a page
in the
value (to quickly identify it) and having something like :
"appplication.panel.Panels.Search.title"
I'm waiting for your advices on this (1 / 2 / 3 or another
proposal).
Proposal 3) looks good to me since it would be quite helpful to know
on what
part of the interface a message is located when translating it to
other
languages. 
8:07 p.m.
Vincent Massol wrote:
Hi there,
On Nov 26, 2008, at 2:21 PM, Guillaume Lerouge wrote:
How about:
<product>.<module>[.<topic>[.<subtopics...>]].[element]
Where product is either platform or the name of the product (xe, xws,
xeclipse), module is either the name of the platform component (core,
rendering, macros) or the name of the application (blog, calendar,
administration), topic is an optional component or application
submodule, and element is the text being translated.
Examples:
platform.core.action.objectRemove.noClassnameSpecified
platform.macros.code.unknownSyntax
platform.macros.velocity.unhandledException
xe.administration.groups.addNewUser
xe.blog.management.createBlog
xe.blog.blogPost.editing.hide
Given that applications might not be bundled with a product, and that
most applications are not specific to one product, but can be used in
several, we could remove the product name.
I don't think that the component/application name should be removed,
even though the localization is included in an application's space and
resources are used in one type of document, because we could get
conflicts when using several applications together (for example
management.title could be used both in the blog and calendar applications).
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi,
On Wed, Nov 26, 2008 at 1:52 PM, Thomas Eveilleau <thomas(a)xwiki.com>
wrote:
I'll let Sergiu answer first since he's the one who has thought the
most about this.
However 3) doesn't sound so good to me:
* text not very reusable for other locations
* subject to document name change so high risk of being dis-synchronized
* For applications resource bundles should go in wiki pages and thus
the namespace is already done by the application space
The main resource bundles should only be for templates/skins.
Everything application-related should go in Document Resource Bundles
IMO:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplica…
Hello,
I'd like to work on translations of default XE pages (pages that
are not
internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
In order to do things correctly I'd like to now the syntax I should
use
for the $msg.get values.
What we have in a page like XWiki.XWikiUserSheet is :
"platform.core.profile.firstname" for the firstname
1 ) Should I use the same syntax ("platform.core.tags.title" for
the
title of Main.Tags - if i keep my example) ?
2 ) Or should we use more scalable values (tomorrow we will have a
core
and applications on it : should we consider the Panels as an
application
and have something like "application.panel.panelname.element" ?).
3 ) Maybe that we also can use things like the fullname of a page
in the
value (to quickly identify it) and having something like :
"appplication.panel.Panels.Search.title"
I'm waiting for your advices on this (1 / 2 / 3 or another
proposal).
Proposal 3) looks good to me since it would be quite helpful to know
on what
part of the interface a message is located when translating it to
other
languages.
8:54 p.m.
New subject: [xwiki-devs] Translations : syntax to use (msg.get values) to internationalize pages
On Nov 26, 2008, at 8:07 PM, Sergiu Dumitriu wrote:
Vincent Massol wrote:
+1 to the above without the product name except for platform.
Hi there,
On Nov 26, 2008, at 2:21 PM, Guillaume Lerouge wrote:
How about:
<product>.<module>[.<topic>[.<subtopics...>]].[element]
Where product is either platform or the name of the product (xe, xws,
xeclipse), module is either the name of the platform component (core,
rendering, macros) or the name of the application (blog, calendar,
administration), topic is an optional component or application
submodule, and element is the text being translated.
Examples:
platform.core.action.objectRemove.noClassnameSpecified
platform.macros.code.unknownSyntax
platform.macros.velocity.unhandledException
xe.administration.groups.addNewUser
xe.blog.management.createBlog
xe.blog.blogPost.editing.hide
Given that applications might not be bundled with a product, and that
most applications are not specific to one product, but can be used in
several, we could remove the product name. Hi,
On Wed, Nov 26, 2008 at 1:52 PM, Thomas Eveilleau <thomas(a)xwiki.com>
wrote:
I'll let Sergiu answer first since he's the one who has thought the
most about this.
However 3) doesn't sound so good to me:
* text not very reusable for other locations
* subject to document name change so high risk of being dis-
synchronized
* For applications resource bundles should go in wiki pages and thus
the namespace is already done by the application space
The main resource bundles should only be for templates/skins.
Everything application-related should go in Document Resource Bundles
IMO:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplica…
Hello,
I'd like to work on translations of default XE pages (pages that
are not
internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
In order to do things correctly I'd like to now the syntax I should
use
for the $msg.get values.
What we have in a page like XWiki.XWikiUserSheet is :
"platform.core.profile.firstname" for the firstname
1 ) Should I use the same syntax ("platform.core.tags.title" for
the
title of Main.Tags - if i keep my example) ?
2 ) Or should we use more scalable values (tomorrow we will have a
core
and applications on it : should we consider the Panels as an
application
and have something like "application.panel.panelname.element" ?).
3 ) Maybe that we also can use things like the fullname of a page
in the
value (to quickly identify it) and having something like :
"appplication.panel.Panels.Search.title"
I'm waiting for your advices on this (1 / 2 / 3 or another
proposal).
Proposal 3) looks good to me since it would be quite helpful to know
on what
part of the interface a message is located when translating it to
other
languages. I don't think that the component/application name
should be removed,
even though the localization is included in an application's space and
resources are used in one type of document, because we could get
conflicts when using several applications together (for example
management.title could be used both in the blog and calendar
applications).
Agreed. +1 to keep it.
Thanks
-Vincent
27 Nov
27 Nov
10:57 a.m.
Vincent Massol a écrit :
On Nov 26, 2008, at 8:07 PM, Sergiu Dumitriu wrote:
Ok !
Thanks,
Thomas
Vincent Massol wrote:
+1 to the above without the product name except for platform.
Hi there,
On Nov 26, 2008, at 2:21 PM, Guillaume Lerouge wrote:
How about:
<product>.<module>[.<topic>[.<subtopics...>]].[element]
Where product is either platform or the name of the product (xe, xws,
xeclipse), module is either the name of the platform component (core,
rendering, macros) or the name of the application (blog, calendar,
administration), topic is an optional component or application
submodule, and element is the text being translated.
Examples:
platform.core.action.objectRemove.noClassnameSpecified
platform.macros.code.unknownSyntax
platform.macros.velocity.unhandledException
xe.administration.groups.addNewUser
xe.blog.management.createBlog
xe.blog.blogPost.editing.hide
Given that applications might not be bundled with a product, and that
most applications are not specific to one product, but can be used in
several, we could remove the product name.
Hi,
On Wed, Nov 26, 2008 at 1:52 PM, Thomas Eveilleau <thomas(a)xwiki.com>
wrote:
> Hello,
>
> I'd like to work on translations of default XE pages (pages that
> are not
> internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
> In order to do things correctly I'd like to now the syntax I should
> use
> for the $msg.get values.
>
> What we have in a page like XWiki.XWikiUserSheet is :
> "platform.core.profile.firstname" for the firstname
>
> 1 ) Should I use the same syntax ("platform.core.tags.title" for
> the
> title of Main.Tags - if i keep my example) ?
>
> 2 ) Or should we use more scalable values (tomorrow we will have a
> core
> and applications on it : should we consider the Panels as an
> application
> and have something like "application.panel.panelname.element" ?).
>
> 3 ) Maybe that we also can use things like the fullname of a page
> in the
> value (to quickly identify it) and having something like :
> "appplication.panel.Panels.Search.title"
>
> I'm waiting for your advices on this (1 / 2 / 3 or another
> proposal).
>
>
Proposal 3) looks good to me since it would be quite helpful to know
on what
part of the interface a message is located when translating it to
other
languages.
I'll let Sergiu answer first since he's the one who has thought
the
most about this.
However 3) doesn't sound so good to me:
* text not very reusable for other locations
* subject to document name change so high risk of being dis-
synchronized
* For applications resource bundles should go in wiki pages and thus
the namespace is already done by the application space
The main resource bundles should only be for templates/skins.
Everything application-related should go in Document Resource Bundles
IMO:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplica…
I don't
think that the component/application name should be removed,
even though the localization is included in an application's space and
resources are used in one type of document, because we could get
conflicts when using several applications together (for example
management.title could be used both in the blog and calendar
applications).
Agreed. +1 to keep it.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11:06 a.m.
New subject: [xwiki-devs] Translations : syntax to use (msg.get values) to internationalize pages
+1
On Wed, Nov 26, 2008 at 8:07 PM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
Vincent Massol wrote:
--
Thomas Mortagne
Hi there,
On Nov 26, 2008, at 2:21 PM, Guillaume Lerouge wrote:
How about:
<product>.<module>[.<topic>[.<subtopics...>]].[element]
Where product is either platform or the name of the product (xe, xws,
xeclipse), module is either the name of the platform component (core,
rendering, macros) or the name of the application (blog, calendar,
administration), topic is an optional component or application
submodule, and element is the text being translated.
Examples:
platform.core.action.objectRemove.noClassnameSpecified
platform.macros.code.unknownSyntax
platform.macros.velocity.unhandledException
xe.administration.groups.addNewUser
xe.blog.management.createBlog
xe.blog.blogPost.editing.hide
Given that applications might not be bundled with a product, and that
most applications are not specific to one product, but can be used in
several, we could remove the product name.
I don't think that the component/application name should be removed,
even though the localization is included in an application's space and
resources are used in one type of document, because we could get
conflicts when using several applications together (for example
management.title could be used both in the blog and calendar applications).
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Hi,
On Wed, Nov 26, 2008 at 1:52 PM, Thomas Eveilleau <thomas(a)xwiki.com>
wrote:
I'll let Sergiu answer first since he's the one who has thought the
most about this.
However 3) doesn't sound so good to me:
* text not very reusable for other locations
* subject to document name change so high risk of being dis-synchronized
* For applications resource bundles should go in wiki pages and thus
the namespace is already done by the application space
The main resource bundles should only be for templates/skins.
Everything application-related should go in Document Resource Bundles
IMO:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplica…
Hello,
I'd like to work on translations of default XE pages (pages that
are not
internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
In order to do things correctly I'd like to now the syntax I should
use
for the $msg.get values.
What we have in a page like XWiki.XWikiUserSheet is :
"platform.core.profile.firstname" for the firstname
1 ) Should I use the same syntax ("platform.core.tags.title" for
the
title of Main.Tags - if i keep my example) ?
2 ) Or should we use more scalable values (tomorrow we will have a
core
and applications on it : should we consider the Panels as an
application
and have something like "application.panel.panelname.element" ?).
3 ) Maybe that we also can use things like the fullname of a page
in the
value (to quickly identify it) and having something like :
"appplication.panel.Panels.Search.title"
I'm waiting for your advices on this (1 / 2 / 3 or another
proposal).
Proposal 3) looks good to me since it would be quite helpful to know
on what
part of the interface a message is located when translating it to
other
languages.
26 Nov
26 Nov
3:04 p.m.
New subject: [xwiki-devs] Translations : syntax to use (msg.get values) to internationalize pages
On Wed, Nov 26, 2008 at 1:52 PM, Thomas Eveilleau <thomas(a)xwiki.com> wrote:
Hello,
I'd like to work on translations of default XE pages (pages that are not
internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
In order to do things correctly I'd like to now the syntax I should use
for the $msg.get values.
What we have in a page like XWiki.XWikiUserSheet is :
"platform.core.profile.firstname" for the firstname
1 ) Should I use the same syntax ("platform.core.tags.title" for the
title of Main.Tags - if i keep my example) ?
2 ) Or should we use more scalable values (tomorrow we will have a core
and applications on it : should we consider the Panels as an application
and have something like "application.panel.panelname.element" ?).
3 ) Maybe that we also can use things like the fullname of a page in the
value (to quickly identify it) and having something like :
"appplication.panel.Panels.Search.title"
-1 for 3), it too difficult to reuse and to easy to break. If you want
to add location informations you can easily do that with comments in
translation resource file of page.
1) Main.Tags is not part of core since it's a XE xar page so using
"platform.core" for it is wrong.
Also same as Vincent about translations resources: XE or any
non-platform translation should go to it's respective xar and not in
the core Application Resource files.
I'm waiting for your advices on this (1 / 2 / 3 or another proposal).
Thanks,
Thomas Eveilleau
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
3:08 p.m.
Thomas Mortagne a écrit :
On Wed, Nov 26, 2008 at 1:52 PM, Thomas Eveilleau
<thomas(a)xwiki.com> wrote:
Just for information : XWiki.XWikiUserSheets is not a XE xar page ?
Hello,
I'd like to work on translations of default XE pages (pages that are not
internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
In order to do things correctly I'd like to now the syntax I should use
for the $msg.get values.
What we have in a page like XWiki.XWikiUserSheet is :
"platform.core.profile.firstname" for the firstname
1 ) Should I use the same syntax ("platform.core.tags.title" for the
title of Main.Tags - if i keep my example) ?
2 ) Or should we use more scalable values (tomorrow we will have a core
and applications on it : should we consider the Panels as an application
and have something like "application.panel.panelname.element" ?).
3 ) Maybe that we also can use things like the fullname of a page in the
value (to quickly identify it) and having something like :
"appplication.panel.Panels.Search.title"
-1 for 3), it too difficult to reuse and to easy to break. If you want
to add location informations you can easily do that with comments in
translation resource file of page.
1) Main.Tags is not part of core since it's a XE xar page so using
"platform.core" for it is wrong.
Also same as Vincent about translations resources: XE or any
non-platform translation should go to it's respective xar and not in
the core Application Resource files.
I'm waiting for your advices on this (1 / 2 /
3 or another proposal).
Thanks,
Thomas Eveilleau
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
3:21 p.m.
New subject: [xwiki-devs] Translations : syntax to use (msg.get values) to internationalize pages
On Nov 26, 2008, at 3:08 PM, Thomas Eveilleau wrote:
Thomas Mortagne a écrit :
Everything that is a page is a XE XAR page. So if there are resources
for that page in the current resource properties file they'll also
need to be moved.
Thanks
-Vincent
On Wed, Nov 26, 2008 at 1:52 PM, Thomas Eveilleau
<thomas(a)xwiki.com> wrote:
Just for information : XWiki.XWikiUserSheets is not a XE xar page ? Hello,
I'd like to work on translations of default XE pages (pages that
are not
internationalized yet) like Photos.WebHome, Main.Tags, Panels etc.
In order to do things correctly I'd like to now the syntax I
should use
for the $msg.get values.
What we have in a page like XWiki.XWikiUserSheet is :
"platform.core.profile.firstname" for the firstname
1 ) Should I use the same syntax ("platform.core.tags.title" for
the
title of Main.Tags - if i keep my example) ?
2 ) Or should we use more scalable values (tomorrow we will have a
core
and applications on it : should we consider the Panels as an
application
and have something like "application.panel.panelname.element" ?).
3 ) Maybe that we also can use things like the fullname of a page
in the
value (to quickly identify it) and having something like :
"appplication.panel.Panels.Search.title"
-1 for 3), it too difficult to reuse and to easy to break. If you
want
to add location informations you can easily do that with comments in
translation resource file of page.
1) Main.Tags is not part of core since it's a XE xar page so using
"platform.core" for it is wrong.
Also same as Vincent about translations resources: XE or any
non-platform translation should go to it's respective xar and not in
the core Application Resource files.
5772
days inactive
5773
days old
9 comments
5 participants
participants (5)
-
Guillaume Lerouge -
Sergiu Dumitriu -
Thomas Eveilleau -
Thomas Mortagne -
Vincent Massol