(OT) Programa =?ISO-8859-1?Q?cibercaf=E9?=

Hola, buenos d=EDas.
Tengo un amigo que tiene un cibercaf=E9 y me ha pedido que le
recomiende =
un programa para gestionar la conexi=F3n, permiso de
programas y esas=20
cosas que llevan los cibercaf=E9s.
Dice que le han comentado alguno que a la vez lleva el
control de stock.
Como hay tanto de todo por el google, me gustar=EDa saber si
alguno de=20
vosotros tiene experiencia en el tema y me puede recomendar
algo al=20
respecto.
Muchas gracias.

Hola Misha, buenas tardes.
Y tanto que me ha servido tu comentario, muchas gracias. Creo
que es=20
justo lo que necesita.
Pienso que el cibercontrol es el que m=E1s se le adecua,
porque adem=E1s =
de=20
que est=E1 en castellano es m=E1s barato.
Muchas gracias :)
Mikhail escribi=F3:
> Que tal Lolita,
>=20
> hace como 5 a=F1os ten=EDa unos clientes que usaban el
sw de CiberContr=
ol
>
http://www.cibercontrol.com/index.htm
> Yo lo estudi=E9 y lo manej=E9 en ese tiempo y estaba muy
bueno...
> Reportes, cortes del dia, la gente no pod=EDa modificar
nada que no qui=
sieras,
> control de impresiones... etc etc etc
> Luego, como al a=F1o, alguien me pidio consejo y
busqu=E9 mas opciones =
y tambien
> me lleno el ojo el siguiente:
>
http://www.cybertimesoftware.com/
> Son los dos unicos que yo te podr=EDa recomendar... y
pues bueno, el q=
ue aun
> est=E9n las empresas significa que han tenido
continuidad desde esos a=F1=
os...
>=20
> Espero que te sirva mi comentario, Saludos.
>=20
> Misha.
>=20
>=20

Similar Messages

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>

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.

How to set the Xml Encoding ISO-8859-1 to Transformer or DOMSource

I have a xml string and it already contains an xml declaration with encoding="ISO-8859-1". (In my real product, since some of the element/attribute value contains a Spanish character, I need to use this encoding instead of UTF-8.) Also, in my program, I need to add more attributes or manipulate the xml string dynamically, so I create a DOM Document object for that. And, then, I use Transformer to convert this Document to a stream.
My problme is: Firstly, once converted through the Transformer, the xml encoding changed to default UTF-8, Secondly, I wanted to check whether the DOM Document created with the xml string maintains the Xml Encoding of ISO-8859-1 or not. So, I called Document.getXmlEncoding(), but it is throwing a runtime error - unknown method.
Is there any way I can maintain the original Xml Encoding of ISO-8859-1 when I use either the DOMSource or Transformer? I am using JDK1.5.0-12.
Following is my sample program you can use.
I would appreciate any help, because so far, I cannot find any answer to this using the JDK documentation at all.
Thanks,
Jin Kim
import java.io.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
public class XmlEncodingTest
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Transformer transformer = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Yes\" />\n")
                 .append("</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("initial xml = \n" + xmlStrBuf.toString());
        try
            //Test1: Use the transformer to ouput the xmlStrBuf.
            // This shows the xml encoding result from the transformer which will change to UTF-8
            tFactory = TransformerFactory.newInstance();
            transformer = tFactory.newTransformer();
            StreamSource ss = new StreamSource( new StringBufferInputStream( xmlStrBuf.toString()));
            System.out.println("Test1 result = ");
            transformer.transform( ss, new StreamResult(System.out));
            //Test2: Create a DOM document object for xmlStrBuf and manipulate it by adding an attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new StringBufferInputStream( xmlStrBuf.toString()));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document. the encoding becomes UTF-8
            DOMSource source = new DOMSource(document);
            StreamResult result = new StreamResult(System.out);
            System.out.println("\n\nTest2 result = ");
            transformer.transform(source, result);
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
    public static void main( String arg[])
        XmlEncodingTest xmlTest = new XmlEncodingTest();
        xmlTest.performTest();
}

Thanks DrClap for your answer. With your information, I rewrote the sample program as in the following, and it works well now as I intended! About the UTF-8 and Spanish charaters, I think you are right. It looks like there can be many factors involved on this subject though - for example, the real character sets used to create an xml document, and the xml encoding information declared will matter. The special character I had a trouble was u00F3, and somehow, I found out that Sax Parser or even Document Builder parser does not like this character when encoding is set to "UTF-8" in the Xml document. My sample program below may not be a perfect example, but if you replaces ISO-8859-1 with UTF-8, and not setting the encoding property to the transfermer, you may notice that the special character in my example is broken in Test1 and Test2. In my sample, I decided to use ByteArrayInputStream instead of StringBufferInpuptStream because the documentation says StringBufferInputStream may have a problem with converting characters into bytes.
Thanks again for your help!
Jin Kim
import java.io.*;
import java.util.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
* XML encoding test for Transformer
public class XmlEncodingTest2
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Resoluci�n\">\n")
                 .append("Special charatered attribute test")
                 .append("\n</ELEM>")
                 .append("\n</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("**** Initial xml = \n" + xmlStrBuf.toString());
        try
            //TransformerFactoryImpl transformerFactory = new TransformerFactoryImpl();
            //Test1: Use the transformer to ouput the xmlStrBuf.
            tFactory = TransformerFactory.newInstance();
            Transformer transformer = tFactory.newTransformer();
            byte xmlbytes[] = xmlStrBuf.toString().getBytes("ISO-8859-1");
            StreamSource streamSource = new StreamSource( new ByteArrayInputStream( xmlbytes ));
            ByteArrayOutputStream xmlBaos = new ByteArrayOutputStream();
            Properties transProperties = transformer.getOutputProperties();
            transProperties.list( System.out); // prints out current transformer properties
            System.out.println("**** setting the transformer's encoding property to ISO-8859-1.");
            transformer.setOutputProperty("encoding", "ISO-8859-1");
            transformer.transform( streamSource, new StreamResult( xmlBaos));
            System.out.println("**** Test1 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //Test2: Create a DOM document object for xmlStrBuf to add a new attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new ByteArrayInputStream( xmlbytes));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document.
            DOMSource source = new DOMSource(document);
            xmlBaos.reset();
            transformer.transform( source, new StreamResult( xmlBaos));
            System.out.println("\n\n****Test2 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //xmlBaos.flush();
            //xmlBaos.close();
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
        finally
    public static void main( String arg[])
        XmlEncodingTest2 xmlTest = new XmlEncodingTest2();
        xmlTest.performTest();
}

Encoding XML in ISO-8859-1 from a unicode system

Hello
I want to generate an XML with an encoding ISO-8859-1. I'm on a unicode platform.
I've done the following program :
It works well with the line 'encoding UTF-16.
With the line encoding 'encoding ISO ...', I have special characters in the sting xml_string.
NB : The program works correctly on a non-unicode platform.
Can you help me ?
Thank you
REPORT .
DATA : xml_string TYPE string.
DATA : BEGIN OF l_id,
         numero(10),
         systeme   TYPE gsval,
         date      TYPE d,
         heure     TYPE uzeit,
         type(7),
         nb_nid TYPE i,
       END OF l_id.
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.
START-OF-SELECTION.
l_id-date    = sy-datum.
l_id-heure   = sy-uzeit.
l_id-type    = 'BATCH'.
ixml = cl_ixml=>create( ).
streamfactory = ixml->create_stream_factory( ).
ixml_ostream = streamfactory->create_ostream_cstring( xml_string ).
encoding = ixml->create_encoding( character_set = 'ISO-8859-1' byte_order = 0 ).
encoding = ixml->create_encoding( character_set = 'UTF-16' byte_order = 0 ).
ixml_ostream->set_encoding( encoding = encoding ).
CALL TRANSFORMATION ztest_xml
        SOURCE id   = l_id
        RESULT XML ixml_ostream.
BREAK-POINT.

Forum rules say: no mail (we must share the solution)
I didn't understand what was exactly his issue, and what he exactly meant by "then to convert with the good encoding".
His first sentence means that he used the following program (using Xstring instead of string):
REPORT .
DATA : xml_xstring TYPE xstring.
DATA : BEGIN OF l_id,
numero(10),
systeme TYPE gsval,
date TYPE d,
heure TYPE uzeit,
type(7),
nb_nid TYPE i,
END OF l_id.
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.
START-OF-SELECTION.
l_id-date = sy-datum.
l_id-heure = sy-uzeit.
l_id-type = 'BATCH'.
ixml = cl_ixml=>create( ).
streamfactory = ixml->create_stream_factory( ).
ixml_ostream = streamfactory->create_ostream_xstring( xml_xstring ).
encoding = ixml->create_encoding( character_set = 'ISO-8859-1' byte_order = 0 ).
ixml_ostream->set_encoding( encoding = encoding ).
CALL TRANSFORMATION id
SOURCE id = l_id
RESULT XML ixml_ostream.
* in debug here, you'll see that xml_xstring contains
* XML result in ISO-8859-1 encoding
BREAK-POINT.

Cannot change charset from 'ISO-8859-1' to 'UTF-8' ?

I've programed a web application with Facelets. As I start the first page "index.html" I got the following exception:
"java.lang.IllegalStateException: Attempt to change ContentType after calling getWriter() (cannot change charset from 'ISO-8859-1' to 'UTF-8')"
The header of the "index.html" looks as follow:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="refresh" content="0; url=./guess.jsf" />
<title>Untitled Document</title>
</head>
What's wrong? Is it a bug of weblogic?

same problem here with wl8.1
have you sold it and if yes, how?
thanks

Abap Proxy Convert UTF-8 to ISO-8859-1

Dear,
I have the following scenario:
Abap Proxy-> PI -> WebService.
I need to change the encondig UTF-8 to ISO-8859-1 when the SAP ECC sends data to the PI.
How do I do this?
I have a XSLT program that performs the this conversion, UTF-8 to ISO-8859-1, between PI and WebService.
Regards,
Sérgio Salomã

To understand more about Character Encoding in SAP Process Integration. You can refer the following link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true

British Pound Sterling with UTF-8 and ISO-8859-15

Please excuse my long-windedness ... I'm simply trying to answer all possible questions up front and give the most possible information. I've searched through tons of forums and all over various sites and references and am not able to come up with a concrete solution to this. I'd appreciate any help anyone has.
I'm having some trouble with character sets and international currencies.
Our server was recently upgraded from Red Hat 7.3 to Red Hat 8.0. I understand that the default system encoding thus changed from ISO-8859-15 to UTF-8. I have verified this by executing the following:
public class WhichEncoding {
public static void main(String args[])
    String p = System.getProperty("file.encoding");
    System.out.println(p);
}I have two machines, one which represents the old system (7.3) and one representing the new (8.0), which I will call machine73 and machine80 respectively.
[machine73:~]# java WhichEncoding
ISO-8859-15
[machine80:~]# java WhichEncoding
UTF-8I have also verified that the JVM is using the correct default character set by executing the following:
import java.io.ByteArrayOutputStream;
import java.io.OutputStreamWriter;
public class WhichCharset {
    public static void main (String[] args) {
        String foo = (String)(new OutputStreamWriter(new ByteArrayOutputStream())).getEncoding();
        System.out.println(foo);
}which yields:
[machine73:~]# java WhichCharset
ISO-8859-15
[machine80:~]# java WhichCharset
UTF8Here comes the problem. I have the following piece of code:
import java.text.NumberFormat;
import java.util.Locale;
public class TestPoundSterling
    public static void main (String[] args)
        NumberFormat nf = NumberFormat.getCurrencyInstance(new Locale("en", "GB"));
        System.out.println(nf.format(1.23));
}When I compile and execute this, I see mixed results. On machine73, I see what I would expect to see, the British Pound Sterling followed by 1.23. To be sure, I outputted the results to a file which I viewed in a hex editor, and observed [A3 31 2E 32 33 0A], which seems to be correct.
However, when I execute it on machine80, I see a capital A with a circumflex (carat) preceding the British Pound Sterling and the 1.23. The hex editor shows [C2 A3 31 2E 32 33 0A].
I looked up these hexadecimal values:
Extended ASCII
0xC2 = "T symbol"
0xA3 = lowercase "u" with grave
ISO-8859-1
0xC2 = Capital "A" with circumflex (carat)
0xA3 = British Pound Sterling
Unicode Latin-1
0x00C2 = Capital "A" with circumflex (carat)
0x00A3 = British Pound Sterling
(This explains why, when I remove /bin/unicode_start and reboot, I see a "T symbol" and "u" with a grave in place of what I saw before ... probably an irrelevant sidenote).
I found a possible answer on http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8 under the Examples section. Apparently, a conversion between Unicode and UTF-8 acts differently based on the original Unicode value. Since the Pound Sterling falls between U-00000080 � U-000007FF (using the chart on the mentioned site), the conversion would be (as far as I can tell):
U-000000A3 = 11000010 10101001 = 0xC2 0xA3
This appears to be where the extra 0xC2 pops up.
Finally, to the whole point of this: How can I fix this so that things work as they should on machine80 like they did on machine73. All I want to see at the command line is the Pound Sterling. Getting the 0xC2 preceding the Pound Sterling causes some parts of my applications to fail.
Here's some additional information that might be of use:
[machine73:~]# cat /etc/sysconfig/i18n
LANG="en_US.iso885915"
SUPPORTED="en_US.iso885915:en_US:en"
SYSFONT="lat0-sun16"
SYSFONTACM="iso15"
[machine73:~]# echo $LANG
en_US.iso885915
[machine80:~]# cat /etc/sysconfig/i18n
LANG="en_US.UTF-8"
SUPPORTED="en_US.UTF-8:en_US:en"
SYSFONT="latarcyrheb-sun16"
[machine80:~]# echo $LANG
en_US.UTF-8Any help is very, very much appreciated. Thanks.

you didn't look hard enough, this is a faq...
there three options:
1) change the system encoding by setting LANG or LC_CTYPE environment variables... assuming you use bash:bash$ export LC_CTYPE=en_GB.iso88591 you can check the available locales with locale -a ... pipe it to grep en_GB to filter out the non-british english locales
-OR-
2) change the java default encoding from the command line with -Dfile.encoding... run with$ java -Dfile.encoding=ISO-8859-1 yourclass-OR-
3) set the encoding from within the program with OutputStreamWriter, or use a PrintStream that has the encoding set..PrintStream out = new PrintStream(new FileOutputStream(FileDescriptor.out), true, "ISO-8859-1");
System.setOut(out);see also the internationalization tutorial & the javadoc of the related classes....

Labview support for ISO 8859-5

HI,
does Labview support ISO 8859-5 character sets?
If yes, then how do i change the default character set in Labview from ASCII to ISO 8859-5?
If no, then which is the simplest way to display russian characters in Labview 6.1 (Labview 6.1 on SuSE LINUX)
Thanks and Regards,
Pavitra

Hi Pavitra,
There is a very easy way to do that in Windows. Start>Settings>Regional and Language Options. Make sure Russian is included as an input language language on the language tab, as well as on the advanced tab where you can specify the language for non-unicode programs.
I have attached a screenshot that demonstrates cyrillic fonts in LabVIEW. The example is done with Bulgarian font, but it should work the same way with Russian. As you can see I have also specified Arial CYR as my font for the front panel and the block diagram.
Try to use the same logic for a Linux system.
Hope that helps!
Kalin T.
National Instruments
Attachments:
cyrillic.jpg ‏51 KB

=?iso-8859-1?Q?Re:_Charlas_de_Photoshop._La_iluminaci=F3n_5=AA_Parte._El_?= =?iso-8859-1?Q?proceso?=

This is a multi-part message in MIME format.
------=_NextPart_000_0037_01C69D19.C832BF30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Fe de erratas:
En la parte 1=AA escrib=ED un 'fosforo' sin acentuar, as=ED
no enciende.
Histograma lo escribo con may=FAscula inicial o en
min=FAsculas, =
gilipollez m=EDa para distinguir entre el concepto y la
herramienta.
En la 2=AA parte : yo que me quejaba de la falta de
ortograf=EDa del =
programa con la palabra 'Imagen', caigo tambi=E9n en no
acentuarla. Ya =
sabes, el asno es el =FAnico animal que no tropieza donde el
hombre, o =
algo as=ED. je,je
En la 3=AA parte hay una boutade: el palabro 'paspart=FAs'
que utilizan =
ls pintores para referirse a los espacios que rodean a la
im=E1gen del =
cuadro y la separan del marco. Es una adaptaci=F3n de la
expresi=F3n =
francesa 'pass=E9 par tout'.
En la 5=AA parte hay un 'abr=E1' al que se le ha ca=EDdo la
hache. =
Deber=EDa decir 'habr=E1'.
Tambi=E9n hay un 'm=E1s centrado e dentado que antes', soy
muy =
siciliano.
Perd=F3n por mi mal verbo y mis palabros, seguro que si te
fijas =
encuentras m=E1s fallos, y esto solo me pasa por releer lo
que escribo.
Salu2
`8=AC}
Juan Muro
------=_NextPart_000_0037_01C69D19.C832BF30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML xmlns:o =3D
"urn:schemas-microsoft-com:office:office" xmlns:st1 =
=3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912"
name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Fe de=20
erratas:</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">En la parte =
1=AA escrib=ED=20
un 'fosforo' sin acentuar, as=ED no
enciende.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Histograma lo =
escribo=20
con may=FAscula inicial o en min=FAsculas,
gilipollez m=EDa para =
distinguir entre=20
el concepto y la herramienta.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">En la 2=AA =
parte : yo que=20
me quejaba de la falta de ortograf=EDa del programa con la
palabra =
'Imagen', caigo=20
tambi=E9n en no acentuarla. Ya sabes, el asno es el =FAnico
animal que =
no tropieza=20
donde el hombre, o algo as=ED. je,je</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">En la 3=AA =
parte hay una=20
boutade: el palabro 'paspart=FAs' que utilizan ls pintores
para =
referirse a los=20
espacios que rodean a la im=E1gen del cuadro y la separan del
marco. Es =
una=20
adaptaci=F3n de la expresi=F3n francesa 'pass=E9 par
tout'.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">En la 5=AA =
parte hay un=20
'abr=E1' al que se le ha ca=EDdo la hache. Deber=EDa decir =
'habr=E1'.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Tambi=E9n hay =
un 'm=E1s=20
centrado e dentado que antes', soy muy
siciliano.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Perd=F3n por =
mi mal verbo=20
y mis palabros, seguro que si te fijas encuentras m=E1s
fallos, y esto =
solo me=20
pasa por releer lo que escribo.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Verdana">Salu2</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Verdana">`8=AC}</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Juan=20
Muro</SPAN></DIV></BODY></HTML>
------=_NextPart_000_0037_01C69D19.C832BF30--

This is a multi-part message in MIME format.
------=_NextPart_000_0037_01C69D19.C832BF30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Fe de erratas:
En la parte 1=AA escrib=ED un 'fosforo' sin acentuar, as=ED
no enciende.
Histograma lo escribo con may=FAscula inicial o en
min=FAsculas, =
gilipollez m=EDa para distinguir entre el concepto y la
herramienta.
En la 2=AA parte : yo que me quejaba de la falta de
ortograf=EDa del =
programa con la palabra 'Imagen', caigo tambi=E9n en no
acentuarla. Ya =
sabes, el asno es el =FAnico animal que no tropieza donde el
hombre, o =
algo as=ED. je,je
En la 3=AA parte hay una boutade: el palabro 'paspart=FAs'
que utilizan =
ls pintores para referirse a los espacios que rodean a la
im=E1gen del =
cuadro y la separan del marco. Es una adaptaci=F3n de la
expresi=F3n =
francesa 'pass=E9 par tout'.
En la 5=AA parte hay un 'abr=E1' al que se le ha ca=EDdo la
hache. =
Deber=EDa decir 'habr=E1'.
Tambi=E9n hay un 'm=E1s centrado e dentado que antes', soy
muy =
siciliano.
Perd=F3n por mi mal verbo y mis palabros, seguro que si te
fijas =
encuentras m=E1s fallos, y esto solo me pasa por releer lo
que escribo.
Salu2
`8=AC}
Juan Muro
------=_NextPart_000_0037_01C69D19.C832BF30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML xmlns:o =3D
"urn:schemas-microsoft-com:office:office" xmlns:st1 =
=3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912"
name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Fe de=20
erratas:</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">En la parte =
1=AA escrib=ED=20
un 'fosforo' sin acentuar, as=ED no
enciende.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Histograma lo =
escribo=20
con may=FAscula inicial o en min=FAsculas,
gilipollez m=EDa para =
distinguir entre=20
el concepto y la herramienta.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">En la 2=AA =
parte : yo que=20
me quejaba de la falta de ortograf=EDa del programa con la
palabra =
'Imagen', caigo=20
tambi=E9n en no acentuarla. Ya sabes, el asno es el =FAnico
animal que =
no tropieza=20
donde el hombre, o algo as=ED. je,je</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">En la 3=AA =
parte hay una=20
boutade: el palabro 'paspart=FAs' que utilizan ls pintores
para =
referirse a los=20
espacios que rodean a la im=E1gen del cuadro y la separan del
marco. Es =
una=20
adaptaci=F3n de la expresi=F3n francesa 'pass=E9 par
tout'.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">En la 5=AA =
parte hay un=20
'abr=E1' al que se le ha ca=EDdo la hache. Deber=EDa decir =
'habr=E1'.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Tambi=E9n hay =
un 'm=E1s=20
centrado e dentado que antes', soy muy
siciliano.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Perd=F3n por =
mi mal verbo=20
y mis palabros, seguro que si te fijas encuentras m=E1s
fallos, y esto =
solo me=20
pasa por releer lo que escribo.</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Verdana">Salu2</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Verdana">`8=AC}</SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:
Verdana">Juan=20
Muro</SPAN></DIV></BODY></HTML>
------=_NextPart_000_0037_01C69D19.C832BF30--

Creating XML-files in ABAP with format ISO-8859-1 after the use of unicode

Hello,
We have a problem with XML-files created in z_abap-programma.
Before the use of unicode the XML-file was of the format: ISO-8859-1.
After the introducting of unicode the format is UTF-16.
In the abap-program we are using:
        CALL TRANSFORMATION xls-program
         SOURCE t_vbak = it_vbak
         RESULT XML xmlstring.
        CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
          EXPORTING
            text     = xmlstring
          IMPORTING
            buffer   = lx_xml_as_string.
        CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
          EXPORTING
            buffer        = lx_xml_as_string
          IMPORTING
            output_length = li_xml_size
          TABLES
            binary_tab    = ltb_xml_table.
        CALL METHOD cl_gui_frontend_services=>gui_download
          EXPORTING
            bin_filesize = li_xml_size
            filename     = lc_filename
            filetype     = 'BIN'
          CHANGING
            data_tab     = ltb_xml_table
          EXCEPTIONS
            OTHERS       = 24.
Is it prossible to create the XML-file with the format ISO-8859-1 after the unicode, please can you explane how to solve this problem.
Regards,
Theo Pijlman

hi theo,
did you read my thread i wrote some days before ? have a look in my sample coding find   " if_ixml_encoding ..... " there you can set the encoding of character .
greetz
tony
thread:
Re: abap to xml
SAP Explanation for Interface if_ixml_encoding :
http://help.sap.com/saphelp_nw04/helpdata/de/bb/5766a6dca511d4990b00508b6b8b11/content.htm

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);

I keep trying to load firefox 6 and keep getting this error - The requested URL /cse?cx=partner-pub-3540673482024757:xbhdw8hkfz5&ie=ISO-8859-1&q=&sa=Search was not found on this server. That's all we know. in English

I keep trying to load firefox 6 and keep getting this error - The requested URL /cse?cx=partner-pub-3540673482024757:xbhdw8hkfz5&ie=ISO-8859-1&q=&sa=Search was not found on this server. That’s all we know. in English

Bookmark and use this;
Download the '''[https://addons.mozilla.org/en-US/firefox/addon/searchreset/ Mozilla Search Reset]''' {web link}
This add-on is very simple: on installation, it backs up
and then resets your search preferences and home page
to their default values, and then uninstalls itself. This
affects the search bar, URL bar searches, and the home page.
Sometimes a problem with Firefox may be a result of malware installed on your computer, that you may not be aware of.
You can try these free programs to scan for malware, which work with your existing antivirus software:
* [http://www.microsoft.com/security/scanner/default.aspx Microsoft Safety Scanner]
* [http://www.malwarebytes.org/products/malwarebytes_free/ MalwareBytes' Anti-Malware]
* [http://support.kaspersky.com/viruses/disinfection/5350 Anti-Rootkit Utility - TDSSKiller]
* [http://general-changelog-team.fr/en/downloads/viewdownload/20-outils-de-xplode/2-adwcleaner AdwCleaner] (for more info, see this [http://www.bleepingcomputer.com/download/adwcleaner/ alternate AdwCleaner download page])
* [http://www.surfright.nl/en/hitmanpro/ Hitman Pro]
* [http://www.eset.com/us/online-scanner/ ESET Online Scanner]
[http://windows.microsoft.com/MSE Microsoft Security Essentials] is a good permanent antivirus for Windows 7/Vista/XP if you don't already have one.
Further information can be found in the [[Troubleshoot Firefox issues caused by malware]] article.
Did this fix your problems? Please report back to us!

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.

(OT) Programa =?ISO-8859-1?Q?cibercaf=E9?=

Similar Messages

Maybe you are looking for