RE: NLS in Jetspeed

[David Sean Taylor <da...@bluesunrise.com>]

Hope this finds its way to the right list, and I hope everyone finds the new
list!

Im continuing Ingo's and Santiago's discussion 'RE: NLS in Jetspeed' from a
few days ago on the old list:

> > I'd like to improve the national language support in Jetspeed.

I never finished the language code for the profiler, but it shouldn't take
too long, although Im not as fast as Ingo, but who is! :))

> > * The templates are moved into respective subdirectories (e.g.
> > templates/jsp/en/{layouts,navigations,screens} for JSP

The profiler proposal specified that the implementation use file names, not
directories, for language specific resources
The directories are broken down by mediatype
Since I haven't yet completed writing the language support, Im open to
arguments for a different impl.

> (I think subclassing he TurbineTemplateService is the easiest way of doing
this)

You could also add the code to the TurbineTemplateService.
As Ingo and I are aware, it already has a fallback algorithm.
Its just a matter of deciding whether NLS should go into Turbine.
If it doesn't, it will still be difficult to separate the fallback
algorithm, and you end up completely rewriting it anyway.

BTW - Ingo - that reminds me - did our fix ever get committed on the default
name bug?

>
> Also, don't forget it is lang_COUNTRY, as in de, de_AT, de_CH, de_DE
> (jre even has a de_DE_EURO).
>
> I think the approach should be having
>
> default
> (files here)
>     lang
>     (files here maybe)
>         COUNTRY
>         (files here maybe)
> ...
>

This differs from the proposal.
See jetspeed/proposals/0005.txt

> The schema for psml is user/mime_type or group/mime_type or
> default/mime_type
> Our schema for skins is lang/mime_type/browser/version/theme
>
> I think we should unify this code under the Profiler Service,
> to have a
> method that,
> given a CapabilityMap/RunData, a "kind_of_resource" and a
> name, returns
> the resource going to
> the leaves and falling back if it does not exist.
>

Yes, when you say 'kind_of_resource' you mean:
- markup (psml)
- template
- skins ?
- ...

So this profiling service will find any resource, not just psml markup.
+1 on that

The JetspeedProfileManagerService is actually undergoing some changes, most
of the implementation will remain, but Raphael has refactored the profiler
into two services under the new customization package (see the
'psml_02-branch' branch):

1. ConfigStoreService
2. ProfileService

I will look into factoring out the resource fallback algorithm into a
generic fallback service, and also consider directories to delineate NLS
resources

-- david

RE: NLS in Jetspeed

[David Sean Taylor <da...@bluesunrise.com>]

>
> OK. I don't have any problems with the proposal. I was just
> pointing the fact that there are also geographical variations.
>  color <--> colour, USD <--> UKP, quatre vingt <--> huitante (spell?)
>

Yes, I believe the proposal covers that with examples like fr_FR, fr_BE
(Ma femme est belge) quatre vingt dix <--> nonante :)

> huitante (spell?)
Is that fr_CH? Shouldn't that be 'octante'?

> > I will look into factoring out the resource fallback algorithm into a
> > generic fallback service, and also consider directories to delineate NLS
> > resources
>
> If we go for a common "resource" solution, it will actually be
> simpler, as we would use
> the same pattern. I'm 0 on that.
>

The downside is more subdirectories, which is a pain for site maintenance.
Let me revise the proposal considering a common resource-fallback service.

>
> BTW, regarding the proposals, I'm lazy, and I would like the proposals
> to be visible from the web site.
>
> When I clean my working copy mess of the new server/permissions, etc. I
> think I will put them under xdocs/proposals (wrapped in <pre></pre> ).
> What do you think?
>

Im +1 on the relevant proposals, and -1 on any outdated proposals.


- david



> -----Original Message-----
> From: Santiago Gala [mailto:sgala@hisitech.com]
> Sent: Thursday, March 01, 2001 5:11 AM
> To: jetspeed-dev@jakarta.apache.org
> Subject: Re: NLS in Jetspeed
>
>
> David Sean Taylor wrote:
>
> > Hope this finds its way to the right list, and I hope
> everyone finds the new
> > list!
> >
>
> It did! Amazingly, it also arrived to the proper filtered box
> in my mail!
>
> >> Also, don't forget it is lang_COUNTRY, as in de, de_AT,
> de_CH, de_DE
> >> (jre even has a de_DE_EURO).
> >>
> >> I think the approach should be having
> >>
> >> default
> >> (files here)
> >>     lang
> >>     (files here maybe)
> >>         COUNTRY
> >>         (files here maybe)
> >> ...
> >>
> >
> >
> > This differs from the proposal.
> > See jetspeed/proposals/0005.txt
> >
>
> OK. I don't have any problems with the proposal. I was just
> pointing the fact that there are also geographical variations.
>  color <--> colour, USD <--> UKP, quatre vingt <--> huitante (spell?)
>
> The _EURO stuff looks pathological to me, and transient in any case,
> (as my elder daughter reminds me, I have to carry her to the
> bank january
> next year, to change all her valuable pesetas into euros :-)
>
> >
> > Yes, when you say 'kind_of_resource' you mean:
> > - markup (psml)
> > - template
> > - skins ?
> > - ...
> >
> > So this profiling service will find any resource, not just
> psml markup.
> > +1 on that
>
> Yes, that is the idea. I'm seeing that we have very similar features
> for the three problems:
> - getting a resource dependent on user/request/session info
> - specialized resources with a given search order
> - fallback algorithm to a root.
>
> >
> > The JetspeedProfileManagerService is actually undergoing
> some changes, most
> > of the implementation will remain, but Raphael has
> refactored the profiler
> > into two services under the new customization package (see the
> > 'psml_02-branch' branch):
> >
> > 1. ConfigStoreService
> > 2. ProfileService
> >
> > I will look into factoring out the resource fallback
> algorithm into a
> > generic fallback service, and also consider directories to
> delineate NLS
> > resources
>
> If we go for a common "resource" solution, it will actually
> be simpler, as we would use
> the same pattern. I'm 0 on that.
>
>
> BTW, regarding the proposals, I'm lazy, and I would like the
> proposals
> to be visible from the web site.
>
> When I clean my working copy mess of the new
> server/permissions, etc. I
> think I will put them under xdocs/proposals (wrapped in <pre></pre> ).
> What do you think?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>

Re: NLS in Jetspeed

[Santiago Gala <sg...@hisitech.com>]

David Sean Taylor wrote:

> Hope this finds its way to the right list, and I hope everyone finds the new
> list!
>

It did! Amazingly, it also arrived to the proper filtered box in my mail!
 
>> Also, don't forget it is lang_COUNTRY, as in de, de_AT, de_CH, de_DE
>> (jre even has a de_DE_EURO).
>> 
>> I think the approach should be having
>> 
>> default
>> (files here)
>>     lang
>>     (files here maybe)
>>         COUNTRY
>>         (files here maybe)
>> ...
>> 
> 
> 
> This differs from the proposal.
> See jetspeed/proposals/0005.txt
> 

OK. I don't have any problems with the proposal. I was just
pointing the fact that there are also geographical variations.
 color <--> colour, USD <--> UKP, quatre vingt <--> huitante (spell?)

The _EURO stuff looks pathological to me, and transient in any case,
(as my elder daughter reminds me, I have to carry her to the bank january
next year, to change all her valuable pesetas into euros :-)

> 
> Yes, when you say 'kind_of_resource' you mean:
> - markup (psml)
> - template
> - skins ?
> - ...
> 
> So this profiling service will find any resource, not just psml markup.
> +1 on that

Yes, that is the idea. I'm seeing that we have very similar features
for the three problems:
- getting a resource dependent on user/request/session info
- specialized resources with a given search order
- fallback algorithm to a root.

> 
> The JetspeedProfileManagerService is actually undergoing some changes, most
> of the implementation will remain, but Raphael has refactored the profiler
> into two services under the new customization package (see the
> 'psml_02-branch' branch):
> 
> 1. ConfigStoreService
> 2. ProfileService
> 
> I will look into factoring out the resource fallback algorithm into a
> generic fallback service, and also consider directories to delineate NLS
> resources

If we go for a common "resource" solution, it will actually be simpler, as we would use
the same pattern. I'm 0 on that.


BTW, regarding the proposals, I'm lazy, and I would like the proposals 
to be visible from the web site.

When I clean my working copy mess of the new server/permissions, etc. I 
think I will put them under xdocs/proposals (wrapped in <pre></pre> ).
What do you think?