You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-users@xalan.apache.org by David N Bertoni/Cambridge/IBM <da...@us.ibm.com> on 2002/08/13 06:54:52 UTC

RE: FW: URL escaping in Xalan-C




Hi Ann,

Yes, please post to the list.

The proprietary attributes for xsl:output that are implemented in Xalan-J
are:

   indent-amount
   omit-meta-tag
   use-url-escaping

The default values for these are, respectively:

   0
   no
   yes

You can check the Xalan-J documentation for more information:

   http://xml.apache.org/xalan-j/usagepatterns.html#outputprops

I've just finished implementing these in Xalan-C++, so support for them
will appear in the CVS repository in a day or two, and will be in the next
release..

The new code does not support the "entities" or "content-handler"
attributes.  The "entities" attribute is a possibility for the future, but
the content-handler attribute is not likely to be implemented.

Dave



                                                                                                                                      
                      "Ann Gan"                                                                                                       
                      <agan@siebel.            To:      David N Bertoni/Cambridge/IBM@Lotus, "Ann Gan" <ag...@siebel.com>              
                      com>                     cc:      "Owen Wessling" <ow...@siebel.com>                                        
                                               Subject: RE: FW: URL escaping in Xalan-C                                               
                      08/12/2002 06:07                                                                                                
                      PM                                                                                                              
                                                                                                                                      
                                                                                                                                      






Dave,

Thank you very much for replying.
I have more  questions as stated below.  Do you prefer me to post it to the
user list  now?

-----Original Message-----
From: David N Bertoni [mailto:david_n_bertoni@us.ibm.com]
Sent:  Monday, August 12, 2002 5:51 PM
To: agan@siebel.com
Cc:  owessling
Subject: Re: FW: URL escaping in  Xalan-C




Hi  Ann,

The first thing is to subscribe to and post messages to the Xalan-C  user
list.  Sending directly to me is not the thing to do.

This  property can be surfaced at some point through a proprietary
attribute
on  xsl:output and/or through a programmatic interface.

What's the proprietary attribute you are  referring to here?

Thanks,

Ann


 If you have a
specific proposal, the best thing to do is post it  on the user list.  I
will look at how Xalan-J is handling this, and do  the same in the C++
processor.  I suspect they expose this through a  Xalan-specific extension
of xsl:output.

For the time being, I suggest  you simply hack the code and rebuild Xalan.
In that case, you could set the  property to default to false, or expose it
through the APIs, although it will  need to go through several  layers.

Dave



                       "Ann
Gan"                                                                                                      
                       <agan@siebel.             To:      David N
Bertoni/Cambridge/IBM@Lotus
                       com>                      cc:      "Owen Wessling"
<ow...@siebel.com>
                                                Subject: FW: URL escaping
in  Xalan-C
                       08/12/2002  04:
44                                                                                               

PM                                                                                                             




David,

I  am working at Siebel with Joseph Boyle.  I got his forwarded email
about
the following information.

I have more questions regarding this  issue and hope you can help me to
answer:
What version of Xalana are  exposing SpecialEscapeURLs property now?
What's the future plan for supporing  the exposure of SpecialEscapeURLs
property?
We have immediate need of  using this property.  Where can we express our
requirement
to  influence the future plan?

If you are not the right person for asking the  above questions, pls refer
me
to the right person.

Thanks in  advance,

Ann

-----Original Message-----
From: Joseph  Boyle
Sent: Tuesday, August 06, 2002 8:45 AM
To: Frank Yin; Manoj Das;  Michael Bishop; Chandu Bhavsar; Owen Wessling;
Ann Gan
Subject: FW: URL  escaping in Xalan-C


FYI

-----Original Message-----
From:  Joseph Boyle
Sent: Friday, August 02, 2002 3:05 PM
To:  'xalan-dev@xml.apache.org'
Subject: RE: URL escaping in  Xalan-C


Thanks for the quick answer.

It looks like Xalan-Java  version 1.2.D01 was exposing a SpecialEscapeURLs
property to control  this.


-----Original Message-----
From: David N  Bertoni/Cambridge/IBM [mailto:david_n_bertoni@us.ibm.com]
Sent:  Friday, August 02, 2002 2:23 PM
To: xalan-dev@xml.apache.org
Subject: RE:  URL escaping in Xalan-C






This sounds like something we  could expose and add as a proprietary
attribute on xsl:output at some point.

Currently, though, you're going to need to hack the code  yourself.

Dave





                       "Joseph  Boyle"

                       <Boyle@siebel.            To:
"'xalan-dev@xml.apache.org'"  <xa...@xml.apache.org>

                       com>                      cc:      (bcc: David
Bertoni/Cambridge/IBM)
                                                Subject: RE: URL escaping
in
Xalan-C
                       08/02/2002  12:59

                       PM

                       Please  respond

                       to xalan-dev








Unfortunately we have to support  wireless (mobile phone) browser software
which is not Unicode enabled, uses  only codepage, and sends non-ASCII in
URLs that it generates for form input  etc. as % hex escaped bytes
representing codepage not UTF-8. These would be  indistinguishable from %
hex
encoded bytes in the Xalan output, and we  would not know whether to decode
them from codepage or from UTF-8 at the  server side.

No browser I've encountered unconditionally implements the  IETF mandate to
always represent non-ASCII in URLs as hex escaped UTF-8. IE  does have an
option checkbox "Always send URLs as UTF-8", but other than  that, browsers
normally send non-ASCII in the encoding of the currently  displayed page
where the form or link occurs. Hex UTF-8 encoded URLs work  when we send
our
pages as UTF-8, but this is not possible in the cases where  the browser
has
no Unicode support.

Joseph

-----Original  Message-----
From: David N Bertoni/Cambridge/IBM [mailto:david_n_bertoni@us.ibm.com]
Sent:  Friday, August 02, 2002 11:47 AM
To: xalan-dev@xml.apache.org
Subject: Re:  URL escaping in Xalan-C






No, there's no interface to  do that.  This was in there for experimental
purposes, but the APIs to  modify it were never publically exposed.

Is there some reason why you  want to generate URLs which are not properly
escaped?  I don't see it as  behavior we support in the normal release, but
you could always modify the  sources yourself to do what you  want.

Dave





                       "Joseph  Boyle"

                       <Boyle@siebel.            To:
"'xalan-dev@xml.apache.org'"  <xa...@xml.apache.org>

                       com>                      cc:      (bcc: David
Bertoni/Cambridge/IBM)
                                                Subject: URL escaping  in
Xalan-C
                       08/02/2002  10:24

                       AM

                       Please  respond

                       to xalan-dev








Is there a way to turn off  escaping of URLs in output as hex encoded UTF-
8?
I can see setting  m_escapeURLs in FormatterToHTML.cpp to false would do
this, but m_escapeURLs  is initialized to true and I do not see an
interface
to change it. Thanks,  Joseph