Hi,
in 1.1, I had my own markup parser and XMLPullParser, that basically
replaced all ${key} strings in Markup with the values from associated
properties files.
This no longer works for 1.2, because
MarkupParserFactory.newMarkupParser does not provide the
MarkupContainer, for which the
Just thinking out loud. Not sure it realy works. Like you would create
your own IResourceStream to read markup from say a database instead of
file, it is possible to create a resource stream which first calls the
default file resource stream and than applies the transformation and
that in turn is
Can't say I like the first approach much. When I was implementing the
localization before, that was the first thing i tried. Didn't like it
then, but maybe things have changed.
Still, it won't be possible for me to use Localizer, right? I'll have to
load the properties files myself.
Having
On 1/19/06, Matej Knopp [EMAIL PROTECTED] wrote:
Can't say I like the first approach much. When I was implementing the
localization before, that was the first thing i tried. Didn't like it
then, but maybe things have changed.
Still, it won't be possible for me to use Localizer, right? I'll
Juergen Donnerstag wrote:
On 1/19/06, Matej Knopp [EMAIL PROTECTED] wrote:
Can't say I like the first approach much. When I was implementing the
localization before, that was the first thing i tried. Didn't like it
then, but maybe things have changed.
Still, it won't be possible for me to use
What comes into my mind. MarkupResourceStream keeps a copy of
containerInfo. May be that requires less changes to your code. Though
I still think that using the StreamLocator is the much cleaner
approach.
Juergen
On 1/19/06, Juergen Donnerstag [EMAIL PROTECTED] wrote:
On 1/19/06, Matej Knopp
Yes, that is what XmlPullParser does. See XmlPullParser.parse() and
determineEncoding()
Juergen
On 1/19/06, Matej Knopp [EMAIL PROTECTED] wrote:
Juergen Donnerstag wrote:
On 1/19/06, Matej Knopp [EMAIL PROTECTED] wrote:
Can't say I like the first approach much. When I was implementing the
