=?iso-8859-1?Q?Fort=E9?= problem

JeanLuc Thiveyrat : MICHELIN FRANCE.
When we use the import or export facility of Forté, we have a crash
without any informations in the log.
It works under FSCRIPT, so it seems to be a problem due to the call of
the standard microsoft windows for choosing the file where you want to
store the pex or the cex.
I already had this problem when I install the first time Forté on NT
4.0.
I solved it by putting the name of the client in the node name
(control panel) !!!
But now for a new PC, even this solution does not work.
Any idea ?
Thanks.

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Similar Messages

Replies are sometimes using ISO-8859-1character set

Hello,
I am using iCloud - and iCloud Mail - in OSX 10.10.2 Yosemite on Macs (several different Macs).
Sometimes -- rarely -- when I do a reply to all and I look at the reply I mailed out under the "Sent" tab, I see that the whole reply is "garbled".
Loads of A's and 0's.
The actual reply is preceded with a text that resembles this (the numbers change from reply to reply):
Quote
--Apple-Webmail-42--c10907ed-7ae8-475d-80.....followed by more numbers
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=ISO-8859-1;
format=flowed
Unquote
The above "header" is followed by my reply that is completely garbled up too.
How can I avoid this formatting from happening?
Thanks in advance for your help.

LDAP is UTF-8 and Oracle is set to ISO-8859-1. Now
the problem is user info goes Oracle first and is
being validated by another UTF-8 based application
and then goes to LDAP. You are lucky things start in ISO-8859-1, because it encodes a proper subset of UTF-8. However, for characters beyond 127, UTF-8 encodes the character differently than ISO. Consequently, on the transition between Oracle and the UTF-8 based application, characters need to be recoded. Similarly, when characters come out of LDAP in UTF-8, they must be recoded to ISO if this is the encoding of your pages.
In this process all the
characters are getting distorted and I cannot change
LDAP and Oracle default charsets.Well, then there is no way around a recode. You cannot even try to trick the UTF-8 based application if it is slightly picky, because some ISO codes are simply illegal in UTF-8. The other way round would work: store UTF-8 in an ISO based application without recoding. At some point the ISO based application would just see two funny characters where there is only one, but as long as this does not distort any alphabetical sorting or even presentation to a user, you would just not care.
Harald.

=?iso-8859-1?Q?Fort=E9_CGI_problem?=

Messaggio a più sezioni in formato MIME.
------=_NextPart_000_008F_01BEFB9C.9ADF54B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
We have encountered the following problem:
Using the basic authentication on a web server, there is an problem =
passing the information between web server and Fort=E9.
In the attribute REMOTE_USER in the object Request.cgienv should be =
present the value of the user authentication, so in Fort=E9 we should =
access to it.
Instead, many of the values in the Request.cgienv not exists and we show =
the list:=20
**************** Attributes CGI in Request.cgienv ****************=20
Value of AUTH_TYPE=20
(nil)=20
Value of CONTENT_LENGTH=20
0=20
Value of CONTENT_TYPE=20
(nil)=20
Value of GATEWAY_INTERFACE=20
(nil)=20
Value of HTTP_ACCEPT=20
(nil)=20
Value of HTTP_COOKIE=20
(nil)=20
Value of HTTP_USER_AGENT=20
(nil)=20
Value of PATH_INFO=20
/frte_cs0=20
Value of PATH_TRANSLATED=20
(nil)=20
Value of QUERY_STRING=20
ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm=20
Value of REMOTE_ADDR=20
(nil)=20
Value of REMOTE_HOST=20
(nil)=20
Value of REMOTE_IDENT=20
(nil)=20
Value of REMOTE_USER=20
(nil)=20
Value of REQUEST_METHOD=20
GET=20
Value of SCRIPT_NAME=20
(nil)=20
Value of SERVER_NAME=20
(nil)=20
Value of SERVER_PORT=20
0=20
Value of SERVER_PROTOCOL=20
(nil)=20
Value of SERVER_SOFTWARE=20
(nil)=20
In the environment are installed the followings versions of products:
Fort=E9 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Fort=E9 3.G.2 and WebEnterprise 1.B, the =
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of the =
basic authentication in a Fort=E9 variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.
*------------------------------------------------------------------------=
Massimiliano Delsante
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
------=_NextPart_000_008F_01BEFB9C.9ADF54B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<DEFANGED-META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<DEFANGED-META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY><DEFANGED-BODY bgColor=3D#ffffff>
<DIV>
<DIV>
We have encountered the following problem:

Using the basic authentication on a web server, there =
is an=20
problem passing the information between web server and Forté.
In the attribute REMOTE_USER in the object =
Request.cgienv=20
should be present the value of the user authentication, so in =
Forté we=20
should access to it.
Instead, many of the values in the Request.cgienv not =
exists=20
and we show the list: 

**************** Attributes CGI in Request.cgienv=20
**************** 
Value of AUTH_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of CONTENT_LENGTH 0 <FONT=20
face=3DArial size=3D2>
Value of CONTENT_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of GATEWAY_INTERFACE (nil)<FONT=20
size=3D2> 
Value of HTTP_ACCEPT (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_COOKIE (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_USER_AGENT (nil) <FONT=20
face=3DArial size=3D2>
Value of PATH_INFO /frte_cs0 <FONT=20
face=3DArial size=3D2>
Value of PATH_TRANSLATED (nil) <FONT=20
face=3DArial size=3D2>
Value of QUERY_STRING=20
 ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm</F=
ONT><FONT=20
size=3D2> 
Value of REMOTE_ADDR (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_HOST (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_IDENT (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_USER (nil) <FONT=20
face=3DArial size=3D2>
Value of REQUEST_METHOD GET <FONT=20
face=3DArial size=3D2>
Value of SCRIPT_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_PORT 0 <FONT=20
face=3DArial size=3D2>
Value of SERVER_PROTOCOL (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_SOFTWARE (nil) <FONT=20
face=3DArial size=3D2>
In the environment are installed the followings versions of =
products:
Forté 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Forté 3.G.2 and WebEnterprise 1.B, =
the=20
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of =
the=20
basic authentication in a Forté variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.</DIV></DIV>
<DIV>*---------------------------------------------------------------=
----------------------------------------------* Massimiliano=20
Delsante</DIV>
<DIV> </DIV>
<DIV>O.T. Consulting S.r.l - <A=20
href=3D"<a href=
"http://www.otconsulting.com">http://www.otconsulting.com</a>">www.otconsulting.com</A> Via =
della=20
Previdenza Sociale N° 11 - 42100 - Reggio Emilia Tel. +39 0522 =
271550 -=20
Fax +39 0522=20
230710 *--------------------------------------------------------------=
-----------------------------------------------* </DIV></BODY><=
/HTML>
------=_NextPart_000_008F_01BEFB9C.9ADF54B0--

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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>

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.

Problems with reading XML files with ISO-8859-1 encoding

Hi!
I try to read a RSS file. The script below works with XML files with UTF-8 encoding but not ISO-8859-1. How to fix so it work with booth?
Here's the code:
import java.io.File;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import java.net.*;
* @author gustav
public class RSSDocument {
 /** Creates a new instance of RSSDocument */
 public RSSDocument(String inurl) {
 String url = new String(inurl);
 try{
 DocumentBuilder builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
 Document doc = builder.parse(url);
 NodeList nodes = doc.getElementsByTagName("item");
 for (int i = 0; i < nodes.getLength(); i++) {
 Element element = (Element) nodes.item(i);
 NodeList title = element.getElementsByTagName("title");
 Element line = (Element) title.item(0);
 System.out.println("Title: " + getCharacterDataFromElement(line));
 NodeList des = element.getElementsByTagName("description");
 line = (Element) des.item(0);
 System.out.println("Des: " + getCharacterDataFromElement(line));
 } catch (Exception e) {
 e.printStackTrace();
 public String getCharacterDataFromElement(Element e) {
 Node child = e.getFirstChild();
 if (child instanceof CharacterData) {
 CharacterData cd = (CharacterData) child;
 return cd.getData();
 return "?";
}And here's the error message:
org.xml.sax.SAXParseException: Teckenkonverteringsfel: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (radnumret kan vara f�r l�gt).
 at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
 at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
 at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
 at org.apache.crimson.parser.Parser2.maybeXmlDecl(Parser2.java:1183)
 at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:653)
 at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
 at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
 at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)
 at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
 at getrss.RSSDocument.<init>(RSSDocument.java:25)
 at getrss.Main.main(Main.java:25)

I read files from the web, but there is a XML tag
with the encoding attribute in the RSS file.If you are quite sure that you have an encoding attribute set to ISO-8859-1 then I expect that your RSS file has non-ISO-8859-1 character though I thought all bytes -128 to 127 were valid ISO-8859-1 characters!
Many years ago I had a problem with an XML file with invalid characters. I wrote a simple filter (using FilterInputStream) that made sure that all the byes it processed were ASCII. My problem turned out to be characters with value zero which the Microsoft XML parser failed to process. It put the parser in an infinite loop!
In the filter, as each byte is read you could write out the Hex value. That way you should be able to find the offending character(s).

Problem with charset ISO-8859 with dinamic action

Hello
I migrated my application that was Apex 3.2, and now Apex is 4.2.3, but a have a problem when I'm use Dynamic Action with ISO-8859.
When I used a filter "ação" in dinamic action filter mounted by the apex presents 'aÃ § Ã £ o.'
If I force use of PlsqlNLSLanguage = BRAZILIAN PORTUGUESE_BRAZIL.UTF8 in Dads, works correct.
Please, Help me! I need to keep ISO-8859!
Thanks

Using another example to illustrate the problem… I
found an apparent solution using "encodeURI".
It sees:
quote:
BEFORE:
function SaveMsg()
if (document.sender.message == "" )
return false;
var mensagem=document.sender.message.value;
ds2.setURL('responsexml.asp?action=add'&msg='+mensagem);
ds2.loadData();
document.sender.message.value="";
document.sender.message.focus();
When the entrance of the changeable "mensagem" was
“João” was recorded in archive XML as
“Joo” ...
input: "João"
output: "Joo"
quote:
AFTER:
function SaveMsg()
if (document.sender.message == "" )
return false;
var mensagem=encodeURI(document.sender.message.value);
ds2.setURL('responsexml.asp?action=add'&msg='+mensagem);
ds2.loadData();
document.sender.message.value="";
document.sender.message.focus();
Now ...
input: "João"
output: "João"
This would be a good solution? I will not have problems,
right? Some opinion/suggestion on this solution?

HTTP Test Tool Umlaut (Special Character) Problem iso-8859-1 utf-8

Hi folks,
I habe a Problem in an HTTP to IDOC Scenario. The configuration works and when I test it, by using the Test Message Tool from the Runtime Workbench i get the following problem:
I post an IDOC XML Charset iso-8859-1 when it arrive as IDoc in business system german umlauts would be displayd very cryptic
ä = Ã¤
ü = Ã¼
and so on ....
When I post the XML with UTF-8 charset it works, what can i do to handle this ?
Thank you

Hi,
maybe this document is helpful:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
and also this thread:
Character translation error in Mapping Lookup API (RFC)
Regards
Patrick

Problem when setting encoding to ISO-8859-1

Hi. Is there something I'm missing when it comes to setting
encoding? Here are the code in the mxml:
<?xml version="1.0" encoding="ISO-8859-1"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
</Application>
In the html-template I'm setting:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1" />
The code for sending data from the app:
<mx:HTTPService
id="service"
url="encoding.jsp"
method="post"
showBusyCursor="true"
result="onResult(event)"
resultFormat="xml"
contentType="application/xml"
fault="onFault(event)"
useProxy="false" />
public function send():void {
var xml:XML = <Data>{data.text}</Data>;
service.send(xml);
But still the respons jsp I have made says it receives the
data in UTF-8 format? What am I doing wrong?
Servercode:
don't work: BufferedReader reader = new BufferedReader( new
InputStreamReader( is ) );
work: BufferedReader reader = new BufferedReader( new
InputStreamReader( is, "UTF-8") );

Are there no-one who have the same problem? I've tried
everything imaginable, and still the serverside receives the data
as UTF-8.
Is it supported at all to set the encoding of the
request?

Nerving Problem with UTF-8 and ISO-8859-1

Hi,
I´m looking for a solution to serve this problem for many hours now, maybe someone can help me:
1.) We need to send our Mails with the ISO-8859-1-Charset because otherwise Windows-Users get the text in the message twice: once as plain, and after a question mark formated. So I changed the NSPreferredMailCharset in the com.apple.mail.plist to ISO-8859-1:
defaults write com.apple.mail NSPreferredMailCharset "ISO-8859-1"
2.) So far so good. It works until I add an attachment to a message. Adding an attachment forces the sending of the mail again as Unicode (UTF-8). I could change the encoding manual, but thats not the way we can work in our company.
My question is: is there any way to force mail to encode as ISO-8859-1? It can´t be that we have to change the encoding for every message.
Thanks a lot
florian
PS: I´m not sure if this is important: we use the osx in German.

I was thinking that since he is from Austria & references a company, there is a very strong possibility that the character "€" (the Euro currency symbol, Unicode 20AC, UTF-8 E2 82 AC) would frequently appear in messages.
Even if he sets a preference for ISO-8859-1 as the default with Terminal, or manually changes messages to ISO-8859-1, it would not be possible to include this symbol in such messages, since there is no "€" in ISO-8859-1.
Similar problems would occur with other symbols sometimes used in business (for example "™"), in engineering ("Ω"), in mathematics ("∑"), or even with some general punctuation marks such as the dagger ("†").
Other possible problems are the use of other currency symbols the Euro replaced (the franc's "₣" or the lira's "₤") or others still in use (the Israeli new sheqel's "₪ or rupee's "₨"). Ligatures in an international environment would really complicate things as well, as this Wikipedia article about the Œthel illustrates.
Note that in none of these cases would the presence or absence of an attachment matter -- ISO-8859-1 simply isn't up to the task.
I suspect that in some cases, if it is possible, setting the default to Windows-1252 (Windows Latin 1 in Mail's list?) would help, since it does include at least the Euro & dagger. I haven't played around with this much, but I do note that in a new message window containing "€" in the body, if I set the text encoding to Windows Latin 1, Automatic, or UTF-8, Mail doesn't complain, but if I set it to ISO Latin 1, I get an error saying the message can't be saved & an "Invalid Text Encoding" alert if I try to send it.
As for how messages are received at the other end, Windows apps (not just Outlook) are notorious for continuing to use non-Unicode API's even after the OS itself has long since moved to Unicode as its internal standard. Some of them employ bass-ackwards fixes like deciding ISO-8859-1 declarations are supposed to be Windows-1252 ones. Worse, Windows itself sometimes seems to interpret a few Windows-1252 code positions as their ISO-8859-1 control equivalents!
All this makes life that much more complicated for people trying to avoid problems like the above.

Hi! Ihave a problems with ISO-8859-1

we define the communications channel type file with file encoding ISO-8859-1, when the messages see in the sxmb_moni is correct the characters is correct and the sign but when you test the message in the id.
when the messages is send have error with de characters and sign the message have a mistake.
Someone know something have one idea..

I've had the same problems with a File Adapter in my XI. If that is your case you have to change your encoding to the encoding of the XI server. I tried with ISO-8859-15(try with it, you never knows) and it worked. Its funny that the encoding in the CC parametrization its the encoding of the server

Are there any books out about =?iso-8859-1?Q?Fort=E9?= or=?iso-8859-1

I am trying to find books on Forté or Forté Express.
Could anyone help me answer this question.
Thank You
John Schaefer
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

that try/catch was just a lazy way to get passed the compiler for this tiny test program. on Sun, both
x = new String(bytes, 0, 2, "ISO-8859-1" );and
x = new String(bytes );produced the same incorrect result. Sun's default is US-ASCII, so it looks like something either wasn't set right, either in the code, or in the OS, or in the java invocation, that it made both ISO-8859-1 and US-ASCII the same or that ISO-8859-1 doesn't even exists and it reverted back to the default. it didn't throw exception, that i know, otherwise, x would not have been set.
Might there be something in the OS or jvm that might relate to ISO-8859-1 support?

Problems reading Latin2 (ISO 8859-2) characters

Hello!
I want to read the content of an MS Access table (in an MDB file) using the JDBC:ODBC driver.
The program works well but there is a character conversion problem when I read text fields from the table.
The Latin2 (ISO 8859-2) characters like áéíóőűüöÁÉÍÓÜÖŰŐ are replaced by the "?" character.
I use the ResultSet object's getString() method.
Any idea about how to solve this problem?

Try to change session encoding from defaut to iso-8559-2
This probably would help:
http://download.oracle.com/javase/1.4.2/docs/guide/jdbc/bridge.html
>
What's New with the JDBC-ODBC Bridge?
* A jdbc:odbc: connection can now have a charSet property, to specify a Character Encoding Scheme other than the client default.
For possible values, see the Internationalization specification on the Web Site.
The following code fragment shows how to set 'Big5' as the character set for all character data.
// Load the JDBC-ODBC bridge driver
Class.forName(sun.jdbc.odbc.JdbcOdbcDriver) ;
// setup the properties
java.util.Properties prop = new java.util.Properties();
prop.put("charSet", "Big5");
prop.put("user", username);
prop.put("password", password);
// Connect to the database
con = DriverManager.getConnection(url, prop);

Problems creating mail attachment in codepage ISO-8859-1

Hi,
i'm sending emails from PI tom our customers. Some of them cannot read the attachements that are created in codepage utf-8.
Can anyone tell me how to create an attachment in codepage ISO-8859-1.
Thanky
BR
Ralf

Hi Ralf,
I create plain text files.
also
actually i´m using an own local ejb to create a nice looking html-email.
Can u please specify whether the attachment is going as a simple txt file or as HTML....
if it is a text file.. then the things are very simple.
From inbound XML,use the MessageTransformationBean,and specify the FCC(File content conversion)how u want the text file.
If it is a HTML or XML u can create the payload from the Mapping itself and send it to adapter.
But make sure that the attachment name is having .htm or .html and content_type is text/html
Babu

=?iso-8859-1?Q?I:_Fort=E9_CGI_problem?=

Messaggio a più sezioni in formato MIME.
------=_NextPart_000_00A9_01BEFB9D.13EFC330
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
*------------------------------------------------------------------------=
Massimiliano Delsante
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
-----Messaggio originale-----
Da: Massimilano Delsante <[email protected]>
A: forte users <[email protected]>
Data: venerd=EC 10 settembre 1999 14.56
Oggetto: Fort=E9 CGI problem
We have encountered the following problem:
Using the basic authentication on a web server, there is an problem =
passing the information between web server and Fort=E9.
In the attribute REMOTE_USER in the object Request.cgienv should be =
present the value of the user authentication, so in Fort=E9 we should =
access to it.
Instead, many of the values in the Request.cgienv not exists and we show =
the list:=20
**************** Attributes CGI in Request.cgienv ****************=20
Value of AUTH_TYPE=20
(nil)=20
Value of CONTENT_LENGTH=20
0=20
Value of CONTENT_TYPE=20
(nil)=20
Value of GATEWAY_INTERFACE=20
(nil)=20
Value of HTTP_ACCEPT=20
(nil)=20
Value of HTTP_COOKIE=20
(nil)=20
Value of HTTP_USER_AGENT=20
(nil)=20
Value of PATH_INFO=20
/frte_cs0=20
Value of PATH_TRANSLATED=20
(nil)=20
Value of QUERY_STRING=20
ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm=20
Value of REMOTE_ADDR=20
(nil)=20
Value of REMOTE_HOST=20
(nil)=20
Value of REMOTE_IDENT=20
(nil)=20
Value of REMOTE_USER=20
(nil)=20
Value of REQUEST_METHOD=20
GET=20
Value of SCRIPT_NAME=20
(nil)=20
Value of SERVER_NAME=20
(nil)=20
Value of SERVER_PORT=20
0=20
Value of SERVER_PROTOCOL=20
(nil)=20
Value of SERVER_SOFTWARE=20
(nil)=20
In the environment are installed the followings versions of products:
Fort=E9 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Fort=E9 3.G.2 and WebEnterprise 1.B, the =
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of the =
basic authentication in a Fort=E9 variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.
*------------------------------------------------------------------------=
Massimiliano Delsante
=20
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
------=_NextPart_000_00A9_01BEFB9D.13EFC330
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<DEFANGED-META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN">
<DEFANGED-META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY><DEFANGED-BODY bgColor=3D#ffffff>
<DIV> </DIV>
<DIV>*---------------------------------------------------------------=
----------------------------------------------* Massimiliano=20
Delsante</DIV>
<DIV> </DIV>
<DIV>O.T. Consulting S.r.l - <A=20
href=3D"<a href=
"http://www.otconsulting.com">http://www.otconsulting.com</a>">www.otconsulting.com</A> Via =
della=20
Previdenza Sociale N° 11 - 42100 - Reggio Emilia Tel. +39 0522 =
271550 -=20
Fax +39 0522=20
230710 *--------------------------------------------------------------=
-----------------------------------------------* </DIV>
<DIV>-----Messaggio =
originale----- Da:=20
Massimilano Delsante <<A=20
href=3D"<a href=
"mailto:[email protected]">mailto:[email protected]</a>">[email protected]</A>&g=
t; A:=20
forte users <<A=20
href=3D"<a href=
"mailto:[email protected]">mailto:[email protected]</a>">[email protected]</A>> =
Data:=20
venerdì 10 settembre 1999 14.56 Oggetto: =
Forté CGI=20
problem </DIV>
<DIV>
<DIV>
We have encountered the following problem:

Using the basic authentication on a web server, there =
is an=20
problem passing the information between web server and Forté.
In the attribute REMOTE_USER in the object =
Request.cgienv=20
should be present the value of the user authentication, so in =
Forté we=20
should access to it.
Instead, many of the values in the Request.cgienv not =
exists=20
and we show the list: 

**************** Attributes CGI in Request.cgienv=20
**************** 
Value of AUTH_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of CONTENT_LENGTH 0 <FONT=20
face=3DArial size=3D2>
Value of CONTENT_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of GATEWAY_INTERFACE (nil)<FONT=20
size=3D2> 
Value of HTTP_ACCEPT (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_COOKIE (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_USER_AGENT (nil) <FONT=20
face=3DArial size=3D2>
Value of PATH_INFO /frte_cs0 <FONT=20
face=3DArial size=3D2>
Value of PATH_TRANSLATED (nil) <FONT=20
face=3DArial size=3D2>
Value of QUERY_STRING=20
 ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm</F=
ONT><FONT=20
size=3D2> 
Value of REMOTE_ADDR (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_HOST (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_IDENT (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_USER (nil) <FONT=20
face=3DArial size=3D2>
Value of REQUEST_METHOD GET <FONT=20
face=3DArial size=3D2>
Value of SCRIPT_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_PORT 0 <FONT=20
face=3DArial size=3D2>
Value of SERVER_PROTOCOL (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_SOFTWARE (nil) <FONT=20
face=3DArial size=3D2>
In the environment are installed the followings versions of =
products:
Forté 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Forté 3.G.2 and WebEnterprise 1.B, =
the=20
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of =
the=20
basic authentication in a Forté variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.</DIV></DIV>
<DIV>*---------------------------------------------------------------=
----------------------------------------------* Massimiliano=20
Delsante</DIV>
<DIV> </DIV>
<DIV>O.T. Consulting S.r.l - <A=20
href=3D"<a href=
"http://www.otconsulting.com">http://www.otconsulting.com</a>">www.otconsulting.com</A> Via =
della=20
Previdenza Sociale N° 11 - 42100 - Reggio Emilia Tel. +39 0522 =
271550 -=20
Fax +39 0522=20
230710 *--------------------------------------------------------------=
-----------------------------------------------* </DIV></BODY><=
/HTML>
------=_NextPart_000_00A9_01BEFB9D.13EFC330--

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Re: =?iso-8859-1?Q?I:_Fort=E9_CGI_problem?=

Massimilano,
We have just experienced this with
Forte 3.0.L.2
WebEnterprise 1.0.D.1
on DEC alpha OSF environment.
There is a forte defect report #48399
relating an unfixed problem in this version of Web Enterprise
"HTTPRequest missing CGI variables, including REMOTE_ADDR and REMOTE_HOST"
which looks like the problem.
Have you had any suggestions to get around this?
John
To: <[email protected]>
Subject: =?iso-8859-1?Q?I:_Fort=E9_CGI_problem?=
From: "Massimilano Delsante" <[email protected]>
Date: Fri, 10 Sep 1999 14:59:27 +0200
Reply-To: "Massimilano Delsante" <[email protected]>
We have encountered the following problem:
Using the basic authentication on a web server, there is an problem =
passing the information between web server and Fort=E9.
In the attribute REMOTE_USER in the object Request.cgienv should be =
present the value of the user authentication, so in Fort=E9 we should =
access to it.
Instead, many of the values in the Request.cgienv not exists and we show =
the list:=20
**************** Attributes CGI in Request.cgienv ****************=20
Value of AUTH_TYPE=20
(nil)=20
Value of CONTENT_LENGTH=20
0=20
Value of CONTENT_TYPE=20
(nil)=20
Value of GATEWAY_INTERFACE=20
(nil)=20
Value of HTTP_ACCEPT=20
(nil)=20
Value of HTTP_COOKIE=20
(nil)=20
Value of HTTP_USER_AGENT=20
(nil)=20
Value of PATH_INFO=20
/frte_cs0=20
Value of PATH_TRANSLATED=20
(nil)=20
Value of QUERY_STRING=20
ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm=20
Value of REMOTE_ADDR=20
(nil)=20
Value of REMOTE_HOST=20
(nil)=20
Value of REMOTE_IDENT=20
(nil)=20
Value of REMOTE_USER=20
(nil)=20
Value of REQUEST_METHOD=20
GET=20
Value of SCRIPT_NAME=20
(nil)=20
Value of SERVER_NAME=20
(nil)=20
Value of SERVER_PORT=20
0=20
Value of SERVER_PROTOCOL=20
(nil)=20
Value of SERVER_SOFTWARE=20
(nil)=20
In the environment are installed the followings versions of products:
Fort=E9 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Fort=E9 3.G.2 and WebEnterprise 1.B, the =
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of the =
basic authentication in a Fort=E9 variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.
*------------------------------------------------------------------------=
Massimiliano Delsante
=20
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
John Soper, Information Systems Development, ITS, The University of Melbourne
email: [email protected] >>>> Tel: 9344 5612

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

=?iso-8859-1?Q?Fort=E9?= problem

Similar Messages

Maybe you are looking for