charsetEncoding

[rodo <ro...@wanadoo.es>]

hello
I have problems with the charset encoding.
I'm interesting in configure slide client and server for iso-8859-1 endoding but It doesn´t success.
I've donwload the last cvs revision and I configured slide.properties with the entry org.apache.slide.urlEncoding=ISO-8859-1
what can I do?


Slide client return errors like the follow one:

Fatal Error: unexpected char: _
antlr.TokenStreamRecognitionException: unexpected char: _
        at org.apache.webdav.cmd.ClientLexer.nextToken(ClientLexer.java:260)
        at antlr.TokenBuffer.fill(TokenBuffer.java:61)
        at antlr.TokenBuffer.LA(TokenBuffer.java:70)
        at antlr.LLkParser.LA(LLkParser.java:50)
        at antlr.Parser.match(Parser.java:179)
        at org.apache.webdav.cmd.ClientParser.cd(ClientParser.java:985)
        at org.apache.webdav.cmd.ClientParser.command(ClientParser.java:328)
        at org.apache.webdav.cmd.ClientParser.commands(ClientParser.java:221)
        at org.apache.webdav.cmd.Client.run(Client.java:159)
        at org.apache.webdav.cmd.Slide.main(Slide.java:124)
_____________________________________________________________________
Horas ilimitadas para leer y enviar correos con Tarifa Plana Wanadoo 
¡¡ desde las 3 de la tarde!!
Compruébalo en http://www.wanadoo.es/acceso-internet


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: charsetEncoding

[Sung-Gu <je...@apache.org>]

Hi rodo,

I'd like to point the difference between your article and your stack trace
message.

My conclusion is that your current problem is the same one as
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14836

> ----- Original Message -----
> From: "rodo" <ro...@wanadoo.es>
> Subject: charsetEncoding
>
>
> hello
> I have problems with the charset encoding.
> I'm interesting in configure slide client and server for iso-8859-1
endoding but It doesn´t success.
> I've donwload the last cvs revision and I configured slide.properties with
the entry org.apache.slide.urlEncoding=ISO-8859-1
> what can I do?

Probably, you're using computer environment with iso-8859-1 now.
Then you don't need to set charset encoding by manual.
What if you want to have another charset encoding not you used in your
environment,
you may create a string instance like new String("the string", iso-8859-2)
right now.
Because it's implemented to set charset yet...  :(

If you really want the function and you can expect it...
It will be supported sooner or later for 2.0...
That's ready in my own repository requiring some arrangement...  ^^;

>
> Slide client return errors like the follow one:
>
> Fatal Error: unexpected char: _
> antlr.TokenStreamRecognitionException: unexpected char: _
>         at
org.apache.webdav.cmd.ClientLexer.nextToken(ClientLexer.java:260)
>         at antlr.TokenBuffer.fill(TokenBuffer.java:61)
>         at antlr.TokenBuffer.LA(TokenBuffer.java:70)
>         at antlr.LLkParser.LA(LLkParser.java:50)
>         at antlr.Parser.match(Parser.java:179)
>         at org.apache.webdav.cmd.ClientParser.cd(ClientParser.java:985)
>         at
org.apache.webdav.cmd.ClientParser.command(ClientParser.java:328)
>         at
org.apache.webdav.cmd.ClientParser.commands(ClientParser.java:221)
>         at org.apache.webdav.cmd.Client.run(Client.java:159)
>         at org.apache.webdav.cmd.Slide.main(Slide.java:124)

The direct reason you get the error message is that antlr error handling is
incorrect, I guess.
But you may want your string is a string defined  in the bugzilla that is
known to you.

Your another try might be a choice to use a client 1.0 version as tagged
SLIDE_1_0 in cvs
Hmm.... also I'm considering of importing the slide 1.0 for 2.0 command line
client.

Sung-Gu

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>