I completely agree with this. So I¹ve updated the editors and configuration managers that store xml content to use the UTF-8 character encoding. I did notice that there are a few spots in the runtime components that are using UTF-16 for their documents. Is there any particular benefits to using one or the other? I¹d like to consolidate things to use a single encoding.
Trip On 7/1/08 9:24 AM, "Luís Almeida" <[EMAIL PROTECTED]> wrote: > Hi, > > Some european languages like portuguese, spanish, etc contain characters that > are not us ascii. This highly constrains the use of static text prompts so it > would very important to introduce some changes in order to support different > encodings in the generated XML files i.e. what are classes should be modified > to change XML declaration <?xml version="1.0" ?> to <?xml version="1.0" > encoding="UTF-8"?> in the generated VoiceXML and project (CallDesign.xml) > > Thanks in advance, > > Best regards, > Luís Miguel Almeida > *********************************** > PT Inovação S.A. > Multimedia Networks Division > > Rua Tenente Valadim 431 - 7º Piso > > 4100-479 Porto - PORTUGAL > > *************************** > > URL: www.ptinovacao.pt > <file:///C:/Documents%20and%20Settings/lalmeida/Application%20Data/Microsoft/S > ignatures/www.ptinovacao.pt> > > Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > Phone: +351 22 605 68 18 > > Fax: +351 22 605 68 10 > > > > > _______________________________________________ > vtp-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/vtp-dev
_______________________________________________ vtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/vtp-dev
