RE: XSLT 2.0: xsl:output: character representation control attribute

Thank you for clarifying this.
 
To confirm, with XSLT 2.0, I will not have to use any processor-specific extension, such as 'saxon:character-representation="native"' (with a standards-compliant processor) in order to output 'native' characters.  However, should I desire to output with a different character representation (though I can't think of a specific purpose), I would use the processor-specific extension where available? I think my confusion was in expecting a character-representation attribute in the new XSLT 2.0 specification, rather than a change in the (default) behaviour of a XSLT 2.0 standard-compliant processor.
 
Deborah

 -----Original Message----- 
 From: Michael Kay [mailto:mhk@mhk.me.uk] 
 Sent: Wed 18/02/2004 17:45 
 To: Deborah Cawkwell; public-qt-comments@w3.org 
 Cc: jirka@kosek.cz 
 Subject: RE: XSLT 2.0: xsl:output: character representation control attribute
 
 

 You appear to be quoting a message that is two years old, I wonder if 
 you have checked the situation in the current specs? 

 This is now covered by section 6.4 of the serialization spec 

 http://www.w3.org/TR/xslt-xquery-serialization 

 which states: 

 Entity references and character references should be used only where the 
 character is not present in the selected encoding, or where the visual 
 representation of the character is unclear (as with  , for 
 example). 

 I suspect this sentence was added in response to the original comment in 
 2002. 

 Could you confirm whether this meets your requirement, or do you still 
 have a problem? 

 Michael Kay 


 > -----Original Message----- 
 > From: public-qt-comments-request@w3.org 
 > [mailto:public-qt-comments-request@w3.org] On Behalf Of 
 > Deborah Cawkwell 
 > Sent: 18 February 2004 15:41 
 > To: public-qt-comments@w3.org 
 > Cc: jirka@kosek.cz 
 > Subject: XSLT 2.0: xsl:output: character representation 
 > control attribute 
 > 
 > 
 > I support Jirka Kosek's requirement for an 'xsl:output' 
 > attribute with the same functionality as 
 > 'saxon:character-representation="native"' for the same reasons, ie: 
 > 
 > - page weight 
 > 
 > - ability to edit generated page. 
 > 
 > Additionally: 
 > 
 > - to use XSLT without extensions specific to a particular 
 > processor (although I think Saxon is great). 
 > 
 > Thanks 
 > 
 > Deborah 
 > 
 > From: Kay, Michael <Michael.Kay@softwareag.com 
 > <mailto:Michael.Kay@softwareag.com?Subject=RE:%20Better%20cont 
 > rol%20over%20character%20encoding%20in%20HTML%20%20output%20me 
 > thod&In-Reply-To=<DFF2AC9E3583D511A21F0008C7E6210602679C03@dae 
 msg02.software-ag.de>&References=> 
 <DFF2AC9E3583D511A21F0008C7E6210602679C03@daemsg02.software-ag.de>> > 
 > Date: Fri, 1 Feb 2002 21:01:04 +0100 
 > Message-ID: 
 > <DFF2AC9E3583D511A21F0008C7E6210602679C03@daemsg02.software-ag.de> 
 > To: "'Jirka Kosek'" <jirka@kosek.cz 
 > <mailto:jirka@kosek.cz?Subject=RE:%20Better%20control%20over%2 
 > 0character%20encoding%20in%20HTML%20%20output%20method&In-Repl 
 > y-To=<DFF2AC9E3583D511A21F0008C7E6210602679C03@daemsg02.softwa 
 > re-ag.de>&References=<DFF2AC9E3583D511A21F0008C7E6210602679C03 
 > @daemsg02.software-ag.de>> >, xsl-editors@w3.org 
 > <mailto:xsl-editors@w3.org?Subject=RE:%20Better%20control%20ov 
 > er%20character%20encoding%20in%20HTML%20%20output%20method&In- 
 > Reply-To=<DFF2AC9E3583D511A21F0008C7E6210602679C03@daemsg02.so 
 > ftware-ag.de>&References=<DFF2AC9E3583D511A21F0008C7E621060267 
 > 9C03@daemsg02.software-ag.de>>  
 > 
 > Thanks for this comment. I'll put a proposal to the WG for discussion. 
 > 
 > Mike Kay 
 > 
 > > -----Original Message----- 
 > > From: Jirka Kosek [mailto:jirka@kosek.cz 
 > > 
 > <mailto:jirka@kosek.cz?Subject=RE:%20Better%20control%20over%2 
 > 0character%20encoding%20in%20HTML%20%20output%20method&In-Repl 
 > y-To=<DFF2AC9E3583D511A21F0008C7E6210602679C03@daemsg02.softwa 
 > re-ag.de>&References=<DFF2AC9E3583D511A21F0008C7E6210602679C03 
 > @daemsg02.software-ag.de>> ] 
 > > Sent: 01 February 2002 18:52 
 > > To: xsl-editors@w3.org 
 > <mailto:xsl-editors@w3.org?Subject=RE:%20Better%20control%20ov 
 > er%20character%20encoding%20in%20HTML%20%20output%20method&In- 
 > Reply-To=<DFF2AC9E3583D511A21F0008C7E6210602679C03@daemsg02.so 
 > ftware-ag.de>&References=<DFF2AC9E3583D511A21F0008C7E621060267 
 > 9C03@daemsg02.software-ag.de>> 
 > > Subject: Better control over character encoding in HTML 
 > output method 
 > > 
 > > 
 > > Hi, 
 > > 
 > > when reading through XSLT 2.0 WD I found that one aspect of 
 > > HTML output 
 > > method is not precisely defined and can cause problems for 
 > users using 
 > > Central European languages. 
 > > 
 > > Citation from section 18.3: 
 > > 
 > > The html output method may output a character using a 
 > character entity 
 > > reference, if one is defined for it in the version of HTML that the 
 > > output method is using. 
 > > 
 > > Thit means, that XSLT procesor will output e.g. &eacute; or &xe9; 
 > > instead of é. This might be acceptable for Western European 
 > languages 
 > > where are accented characters quite rare. But for example in Czech 
 > > accented characters are 10-20 % of all characters used. 
 > Using entities 
 > > means that you will get larger HTML files which are hard to edit by 
 > > hand (if someone other wants to edit them). 
 > > 
 > > For this case I will welcome <xsl:output> attribute with same 
 > > functionality like saxon:character-representation="native" -- i.e. 
 > > attribute which forces output method to use native 
 > characters instead 
 > > of entity references where possible. This feature is really 
 > necessary 
 > > for us in CE -- I must use 
 > > saxon:character-representation="native" in all my 
 > > XSLTs. 
 > > 
 > > Thanks. 
 > >     
 > >                     Jirka Kosek 
 > > 
 > > -- 
 > > ----------------------------------------------------------------- 
 > >   Jirka Kosek                            
 > >   e-mail: jirka@kosek.cz 
 > <mailto:jirka@kosek.cz?Subject=RE:%20Better%20control%20over%2 
 0character%20encoding%20in%20HTML%20%20output%20method&In-Reply-To=<DFF2 
 AC9E3583D511A21F0008C7E6210602679C03@daemsg02.software-ag.de>&References 
 =<DFF2AC9E3583D511A21F0008C7E6210602679C03@daemsg02.software-ag.de>> 
 >   http://www.kosek.cz 
 > 
 > 
 Received on Friday, 1 February 2002 15:01:10 EST 

 *       This message: [ Message body ] 
 *       Next message: Jeni Tennison: "Re: [xsl] Passing sort criteria as 
 a paramter" 
 *       Previous message: Kay, Michael: "RE: Comments for XSLT 2.0 WD" 
 *       Maybe in reply to: Jirka Kosek: "Better control over character 
 encoding in HTML output method" 

 *       Mail actions: [ respond to this message 
 <mailto:xsl-editors@w3.org?Subject=RE:%20Better%20control%20over%20chara 
 cter%20encoding%20in%20HTML%20%20output%20method&In-Reply-To=<DFF2AC9E35 
 83D511A21F0008C7E6210602679C03@daemsg02.software-ag.de>&References=<DFF2 
 AC9E3583D511A21F0008C7E6210602679C03@daemsg02.software-ag.de>>  ] [ mail 
 a new topic <mailto:xsl-editors@w3.org>  ] 
 *       Contemporary messages sorted: [ by date ] [ by thread ] [ by 
 subject ] [ by author ] [ by messages with attachments ] 
 *       Help: [ How to use the archives <http://lists.w3.org/Help/>  ] [ 
 Search in the archives <http://www.w3.org/Search/Mail/Public/>  ] 

 This archive was generated by hypermail pre-2.1.9 
 <http://www.hypermail.org/>  : Wednesday, 24 September 2003 14:06:20 EDT 



 BBCi at http://www.bbc.co.uk/ 

 This e-mail (and any attachments) is confidential and may contain 
 personal views which are not the views of the BBC unless specifically 
 stated. If you have received it in error, please delete it from your 
 system. 
 Do not use, copy or disclose the information in any way nor act in 
 reliance on it and notify the sender immediately. Please note that the 
 BBC monitors e-mails sent or received. 
 Further communication will signify your consent to this. 


BBCi at http://www.bbc.co.uk/


This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless specifically
stated.
If you have received it in error, please delete it from your system. 
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately. Please note that the
BBC monitors e-mails sent or received. 
Further communication will signify your consent to this.

Received on Monday, 23 February 2004 10:39:05 UTC