Return-Path: <neeme@one.lv>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 55081 invoked from network); 20 Jun 2000 19:30:19 -0000
Received: from the.one.lv (159.148.169.70)
  by locus.apache.org with SMTP; 20 Jun 2000 19:30:19 -0000
content-class: urn:content-classes:message
From: "Neeme Praks" <neeme@one.lv>
To: <cocoon-dev@xml.apache.org>
Subject: RE: ResourceBundles - was [RT] i18n
Date: Tue, 20 Jun 2000 21:31:30 +0200
Message-ID: <2ECFE9456D0F6A4FA77B38C25AAE23091940@the.one.lv>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.4208.0
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ResourceBundles - was [RT] i18n
Thread-Index: Ab/UoeiYJWA03EZ7QducAy0b16q/VgGSm6eQ
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N


> -----Original Message-----
> From: Mike Engelhart [mailto:mengelhart@earthtrip.com]
> Sent: Monday, June 12, 2000 9:00 PM
>=20
> on 6/12/00 11:43 AM, Berin Loritsch at=20
> bloritsch@infoplanning.com wrote:
>=20
> > <?xml version=3D"1.0"?>
> > <resource xml:lang=3D"en">
> > <group id=3D"error">
> > <value id=3D"500">Internal Server Error</value>
> > <value id=3D"404">Page not found</value>
> > </group>
> > <group id=3D"uri">
> > <value id=3D"addUser">user/add</value>
> > <value id=3D"killUser">user/obliterate</value>
> > </group>
> > <group id=3D"form">
> > <value id=3D"userName">Enter the user's name here</value>
> > </group>
> > </resource>

[snip]

> So in your example, it would be like
>=20
> String role =3D "uri";
> ResourceBundle res =3D XMLResourceFactory.getResourceBundle(role);
> res.getString("addUser");

I started to implement something like this for myself and came across
following question: would it be possible to nest groups and then address
them using a path?

So, instead of this:

<resources xml:lang=3D"en">
  <group name=3D"forms">
    <resource name=3D"contacts-search-searchfor-desc">find:</resource>
    <resource
name=3D"contacts-search-field-to-search-desc">what:</resource>
    <resource name=3D"contacts-search-from-desc">where:</resource>
    <resource name=3D"contacts-search-from-mycontacts-desc">my
contacts</resource>
    <resource name=3D"contacts-search-from-allmembers-desc">all
members</resource>

    <resource =
name=3D"contacts-search-field-to-search-all">all</resource>
    <resource name=3D"contacts-search-field-to-search-firstname">first
name</resource>
    <resource name=3D"contacts-search-field-to-search-lastname">last
name</resource>
    <resource
name=3D"contacts-search-field-to-search-phone">phone</resource>
    <resource
name=3D"contacts-search-field-to-search-email">e-mail</resource>

    <resource name=3D"contacts-search-submit">Search</resource>
  </group>
</resources>

something like this:

<resources xml:lang=3D"en">
  <group name=3D"forms">
	  <group name=3D"contacts-search">
		  <group name=3D"desc">
		    <resource name=3D"searchfor">find:</resource>
		    <resource name=3D"field-to-search">what:</resource>
		    <resource name=3D"from">where:</resource>
		    <resource name=3D"from-mycontacts">my
contacts</resource>
		    <resource name=3D"from-allmembers">all
members</resource>
		  </group>
=09
		  <group name=3D"input">
			  <group name=3D"field-to-search">
			    <resource name=3D"all">all</resource>
			    <resource name=3D"firstname">first
name</resource>
			    <resource name=3D"lastname">last
name</resource>
			    <resource name=3D"phone">phone</resource>
			    <resource name=3D"email">e-mail</resource>
			  </group>
		    <resource name=3D"submit">Search</resource>
		  </group>
	  </group>
  </group>
</resources>

And then I could address then like:

String role =3D "forms/contacts-search/desc";
ResourceBundle res =3D XMLResourceFactory.getResourceBundle(role);
res.getString("searchfor");

Is this reasonable?

Neeme