German special characters not displaying on page instead of that Question marks displayed

when i submit form,i need to send a mail with filled data.Here Suppose user entered german special characters.I am getting Question marks instead of ä,Ä,ö,Ö,ü,Ü,ß. I have used meta tag like
<meta http-equiv="content-type" content="text/html;charset=utf-8" />.But i am getting fine characters with IE and Chrome.I am using FireFox 3.6.16 english.

Hello core team,
Thanks a lot!!!!
i m not only the person to use html form.So many non technical persons using the same. how can i tell to all persons regarding changing character encoding. i need some permenant solution,

Similar Messages

  • German Special Characters not displayed correctly in RTF  using code

    Hi ,
    In my code we are using webdynpro method
    WDResourceFactory.createResource(
    byte[] data, String resourceName,WDWebResourceType
    Type)
    Here in our code we are implementing this as
    ITemplateElement templateEl = wdContext.currentTemplateElement();
    WDResourceFactory.createResource(
    templateEl.getReportData(),
    reportName.substring(0, reportName.lastIndexOf('.')),
    WDWebResourceType.RTF); reportName.lastIndexOf('.')),
    Here templateEl.getReportData() returns a set of bytes which has some
    german special characters.
    We are generating the Bytes using String.getByes(),Just before
    String text = new String(in);
    collector.putBusinessObject(boName, bo);
    reportDocTemplateParser(collector, text);
    collector.removeBusinessObject(boName);
    String generatedText = collector.generateRTF();
    out = (null != generatedText) ? generatedText.getBytes() : null;
    The out put is the if i am giving a word with german special characters for eg:
    Betriebsübersichten it first gets converted to bytes and then passes through method WDResouseFactory.createResourse(.....) which creates an RTF file and finally in the RTF file it appears as Betriebsbbersichten the special character is not displayed correctly.
    i came to knw that while converting into bytes we have to make it RTF supported encoding.ie for eg generatedText.getBytes('cp1252').i even tried with other charactersets like ISO-8859,cp1253 and so on but none of them worked.
    It would be really great if you could suggest the needful.
    Thanks and Regards
    Neeta

    I soved this by using get_data function of response object. Then converting this into ISO-8859-1 charset.
    See code below.
    DATA :  lv_encoding   TYPE abap_encoding,
              lv_conv       TYPE REF TO cl_abap_conv_in_ce,
              lv_x_string   type xstring.
      lv_x_string = pv_http_client->response->get_data( ).
        lv_encoding = '1100'.
        lv_conv = cl_abap_conv_in_ce=>create(
                              encoding = lv_encoding
                                 input = lv_x_string ).
        lv_conv->read( IMPORTING data = pv_result ).

  • Smart Web Printing does not show/print german special characters (äöü)

    I have installes Smart Web Printing on my computer with WIndows 7. I do use a german localization. Selected text is shown and printed correct, except german special characters ä ö ü. They are even not shown correctly in the menues of the application.

    Response to cor-el suggestions:
    I tried what you suggested as far as checking the theme (it's "Default 8.0") and deleting the sessionstore files (there was one .js file, one -1.js file and one .bak file). I still have the same slow response problems (especially typing, it has gone dead on me for a short time twice while typing this replay so far, now a third time) and lost of headers and trailers and some data.
    I did the suggested actions three times just to make sure that I was doing them correctly. On the first try, the sessionstore.js and sessionstore-1.js was more than twice the size of sessionstore.bak. Since doing what was suggested, the sessionstore.js and sessionstore.bak are, I believe, the same size. I did not write down their size is why I am not certain.
    The printing problem appears to only be with one website which is an investment website which I would prefer not to document here. I print from this website each weekday and I have confirmed that the printing problem started when the upgrade to version 8.0 occurred.
    I need a solution to this or I am going to either go back to IE (Ugh!) or find another browser. The typing delays are an extreme annoyance since I do lots on the Internet including a lot of emailing. The delays also involve the buttons to select functions within a website.
    Is there a way to get back to the version previous to version 8.0?

  • German special characters are not returned from catalog

    When the german special characters are part of the descrition of the article from the the catalog (external). ( reaching catalog from PM order components screen)
    It returns '#' in place german special characters ö ('Umlet') . This is because of the initial charset from the HTML page. How do we get the correct charset of the loaded HTML page.
    But when we execute the same through WTS the german characters are correctly returned but charset is incorrect. Can someone help me to resolve this?

    Hi ,
    Can you pls check the customization OCI interface Convert of HTML fields to SAP Fields where in you maintained the text, which is inturn mapped to conversion module in the customization for example IOCI_DESCRIPTION_W.
    Regards
    Satish

  • Problem with german special characters in APEX

    Hi,
    we have a problem with all the special characters in german language in our Application.
    APEX version 3.1.0.00.32 is installed on a oracle database 9.2.0.6.0
    The nls_characterset of the database is: American_America.WE8ISO8859P1
    We have modified the wdbsvr.app file on our HTTP-Server like it's shown in the installationguide for APEX and have set the nls_lang parameter to American_America.AL32UTF8.
    If I look at the source code of the html-pages of our application, there are already the following settings in the header of every page:
    meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"
    With this settings all the german special characters like ä ö ü are not shown correctly in the browser.
    What can I do that the pages are shown correctly?
    Thanks for help!

    Hi Petra,
    ok, so my guess was correct. So the solution is to set the charset attribute in the HTML header to "charset=UTF-8". This is actually the way it should be. But I'm wondering why it is not in your case? Are you using a custom template for the page(s) in question where the charset attribute is set to a custom value? The meta tags in the HTML header are usually set by/through the #HEAD# substitution string in the header definition section of the page template, cp. one of the page templates in Shared Components --> Templates. And as far as I know you are not able to change this substitution string, you can only switch the inclusion on/off with the option "Include Standard CSS and JavaScript" in each page definition. (I might be mistaken, though, I'm quite new to APEX...)
    Regards
    Frank

  • German special characters..

    I just got my first iPod this afternoon and am now in the process of uploading all my CDs into iTunes. However, some of my files require typing German special characters (umlauted vowels). I'm using a PC and the special character codes for PCs are not working in iTunes. I'm stumped!
    Anyone know how to access special characters? They seem to exist, since certain albums I've uploaded which have German titles are picking up umlauts.
    TIA....
    Bob

    Trevor,
    If the client application attempts to store a character such as the euro that is not defined in the database character set a replacement is selected and the clients representation will be lost. If the client uses a different code page to the databases character set the symbol can still be stored as long as both code pages have a code. The client must also have the character set component of NLS_LANG set to the client's character set.
    The solution is in finding a correct combination of the MS Windows code page that match the chosen Oracle client character set encoding for that character. The problems are with the client PC settings, and the resolution could be time consuming when looking for the available OS code pages and font information. You could find some information on code pages at the following Microsoft site:
    http://www.microsoft.com/typography/unicode/cscp.htm

  • German Special Characters in XSTRING to STRING conversion

    Hi Experts,
    I have a CSV file (created from a Windows Excel file) with German Special Characters (e.g. 'ä', 'Ä') and I am trying to read this into ABAP internal tables. By using the THTMLB tag 'thtmlb:fileUpload' I get an XSTRING and I am trying to convert this into STRING. However, wheny trying to do this I get an exception 'CX_SY_CONVERSION_CODEPAGE'.
    This is my coding:
      data: conv   type ref to cl_abap_conv_in_ce.
      conv = cl_abap_conv_in_ce=>create( input = lr_upload->file_content ).
      conv->read( importing data = lv_content ).
    Note: lr_upload is my XSTRING object from the file upload, lv_content is a STRING.
    In the CSV file the German special characters look fine and the SAP system is a Unicode system, but it seems like there are some problems with the conversions somehow. Any ideas from the experts?
    Thanks a lot and Regards,
    Jens

    As you mention a csv file I'm wondering if your encoding is wrong: I.e. when you create your instance of cl_abap_conv_in_ce you don't specify the encoding of your source hex string, so that means the default encoding is used, which should be UTF-8 in your case. So if your csv file is not encoded in UTF-8, specify the correct encoding in the create method and see if that helps.
    Depending on how you get the file contents you might actually be able to combine the file retrieval with the conversion in one step. E.g. if the file is read from the application server you could specify the used code page via [open dataset ... in legacy text mode ... code page|http://help.sap.com/abapdocu_70/en/ABAPOPEN_DATASET_MODE.htm#&ABAP_ALTERNATIVE_4@4@]. Similarly method gui_upload of class cl_gui_frontend_services also allows you to specify a code page.
    If all of this doesn't help, post some further details on your file (e.g. sample content & encoding) and possibly add some further details from the exception you're getting. As you mention a Unicode system it basically means that we should be able to convert all characters without any problem as long as we specify the correct source code page.
    Cheers, harald

  • TCS 3.0: Anchored Frames contain callouts with german special characters Conversion to RH nok

    Hi all,
    I have Frame documents, which contain anchored frames with callouts. The callouts are created with Frame and contain german special characters like ä,ö,ü. These characters are not converted correctly.
    Thanks for help.
    Regards,
    Rainer

  • Unity Connection 8.6 LDAP or CUCM Import with german special characters called "Umlaut": ä, ö, ü

    Hi,
    for  jabber 9.1 integration i sync'ed all users at Callmanager, Presence and  Unity to our LDAP (MS AD). with CUCM and Presence (both 8.6.x), it  works fine, just Unity Connection sync the Users from AD, but i cannot import Users  with german special characters ä, ö, ü  (i.E. German Name in LDAP-su: Müller).
    Jabber  9.1 need for Voicemail Integration the AD Authentication. Know  somebody, if there is an Workaraound or Fix ?
    This is a general issue, with or without Jabber, with sync directly from AD, or indirectly through CUCM (sync'ed with AD)
    thx and regards
    Jacky

    I located an identical defect (CSCts28455) that was closed as unreproducible. The defect references CSCtj73444 "Add support for UTF-8 password to LDAP and RADIUS/MSCHAP" which is added to 8.4.2 with the recommendation of RADIUS/MSCHAP or LDAP only for international character support. It would make sense to go to the latest in your current train (ie: 8.4.4.1.ED) and see if the issue remains. What you want to do appears to be supported.
    Matthew

  • Mysql problem with german special characters

    hi,
    I wrote a software and it worked quite good, but after I installed it on a new machine with j2se 1.4 I've problems with the german special characters.
    this code works good on the old machine (jdk 1.3.1) and prints the wanted characters like �,�,�.
    Class.forName("org.gjt.mm.mysql.Driver").newInstance();
    java.sql.Connection conn;
    conn = DriverManager.getConnection("jdbc:mysql://localhost/testdb?user=testuser&password=xxxx");
    Statement s = conn.createStatement();
    ResultSet r = s.executeQuery("select something from testtb where id='1'");
    r.first();
    System.out.println( r.getString(1) );
    but on the new machine (j2se 1.4) I only receive the character ?.
    I updated my org.gjt.mm.mysql to the current MySQL Connector/J 3.0.9 and added
    conn = DriverManager.getConnection("jdbc:mysql://localhost/testdb?user=testuser&password=xxxx&useUnicode=true&characterEncoding=ISO-8859-1");
    but I've got still the same problem.
    Thanks in advance
    Markus

    with "wanted characters like �,�,�"
    I meant: like &#x00E4;,&#x00FC;,&#x00F6;

  • Not able to get rid of a Question mark in the Dock

    A friend got stuck with a Question Mark in the Dock of his 4 year old iMac that was linked to an app not compatible anymore with his latest 10.8.2 version ( guess it was a Power PC app, before Mountain Lion, he was still on Leopard ). He apparently deleted the app and some dependencies manually ( instead of using App Cleaner & Co. ) and now whenever he is hovering over that Question Mark, even before being even able to pull it out from the Dock, the screen flashes up white and the Finder resets.
    Is there a way to access the Dock through an element of his user library to get rid of that Mark, or even through a Terminal command ( not that I like to delve in there, but Terminal commands have helped me personally quite often ) ?
    Does the Dock have a dedicated place in the Library's User Folder ? Couldn't find anything on my own Mac.
    Thanks for any clue ....

    Right clicking on it is not even an option, just hovering over it seems to induce a "nuclear" reset of the whole desktop and graphic card on the iMac.
    Have meanwhile found a possible solution by erasing the dock preference file in the user/library/preferences folder to reset the dock to it's default state. Will try this out through a Skype conversation with that Buddy.
    Was seen here :
    https://discussions.apple.com/message/16447109#16447109
    Thank you for stepping in. Good to know that people are still willing to help in this community.
    Greetz to the UK from France

  • HT1721 My computer turns on and displays a folder icon with a question mark in it

    What should i do if my computer's screen is grey and displays a folder icon with a question mark in it?

    http://support.apple.com/kb/TS1440
    Not covered in the article is a possible hard drive failure.

  • My notebook will not start up----I see only a question mark in a small folder.  What to do?

    My notebook will not start up----I see only a question mark in a small folder.  What to do?

    Booting From An OS X Installer Disc
    1. Insert OS X Installer Disc into the optical drive.
      2. Restart the computer.
      3. Immediately after the chime press and hold down the "C" key.
      4. Release the key when the spinning gear below the dark gray Apple
          logo appears.
      5. Wait for installer to finish loading.
    How to Perform an Archive and Install
    An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
    1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger, Leopard or Snow Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
    3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
    4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
    5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
    6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

  • I installed the window 7 os in to my mac book pro. after that the partition is not supported and then the folder with question mark flashing on my screen. plaese helf me what to do next to resume the mac os x?

    i installed the window 7 ultimate OS in to my mac book pro. after that the partition is not supported and then the folder with question mark flashing on my screen. plaese helf me what to do next to resume mac mac os x?

    Assuming that you tried to install Win 7 in bootcamp.
    Power on the machine and press and hold the "option" key when you hear the bong sound.
    Select the Macintosh HD icon and press "return" or just click on the icon.
    Once booted into OS X go to System Preferences and select the Startup Disk icon and configure startup to use the Macintosh HD.

  • I upgraded the OS on my iMac to Lion from the App store; and after installation, it restarted and now the operating system won't start up.... it keeps displaying the apple/folder with a question mark and a circle with a line through it! Please help!

    I upgraded the OS on my iMac to Lion from the App store; and after installation, it restarted and now the operating system won't start up.... it keeps displaying the apple/folder with a question mark and a circle with a line through it! Please help!

    Try starting up with your Snow Leopard DVD and see if the disk can be repaired. Once you are at the installer screen go to the Utilities Menu and choose Disk Utility and choose repair disk. You might also want to try Diskwarrior.
    Hope this helps.
    Ben

Maybe you are looking for