=?iso-8859-1?Q?Re:_=28PS=29_Im=E1genes_de_Rango_din=E1mico_HDR_-3?=

This is a multi-part message in MIME format.
------=_NextPart_000_004C_01C816E0.3950EF70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sin =E1nimo de ofender pero creo que Juan deber=EDas
sustituir a Andres =
Cayon en cuanto al coordinador de Macromedia.. colabora menos
que tu, no =
tiene pedazo art=EDculos como estos.
"Juan Muro" <[email protected]> escribi=F3 en el
mensaje =
news:[email protected]...
---> viene del anterior
Pues bien, ya estamos listos para hacer nuestra primera
im=E1gen HDR, =
tenemos la c=E1mara, el tr=EDpode y el disparador
autom=E1tico y =
adem=E1s ya sabemos c=F3mo ajustamos el diafragma de manera
manual, o =
bien hemos comprobado que nuestra c=E1mara dispone del
maravilloso =
mecanismo de disparo bracketing, (y si esto es cierto quiero
aclarar =
que debemos probar las diferentes aperturas del diafragma
antes de =
disparar en bracketing, pues este modo de disparo
autom=E1tico no ajusta =
la velocidad de obturaci=F3n respecto a la apertura del
diafragma y por =
=E9so nos puede variar la profundidad de campo de tal manera
que nos =
encontramos con zonas m=E1s borrosas que otras dependiendo de
su =
distancia al objetivo, lo cual debemos evitar pues las fotos
que =
obtengamos para componer luego la im=E1gen HDR deben ser
absolutamente =
iguales salvo en la luz).
Pero claro si nos hace falta un tr=EDpode y al menos dos o
tres fotos, =
nunca podremos conseguir una foto HDR en movimiento. Pues no,
no es =
cierto, podemos hacerla, pero simul=E1ndo el HDR a partir de
una buena =
captura RAW, como dije en el primer mensaje, =E9so veremos
despu=E9s =
c=F3mo se hace.
De momento lo importante es conseguir las tomas que
comprondr=E1n =
nuestra imagen final. Lo primero ser=E1 ajustar la
sensibilidad ISO de =
la pel=EDcula a la menor posible (a la que corresponda,
habitualmente a =
21 DIN -- 100 ISO para exteriores normalmente iluminados),
as=ED =
evitaremos el ruido =F3ptico. Lo segundo es ensayar el
m=E9todo de =
apertura del diafragma sin que se nos mueva ni un =E1pice la
c=E1mara. Y =
lo tercero es hacer las fotos, cuantas m=E1s mejor, con un
m=EDnimo de =
dos fotos podemos obtener ya un hdr, pero lo normal es
hacerlo con tres, =
aunque yo he llegado a hacer hasta siete tomas diferentes de
la misma =
im=E1gen.
En estas tomas no tenemos la necesidad de valorar el
contraluz, ni por =
tanto la posici=F3n del sol respecto de la c=E1mara, ni si
alg=FAnas =
partes de la im=E1gen quedar=E1n solarizadas, ni siquiera si
existe =
alg=FAn objeto entre el foco luminoso y el objetivo, porque
todos estos =
obst=E1culos habituales quedar=E1n superados con esta
t=E9cnica.
Pero s=ED debemos valorar el tiempo de exposici=F3n, o lo
que es lo =
mismo la velocidad de obturaci=F3n del diafragma, porque de
ella depende =
en gran medida la cantidad de luz que recibe nuestra im=E1gen
y la =
definici=F3n de las texturas que contiene.
Luego guardaremos las im=E1genes en formato Tiff o Psd y las
=
volcaremos a nuestra computadora, donde las podemos renombrar
(aunque no =
es estrictamente necesario, pero ayuda para organizarse).
Lo dem=E1s ser=E1 todo hecho con nuestro viejo conocido
Photoshop, =
aunque solo admiten esta t=E9cnica las versiones CS2 y CS3, =
b=E1sicamente porque antes no se hab=EDa inventado, je, je.
---> contin=FAa
------=_NextPart_000_004C_01C816E0.3950EF70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3199"
name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Sin =E1nimo de
ofender pero creo que =
Juan deber=EDas=20
sustituir a Andres Cayon en cuanto al coordinador de
Macromedia.. =
colabora menos=20
que tu, no tiene pedazo art=EDculos como
estos.</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT:
5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Juan Muro" <<A=20
href=3D"mailto:[email protected]">[email protected]</A>>
=
escribi=F3 en el=20
mensaje <A=20
=
href=3D"news:[email protected]">news:fff5hs$se2$1@forums=
.macromedia.com</A>...</DIV>
<DIV><FONT face=3DArial
size=3D2><EM>---> viene del =
anterior</EM></FONT></DIV>
<DIV><EM><FONT face=3DArial
size=3D2></FONT></EM> </DIV>
<DIV><FONT face=3DArial size=3D2>Pues bien, ya
estamos listos para =
hacer nuestra=20
primera im=E1gen HDR, tenemos la c=E1mara, el tr=EDpode y el
=
disparador autom=E1tico y=20
adem=E1s ya sabemos c=F3mo ajustamos el diafragma de manera
manual, o =
bien hemos=20
comprobado que nuestra c=E1mara dispone del maravilloso
mecanismo de =
disparo<EM>=20
bracketing, </EM>(y si esto es cierto quiero
aclarar que debemos =
probar=20
las diferentes aperturas del diafragma antes de disparar en
=
bracketing, pues=20
este modo de disparo autom=E1tico no ajusta la velocidad de
=
obturaci=F3n respecto=20
a la apertura del diafragma y por =E9so nos puede variar la
=
profundidad de campo=20
de tal manera que nos encontramos con zonas m=E1s borrosas
que otras =
dependiendo=20
de su distancia al objetivo, lo cual debemos evitar pues las
fotos que =
obtengamos para componer luego la im=E1gen HDR deben ser
absolutamente =
iguales=20
salvo en la luz).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Pero claro si
nos hace falta un =
tr=EDpode y al=20
menos dos o tres fotos, nunca podremos conseguir una foto
HDR en =
movimiento.=20
Pues no, no es cierto, podemos hacerla, pero simul=E1ndo el
HDR a =
partir de=20
una buena captura RAW, como dije en el primer
mensaje, =E9so =
veremos =20
despu=E9s c=F3mo se hace.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>De momento lo
importante es conseguir =
las tomas=20
que comprondr=E1n nuestra imagen final. Lo primero ser=E1 =
ajustar la=20
sensibilidad ISO de la pel=EDcula a la menor
posible (a la que=20
corresponda, habitualmente a 21 DIN -- 100 ISO para
exteriores =
normalmente=20
iluminados), as=ED evitaremos el ruido =F3ptico. Lo segundo
es ensayar =
el m=E9todo=20
de apertura del diafragma sin que se nos mueva ni un =E1pice
la =
c=E1mara. Y lo=20
tercero es hacer las fotos, cuantas m=E1s mejor, con un
m=EDnimo de =
dos fotos=20
podemos obtener ya un hdr, pero lo normal es hacerlo con
tres, aunque =
yo he=20
llegado a hacer hasta siete tomas diferentes de la misma =
im=E1gen.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>En estas tomas
no tenemos la =
necesidad de valorar=20
el contraluz, ni por tanto la posici=F3n del sol respecto de
la =
c=E1mara, ni si=20
alg=FAnas partes de la im=E1gen quedar=E1n solarizadas, ni
siquiera si =
existe alg=FAn=20
objeto entre el foco luminoso y el objetivo, porque todos
estos =
obst=E1culos=20
habituales quedar=E1n superados con esta
t=E9cnica.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Pero s=ED
debemos valorar el tiempo =
de exposici=F3n,=20
o lo que es lo mismo la velocidad de obturaci=F3n del
diafragma, =
porque de ella=20
depende en gran medida la cantidad de luz que recibe nuestra
im=E1gen =
y la=20
definici=F3n de las texturas que
contiene.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Luego
guardaremos las im=E1genes en =
formato Tiff o=20
Psd y las volcaremos a nuestra computadora, donde las
podemos =
renombrar=20
(aunque no es estrictamente necesario, pero ayuda para=20
organizarse).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Lo dem=E1s
ser=E1 todo hecho con =
nuestro viejo=20
conocido Photoshop, aunque solo admiten esta t=E9cnica las
versiones =
CS2 y CS3,=20
b=E1sicamente porque antes no se hab=EDa inventado, je, =
je.</FONT></DIV>
<DIV align=3Dright><FONT face=3DArial
size=3D2><EM>--->=20
contin=FAa</EM></FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2></FONT> </DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_004C_01C816E0.3950EF70--

maybe OP want to extract all numbers from his inbox using regular expressions?

Similar Messages

Como deixar a codificação padrão "iso-8859-1" ao invés de "utf-8" no navegador?

Quando faço o acesso ao banco do meu cartão de crédito, a primeira pagina deles é codificada com "UTF-8" e também existe o comando "charset=utf-8" no código HTML, após digitar o número do cartão, ele direciona para outra página, porém codificada com "iso-8859-1", mas sem nenhuma codificação no código HTML.
Identifiquei que o navegador usa por padrão o "utf-8" quando não existe codificação no código HTML, então gostaria de modificar esse padrão para "iso-8859-1".
O único lugar que encontrei para essa codificação foi ao pressionar o botão de avançado em "Fontes e cores", porém não funcionou.
A versão do meu navegado é 23.0.1, entretanto desde a versão 18 que encontro esse problema.

It is possible that the server sends the file(s) by default with UTF-8 and in such a case this encoding send by the server prevails over all other settings.
You can see the encoding here: Tools > Page Info > General
*Press the F10 key or tap the Alt key to bring up the hidden "Menu Bar" temporarily.

Unable to load database, locales [Arabic_SaudiArabia.ISO-8859-6@Default]

When trying to load data into Essbase I get this error dialogue
Object [65313270] is locked by user [admin@Native Directory]
Unable to load database, locales [Arabic_SaudiArabia.ISO-8859-6@Default] and [English_UnitedStates.Latin1@Binary] are not compatible
Object [65313270] unlocked by user [admin@Native Directory]
Unexpected Essbase error 1019057
Have checked essbase.properties files (all 10 of them!) and the 2 references that I could find both point to the default value of [English_UnitedStates.Latin1@Binary]
So is the problem with the CSV file?

Have you looked at the Load Rule (yes, I know, developed in Studio, but it generates Load Rules which I believe you can open in EAS)? Is the dimension that contains BON accounted for?
Your second issue(s) seems to be that you have conflicting locales -- are you in SA? Could it be that Studio is installed with English as the language and EAS with Arabic (or vice versa)? Sorry, I have hardly any experience in languages other than English. Maybe one of the non-English language posters can chime in.
I can't say whether that load buffer issue means anything at all or not -- it could be a red herring.
Regards,
Cameron Lackpour

UTF-8 encoding vs ISO 8859-1 encoding

The iTunes tech specs call for UTF-8 encoding of the XML feed file; a friend of mine uses feed generator software through his blog that uses ISO 8859 encoding. Is there a way to convert the latter to UTF-8 so that iTunes tags may be successfully added?
When I tried editing his XML file, I got error messages when I submitted the file to RSS feed validator sites (such as http://feedvalidator.org/. Any help or knowledge is appreciated because I am not the least bit expert in this coding arena.

You don't need to convert iso 8859-1 (us-ascii) to utf-8 unless you have nonstandard characters. Basically, ascii is a subset of utf-8 and for English it will serve you just fine. You can have iTunes tags in the xml file even if the file itself is encoded in iso 8859-1.
The error you see at feedvalidator.org is most likely a warning.
Hope this helps!
- Andy Kim
Potion Factory
http://www.potionfactory.com

Mail Receiver - Send file in ISO-8859-1 encoding

Hi,
I'm sending mail with an attachment using mail adapter, but instead of specified ISO-8859-1 it is converted to UTF-8 no BOM,. Because of that, some characters (ñ,ç, etc) are not transferred properly.
Settings:
Message protocol: XIPAYLOAD
No mail package.
Transform.ContentType: multipart/mixed; boundary=--AaZz; charset=ISO-8859-1
Payload:
multipart/mixed; boundary=AaZz; charset=ISO-8859-1</Content_Type><Content>--AaZz
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
File attachment
AaZz
Content-Type: text/plain; charset= ISO-8859-1
Content-Disposition: attachment; filename=TestFile
iso-8859 characters ñ ç ñ ñ
AaZz--
</Content></ns:Mail>
I need advice in how to force the file to be created with ISO-8859-1 enconding.
Thanks in advance.
Regards,
Iván.

Hi Jean-Philippe,
Yes, please check my first post, if you use same settings, and create message as mine, it should work, the TestFile is created as an attachment.
Include this line in the module configuration with transform key:
Transform.ContentType: multipart/mixed; boundary=--AaZz;
If you still have issues, please give me a description of the error.
Regards,
Ivan.

Codepage coverting error utf-8 from System codepage to iso-8859-1 (PI 7.1)

Hello Experts,
In our Prcess, we receive an Idoc from an IS-U system and then we send this Idoc with some Header-Information via http-Adapter to a Seeburger System.
In the outbound communication Channel we have a XI Payload manipulation with xml-Code iso-8859-1.
We get the Error: Codepage coverting error utf-8 from System codepage to iso-8859-1, and only for this Idoc, where othe similar Idocs runs correctly.
Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
PS: another XI in our landscape uses a http-Channel with the same configuration in a similar process, an it work, so guess the Problem is not in the communication channel.
thanks,
best regards

> Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
A would rather think, that there could be any non-iso-8859-1 character be in the IDoc. For example an czech or polish character.

HTTP adapter - change encoding from UTF-8 to ISO-8859-1

Hi,
I am trying to change the encoding used by the HTTP sender adapter in a scenario.
However, when I enter ISO-8859-1 in the XML Code under XI Payload Manipulation on the comms channel it has no effect - the paylad still shows as UTF-8 in SXI_MONITOR.
Am I missing a step or entering the field incorrectly ??
Thanks
Colin.

Hi,
From help
Enhancing the Payload
Some external systems, for example, Web servers in marketplaces, can only process data if it is sent as an HTML form using HTTP.
A typical HTML form comprises named fields. When transferring a completed form to the server or a CGI program, the data must be transferred in such a way that the CGI script can recognize the fields that make up the form, and which data was entered in which field.
The plain HTTP adapter constructs this format using a prolog and an epilog. Therefore, there is a particular code method that separates form fields and their data from each other. This code method uses the following rules:
     Individual form elements, including their data, are separated from each other by the character &.
     The name and data of a form element are separated from each other by an equals sign (=).
     Blanks in the entered data (for example, in multiple words) are replaced by a plus sign (+).
    All characters with the (enhanced) ASCII values 128 to 255 (hexadecimal 80 to FF) are transcribed using a hexadecimal sequence, beginning with a percentage sign (%) followed by the hexadecimal value of the character (for example, the German umlaut ö in the character set ISO-8859-1 is transcribed as %F6).
   All characters that occur in these rules as control characters (&, +, =, and %) are also transcribed hexadecimally in the same way as high value ASCII characters
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
Regards
Chilla

File adapter ISO-8859-1 encoding problems in XI 3.0

We are using the XI 3.0 file adapter and are experiencing some XML encoding troubles.
A SAP R/3 system is delivering an IDoc outbound. XI picks up the IDoc and converts it to an external defined .xml file. The .xml file is send to a connected ftp-server. At the remote FTP server the file is generating an error, as it is expected to arrive in ISO-8859-1 encoding. The Transfer Mode is set to Binary, File Type Text, and Encoding ISO-8859-1.
The .xml file is encoded correctly in ISO-8859-1, but the problem is that the XML encoding declaration has the wrong value 'UTF-8'.
Does anybody know of a work around, to change the encoding declaration to ISO-8859-1 in the message mapping program?

An example of the XSL code might be as follow:
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method='xml' encoding='ISO-8859-1' />
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>

Converting from CP1252 (Windows) to ISO 8859-1 doesn't work with java.nio?

Hi
I'm trying to write some code that checks whether an InputStream contains only characters with a given encoding. I'm using java.nio for that. For tests, I downloaded some character set examples from http://www.columbia.edu/kermit/csettables.html
When creating the CharsetDecoder, I want to get all errors:
    Charset charset = Charset.forName( encoding );
    CharsetDecoder decoder = charset.newDecoder();
    decoder.onMalformedInput( CodingErrorAction.REPORT );
    decoder.onUnmappableCharacter( CodingErrorAction.REPORT );I then read an InputStream and try to convert it. If that fails, it can't contain the desired encoding:
    boolean isWellEncoded = true;
    ByteBuffer inBuffer = ByteBuffer.allocate( 1024 );
    ReadableByteChannel channel = Channels.newChannel( inputStream );
    while ( channel.read( inBuffer ) != -1 )
      CharBuffer decoded = null;
      try
        inBuffer.flip();
        decoded = decoder.decode( inBuffer );
      catch ( MalformedInputException ex )
        isWellEncoded = false;
      catch ( UnmappableCharacterException ex )
        isWellEncoded = false;
      catch ( CharacterCodingException ex )
        isWellEncoded = false;
      if ( decoded != null )
        LOG.debug( decoded.toString() );
      if ( !isWellEncoded )
        break;
      inBuffer.compact();
    channel.close();
    return isWellEncoded;Now I want to check whether a file containing Windows 1252 characters is ISO-8859-1. From my point of view, the code above should fail when it gets to the Euro symbol (decimal 128), since that's not defined in ISO-8859-1.
But all I get is a ? character instead:
(}) 125 07/13 175 7D                 RIGHT CURLY BRACKET, RIGHT BRACE
(~) 126 07/14 176 7E                 TILDE
[?] 128 08/00 200 80 EURO SYMBOL
[?] 130 08/02 202 82 LOW 9 SINGLE QUOTEI also tried to replace the faulty character, using
    decoder.onUnmappableCharacter( CodingErrorAction.REPLACE );
    decoder.replaceWith("!");but I still get the question marks.
I'm probably doing something fundamentally wrong, but I dont get it :-)
Any help is greatly appreciated!
Eric

As a suggestion....create a complete example demonstrating the problem. It shouldn't have channel in it since that wouldn't appear to be the problem (decoding is.) You should create the byte array in the example code - populate it with the byte sequence that you think should work. And your code should then demonstrate that it doesn't. Then post that.

Xslt ecc6 ISO-8859-1 problem when download xml file

Hello,
i create an ABAP test program:
*& Report Z_ABAP_TO_XML                                             *
*& Write the data from an internal ABAP table into an XML document, *
*& and write it onto your frontend computer                         *
REPORT z_abap_to_xml.
TYPE-POOLS: abap.
CONSTANTS gs_file TYPE string VALUE 'C:\Users\Marco Consultant\Desktop\test.xml'.
* This is the structure for the data to go into the XML file
TYPES: BEGIN OF ts_person,
cust_id(4)    TYPE n,
firstname(20) TYPE c,
lastname(20) TYPE c,
END OF ts_person.
* Table for the XML content
DATA: gt_itab        TYPE STANDARD TABLE OF char2048.
* Table and work area for the data to fill the XML file with
DATA: gt_person      TYPE STANDARD TABLE OF ts_person,
      gs_person      TYPE ts_person.
* Source table that contains references
* of the internal tables that go into the XML file
DATA: gt_source_itab TYPE abap_trans_srcbind_tab,
      gs_source_wa   TYPE abap_trans_resbind.
* For error handling
DATA: gs_rif_ex      TYPE REF TO cx_root,
      gs_var_text    TYPE string.
* Fill the internal table
gs_person-cust_id   = '3'.
gs_person-firstname = 'Bill'.
gs_person-lastname = 'Gates'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '4'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
* Fill the source table with a reference to the data table.
* Within the XSLT stylesheet, the data table can be accessed with
* "IPERSON".
GET REFERENCE OF gt_person INTO gs_source_wa-value.
gs_source_wa-name = 'IPERSON'.
APPEND gs_source_wa TO gt_source_itab.
* Perform the XSLT stylesheet
TRY.
    CALL TRANSFORMATION z_abap_to_xml
    SOURCE (gt_source_itab)
    RESULT XML gt_itab.
CATCH cx_root INTO gs_rif_ex.
    gs_var_text = gs_rif_ex->get_text( ).
    gs_var_text = gs_rif_ex->get_text( ).
    MESSAGE gs_var_text TYPE 'E'.
ENDTRY.
* Download the XML file to your client
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
    filename                = gs_file
CHANGING
    data_tab                = gt_itab
EXCEPTIONS
    file_write_error        = 1
    no_batch                = 2
    gui_refuse_filetransfer = 3
    invalid_type            = 4
    no_authority            = 5
    unknown_error           = 6
    header_not_allowed      = 7
    separator_not_allowed   = 8
    filesize_not_allowed    = 9
    header_too_long         = 10
    dp_error_create         = 11
    dp_error_send           = 12
    dp_error_write          = 13
    unknown_dp_error        = 14
    access_denied           = 15
    dp_out_of_memory        = 16
    disk_full               = 17
    dp_timeout              = 18
    file_not_found          = 19
    dataprovider_exception = 20
    control_flush_error     = 21
    not_supported_by_gui    = 22
    error_no_gui            = 23
    OTHERS                  = 24.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
and i created XSLT test conversion:
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output encoding="iso-8859-1" indent="yes" method="xml" version="1.0"/>
<xsl:strip-space elements="*"/>
<xsl:template match="/">
    <CUSTOMERS>
      <xsl:apply-templates select="//IPERSON/item"/>
    </CUSTOMERS>
</xsl:template>
<xsl:template match="IPERSON/item">
    <item>
      <customer_id>
        <xsl:value-of select="CUST_ID"/>
      </customer_id>
      <first_name>
        <xsl:value-of select="FIRSTNAME"/>
      </first_name>
      <last_name>
        <xsl:value-of select="LASTNAME"/>
      </last_name>
    </item>
</xsl:template>
</xsl:transform>
Seem all correct infact the program download a file XML but the file have the encoding="UTF-16" also if i have specified "iso-8859-1" and if i tried to opend the xml file the file appears not correct because is generated with as first character "#", why?
Below the xml generated..
What i have to do to generate a correct XML without errors?
#<?xml version="1.0" encoding="utf-16"?>
<CUSTOMERS>
<item>
    <customer_id>0003</customer_id>
    <first_name>Bill</first_name>
    <last_name>Gates</last_name>
</item>
<item>
    <customer_id>0004</customer_id>
    <first_name>Frodo</first_name>
    <last_name>Baggins</last_name>
</item>
</CUSTOMERS>

hello all!
i resolve the problem using:
* Perform the XSLT stylesheet
g_ixml = cl_ixml=>create( ).
g_stream_factory = g_ixml->CREATE_STREAM_FACTORY( ).
g_encoding = g_ixml->create_encoding( character_set = 'utf-16' "unicode
    byte_order = 0 ).
resstream = g_stream_factory->CREATE_OSTREAM_ITABLE( table = gt_xml_itab ).
call method resstream->set_encoding
    exporting encoding = g_encoding.
I think it's the right way, i put all my ABAP program updated:
*& Report Z_ABAP_TO_XML                                             *
*& Write the data from an internal ABAP table into an XML document, *
*& and write it onto your frontend computer                         *
REPORT z_abap_to_xml.
TYPE-POOLS: abap.
CONSTANTS gs_file TYPE string VALUE 'C:UsersMarco ConsultantDesktop     est.xml'.
data: g_ixml type ref to if_ixml.
data: g_stream_factory type ref to IF_IXML_STREAM_FACTORY.
data: resstream type ref to if_ixml_ostream.
data: g_encoding type ref to if_ixml_encoding.
* This is the structure for the data to go into the XML file
TYPES: BEGIN OF ts_person,
cust_id(4)    TYPE n,
firstname(20) TYPE c,
lastname(20) TYPE c,
END OF ts_person.
* Table for the XML content
DATA: gt_xml_itab        TYPE STANDARD TABLE OF char2048.
* Table and work area for the data to fill the XML file with
DATA: gt_person      TYPE STANDARD TABLE OF ts_person,
      gs_person      TYPE ts_person.
* Source table that contains references
* of the internal tables that go into the XML file
DATA: gt_source_itab TYPE abap_trans_srcbind_tab,
      gs_source_wa   TYPE abap_trans_resbind.
* For error handling
DATA: gs_rif_ex      TYPE REF TO cx_root,
      gs_var_text    TYPE string.
* Fill the internal table
gs_person-cust_id   = '3'.
gs_person-firstname = 'Bill'.
gs_person-lastname = 'Gates'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '4'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '5'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '6'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '7'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '8'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '9'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '10'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id   = '88'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
* Fill the source table with a reference to the data table.
* Within the XSLT stylesheet, the data table can be accessed with
* "IPERSON".
GET REFERENCE OF gt_person INTO gs_source_wa-value.
gs_source_wa-name = 'IPERSON'.
APPEND gs_source_wa TO gt_source_itab.
* Perform the XSLT stylesheet
g_ixml = cl_ixml=>create( ).
g_stream_factory = g_ixml->CREATE_STREAM_FACTORY( ).
g_encoding = g_ixml->create_encoding( character_set = 'utf-16' "unicode
    byte_order = 0 ).
resstream = g_stream_factory->CREATE_OSTREAM_ITABLE( table = gt_xml_itab ).
call method resstream->set_encoding
    exporting encoding = g_encoding.
TRY.
    CALL TRANSFORMATION z_abap_to_xml
    SOURCE (gt_source_itab)
    RESULT XML gt_xml_itab.
CATCH cx_root INTO gs_rif_ex.
    gs_var_text = gs_rif_ex->get_text( ).
    gs_var_text = gs_rif_ex->get_text( ).
    MESSAGE gs_var_text TYPE 'E'.
ENDTRY.
* Download the XML file to your client
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
    filename                = gs_file
    FILETYPE                  = 'BIN'
CHANGING
    data_tab                = gt_xml_itab
EXCEPTIONS
    file_write_error        = 1
    no_batch                = 2
    gui_refuse_filetransfer = 3
    invalid_type            = 4
    no_authority            = 5
    unknown_error           = 6
    header_not_allowed      = 7
    separator_not_allowed   = 8
    filesize_not_allowed    = 9
    header_too_long         = 10
    dp_error_create         = 11
    dp_error_send           = 12
    dp_error_write          = 13
    unknown_dp_error        = 14
    access_denied           = 15
    dp_out_of_memory        = 16
    disk_full               = 17
    dp_timeout              = 18
    file_not_found          = 19
    dataprovider_exception = 20
    control_flush_error     = 21
    not_supported_by_gui    = 22
    error_no_gui            = 23
    OTHERS                  = 24.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
*-- we don't need the stream any more, so let's close it...
CALL METHOD resstream->CLOSE( ).
CLEAR resstream.

Translation UTF8 - ISO-8859-1

Hi there,
When translating a UTF8 file to ISO-8859-1 during loading of that file (using dbms_lob.loadclobfromfile)
I notice that an UTF8 right single quotation mark ' (2019) is converted to an inverted quotation mark ¿.
The left single quotation mark is (correctly) translated to 0060 Grave accent `
My question is; how can I get the (2019) right single quatation mark to be converted to 00B4 Acute Accent ?
Thanks in advance,
Art

It looks like during the insertion from ASP the Latin 1 string has not been converted to UTF8. Hence you are storing Latin-1 encoding inside a UTF-8 database.
I thought it would automatically be handled by OO4O.True. Did you specify the character set of the NLS_LANG env variable for the OO4O client to WE8ISO8859P1 ? If it was set to UTF8 then Oracle will assume that the encoding coming thru' the ASP page are in UTF-8 , hence no conversion takes place ..
Also may be you should check the CODEPAGE directive and Charset property in your ASP ?
null

Not a valid SOAP Content-Type: text/html; charset=iso-8859-1

Friends
JDEV and SOA suite 10134
I have multiple domains on my BPEL Server. In one of the domain since I deployed the new process, all the processes of that domain are now failing on execution with following error in opmn/soa_instance/*.err log files. No errors in domain.log
+"Caused by: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; cha+
+rset=iso-8859-1"+
At the same time we get Internal Server Error on BPEL Console.
I have sync processes with 1 or two invokes, so I am generally losing the instances, cannot provide the details in the process execution. All BPEL processes are invoking Siebel Web Services, that is the common part.
When I restart my system, it may or may not work; even if it works then within few instances execution again starts giving the same error. I can see that after the errors the instance are going through and getting completed successfully few times. All these processes were working successfully earlier.
Any idea about this !!!!
Thanks

Thanks Anirudh,
I don't use compensation handlers. Moreover I have properly defined the scopes and sequences throughout the bpel process. My processes are sync in nature and I'm not able say at what step exactly the processes are failing and throwing the SOAP content Type error though the instances are getting completed with delay soemtimes.

Unsupported Content-Type: text/html; charset=iso-8859-1

Originally posted on JBI forum -
It was helpfully suggested there that I check on JAX-WS forum whether this was an issue with utf-8/16 encodings...
I have been experimenting with the openESB composite application described here
http://jlorenzen.blogspot.com/2007/08/using-jbi-javaee-serviceengine.html
This works fine as it appears on this webpage.
I have tried to adapt it to act as a proxy to a secure version of Hello EJB that runs on the SSL port of glassfish AS.
To do this I edited the EJB to set up the security properties. Edited the BPEL wsdl file and created a new composite application using the updated BPEL project.
This leads to an Unsupported Content-Type exception when a test case is run on the composite application from SOAP-UI
Does anyone know how I can explicitly set the content type of the proxied request to the secure WS?
Thanks
Joss Armstrong
HTTPBC-E00720: Provider for service [{http://j2ee.netbeans.org/wsdl/HelloBPEL}HelloBPELService] endpoint [HelloBPELPort] responded with an error status. Error detail is: BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>
com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=EJBPartnerLink, portType={http://hellopack/}Hello, operation=sayHello)
BPCOR-6129:Line Number is 29
BPCOR-6130:Activity Name is Invoke1
at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:968)
at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:538)
at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:181)
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148)
at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1001)
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:258)
at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1229)
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:407)
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:239)
at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
*Caused by: com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]*
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:171)
at com.sun.xml.ws.tx.client.TxClientPipe.process(TxClientPipe.java:177)
at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
at com.sun.xml.ws.client.Stub.process(Stub.java:248)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:180)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:986)
at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1016)
at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Request doesnt have a Content-Type
com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:372)
at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:228)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)

Jossarm/Jeff,
The Cryptography forum is not the right forum for this question; have you tried posting to the Glassfish forum on java.net?
But, here is what I think the problem might be:
SOAP-based web-service security uses XML Signature and XML Encryption to secure the message - not SSL; as a result it uses text/xml at the start of its message (which is what SOAP messages are). SSL assumes that the secure session has been established and all messages thereafter, are expected to begin with text/html (as expected in HTTP). You cannot mix-and match this - unless the service is an HTTP-based service that expects a SOAP-based message embedded in the HTTPRequest.

Convert utf-8 to iso-8859-1

Hello,
sorry for my very bad english
i use httpxmlrequest to answer a database and show resultin a
div
the string means utf-8 encoded by my javascript fonction and,
of course,
no result are found in the database.
How can i convert the string to iso-8859-1 before request the
database ?
Thank if you have an idea
JiBé (France)

PaulH **AdobeCommunityExpert** a Ã©crit :
> JibÃ© wrote:
>> PaulH **AdobeCommunityExpert** a Ã©crit :
>> I work with a MS SQL server database encoding in
iso-8859-1
>
> data stored in plain text,char,varchar datatypes (ie not
"N")?
datatype of "titre" is varchar(250) and "contenu" is text
using the
> ODBC or JDBC (it would be listed as ms sql server in the
db drivers
> list) driver?
I think it's jdbc driver (case of my test computer)
>
>> The code :
>
> you're not following good i18n practices. while my
preference is for
> unicode ("just use unicode" has been my motto for
years), if you're
> really only ever going to use french & never need
the euro symbol then i
> guess iso-8859-1 (latin-1) is fine.
Here is a part of the content of my application.cfm
<cfprocessingdirective pageencoding="iso-8859-1">
<cfcontent type="text/html; charset=iso-8859-1">
<cfset setEncoding("URL", "iso-8859-1")>
<cfset setEncoding("Form", "iso-8859-1")>
>
> if you think you might need other languages, including
the euro symbol,
> then you should consider unicode. change your text
columsn to "N" type
> (nText, nChar, nVarChar) & swap the latin-1
encodings in the tags above
> to utf-8.
I'm going to test that....
JiBÃ©

XML Encoding Issue - Format UTF-16 to ISO-8859-1

Dear Groupmates,
I have data in my Internal table which i am converting to XML using custom Transformation.
Data is going to third party.The third party system requires data in ISO-8859-1 Format but SAP is generating the same in UTF-16 Format.I have been able to change the format of file from
utf-16 to ISO-8859-1 format but after conversion i am getting invalid tag information in form of characters
like &lt , &gt etc..in my file.
Here is the code i have used to set the encoding to ISO-8859-1 :-
DATA: xmlout TYPE xstring.
DATA: ixml TYPE REF TO if_ixml,
streamfactory TYPE REF TO if_ixml_stream_factory,
encoding TYPE REF TO if_ixml_encoding,
ixml_ostream TYPE REF TO if_ixml_ostream.
ixml = cl_ixml=>create( ).
streamfactory = ixml->create_stream_factory( ).
ixml_ostream = streamfactory->create_ostream_xstring( xmlout ).
encoding = ixml->create_encoding(
character_set = 'ISO-8859-1' byte_order = 0 ).
ixml_ostream->set_encoding( encoding = encoding ).
Sample Output :-
<?xml version="1.0" encoding="iso-8859-1"?>
<AMS_DOC_XML_EXPORT_FILE><AMS_DOCUMENT AUTO_DOC_NUM="FALSE" DOC_CAT="CA" DOC_CD="CA" DOC_DEPT_CD="045" DOC_ID="XR10281060830400001" DOC_IMPORT_MODE="OE" DOC_TYP="CH" DOC_UNIT_CD ="NULL" DOC_VERS_NO="01">
<CH_DOC_HDR AMSDataObject="Y">
<DOC_CAT Attribute="Y"><![CDATA[CA]]></DOC_CAT>
<DOC_TYP Attribute="Y"><![CDATA[CH]]></DOC_TYP>
Please let me know if anyone has idea how i can get rid of the invalid tag information.
Thanks !
With Regards,
Darshan Mulmule

Darshan,
Did you get an answer for this question? We have same requirement to create XML file in ISO-8859-1 format with Attributes is set to "Y" and CDATA is being used for data.
Can you please let me know if you still remember how did you achieve it?
Satyen...

=?iso-8859-1?Q?Re:_=28PS=29_Im=E1genes_de_Rango_din=E1mico_HDR_-3?=

Similar Messages

Maybe you are looking for