BARCODES 128 ENCODING PROBLEM

We are using IDAutomation tools in order to print barcodes in our forms.
We are using the IDautomation barcode font and the special PLL for reports developer.
The system we are using is Oracle 11.5.10.2 and UTF8 as our NLS_LANG.
The problem is that we need BARCODE 128 standard for the reports which means that there is an encoding function which we sent a string to and it prints an encoded barcode string as an output.
When I try to run the report locally on my computer which uses
NLS_LANG="AMERICAN_AMERICA.IW8MSWIN1255" it runs ok and when i try to use the print layout in reports developer it bring the correct barcode.
But, when I try to run the report from the application in the server, the barcode prints invalid.
After some investigations we found:
a. the fonts are installed correctly.
b. the encoding function of the 128 barcode brings different results when run on UTF8 and on AMERICAN_AMERICA.IW8MSWIN1255.
It seems that the problem is not with the barcodes font rather than with the
function that calculates and encodes the 128 barcode.
The same function bring different output when is it running locally and when is
running on the server. The function we are running is the standare one taken
from the IDAutomation PLL for oracle applications and report developer.
Since it is a common PLL used by most of the companies, we think it is a
problem related to the NLS_LANG we are running.
I tried to change the string output of the function and find the ASCII
characters it outputs.
When trying to encode into barcode the string "1234567890" it brings locally
the output:
chr(205)chr(205)chr(44)chr(66)chr(88)chr(110)chr(122)chr(117)chr(206). This is
the right output which was supposed to be.
Butm, when trying to run the encoding function on the server with the UTF-8
NLS_LANG it brings the following INVALID
output:chr(44)chr(44)chr(66)chr(88)chr(110)chr(122)chr(68)
My guess is that some of the ASCII characters in the right output are not
supported in the UTF8 NLS_LANG environment.
Thanks alot,
Please advise

Thanks for your reply
Yes, i know the BIG5 is for Traditional Chinese and japansese is using like Shift-JIS or EUC.
So when i try to post japanese in a BIg5 web page, i think it's normal that i can't see it in BIG5 encoding.
But then i change the Safari default decoding to BIG5 HKSCS, the japanese appers! At the same time i can see the traditional chinese too!
And if i use Firefox, i can both see the japanese and chinese at the default BIG5 encoding.
So i simple think maybe safari translate my japanese into BIG5 HKSCS,not Shift-JIS. But if i use Firefox, i can get the same result with only BIG5 encoding, not BIG5 HKSCS. So i am just wondering why it's different between Safari and Firefox with the same BIG5 encoding.
Following is a example URL
It's a MAC discussing froum with BIG5 encoding in Taiwan.
http://ubb.frostyplace.com.tw/viewtopic.php?t=19162
It's a froum topic posted by me. I input some japanese into this topic
If you browse this page with Safari BIG5 encoding, you can see a lot of question mark instead of the original japanese word that i and other people posted.
But if you change the encoding to BIG5 HKSCS, the japanese appears. And if you using Firefox with BIG5 encoding, the japanese appears too.
So is it someing wrong with Safari's BIG5 encoding or some other reason makes this happen?

Similar Messages

  • Help! Datamatrix Encoding Problems

    Hello,
    We are using custom script to assign text value to datamatrix barcode for encoding. The following works well ("this" refers to barcode object)
    this.rawValue ="Hello WOrld";
    I can decode the datamatrix code generated with the above code in the reader with a scanner.
    The following has problem (it is generating datamatrix code in the reader but i cannot decode using a scanner):
    this.rawValue = DOB.rawValue;
    In order to debug the above I used the following:
    this.rawValue=DOB.rawValue;
    debugtext.rawValue = this.rawValue;
    where debugtext is a text field to display what value the barcode object is holding - the text field is displaying the value correctly.
    This looks very weird. Thanks in advance if you have experienced anything like above and share your observation.

    You may have misunderstood my response to the last note. The $1 to $5 per form per transaction is how much money you would typically SAVE compared to other methods of gathering information from printed forms. For the cost of the Adobe LiveCycle software you will need to consult your local Account Manager.
    In regards to your use-case you really don't need Barcoded Forms unless the user is going to be printing the form and submitting the actual paper.
    If you would like to provide the user with a PDF to enter data within the browser you can do that already. You can also do an HTTP POST back to your server directly from within the browser (and the Reader plug-in) without any additional software.
    It is only when you want to give your users the ability to fill-in and print off-line (with barcode forms) or save off-line and submit outside the browser that you will need additional software.

  • Encoding problems in email while on Windows Mail app

    Hello.
    I have a question concerning email and encoding problems in the Windows Mail App in Windows 8.1.  I have encountered a problem with an email I received, while reading, I see strange ASCII characters in one email.  I have never encountered it in
    my web browsers nor Gmail, just the Mail App.
    I was referred to come here when I had asked a similar question there:
    http://answers.microsoft.com/en-us/windows/forum/windows8_1-ecoms/strange-foreign-ascii-characters-appearing-in/911f8a44-c302-4fa1-bcaa-3297b32d9120
    I don't know which forum to go to so I picked here.
    Is there any way that it can be resolved.  I tried to troubleshoot, nothing worked; I even synched, to no avail.
    I look forward to a response.
    JB

    Hi JB,
    The responder on answers was a bit confused. The MSDN forums are for developers to discuss writing their own apps. We cannot help with problems using Windows or its built-in apps.
    If the folks on answers cannot help then you may need to open a support incident. See
    http://support.microsoft.com , or the folks on answers may be able to direct you to the specific page for the Windows Mail app.
    --Rob

  • Encoding problem while reading binary data from MQ-series

    Dear all,
    we are running on 7.0 and we have an encoding problem while reading binary data from MQ-series. Because we are getting flat strings from queue we use module "Plain2ML" (MessageTransformBean) for wrapping xml-elements around the incoming data.
    The MQ-Series-Server is using CCSID 850, which we configured in connection parameters in communication channel (both parameters for Queuemanager CCSID and also CCSID of target).If there are special characters in the message (which HEX-values differ from codepage to codepage) we get errors in our adapter while executing, please see stack-trace for further analysis below.
    It seems to us that
    1. method ByteToCharUTF8.convert() expects UTF-8 in binary data
    2. Both CCSID parameters are not used anyway in JMS-adapter
    How can we solve this problem without changing anything on MQ-site?
    Here is the stack-trace:
    Catching com.sap.aii.af.mp.module.ModuleException: Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
        at com.sap.aii.af.modules.trans.MessageTransformBean.throwModuleException(MessageTransformBean.java:453)
        at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:387)
        at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
        at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
        at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
        at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:84)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter(ConvertBinaryToXiMessageFilter.java:304)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.ConvertJmsMessageToBinaryFilter.filter(ConvertJmsMessageToBinaryFilter.java:112)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:87)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:123)
        at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filter(TxManagerFilter.java:59)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.DynamicConfigurationFilter.filter(DynamicConfigurationFilter.java:72)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.PmiAgentFilter.filter(PmiAgentFilter.java:66)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.InboundCorrelationFilter.filter(InboundCorrelationFilter.java:60)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.JmsHeadersProfileFilter.filter(JmsHeadersProfileFilter.java:59)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageInvocationsFilter.filter(MessageInvocationsFilter.java:89)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.JarmMonitorFilter.filter(JarmMonitorFilter.java:57)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.ThreadNamingFilter.filter(ThreadNamingFilter.java:62)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.SenderChannelImpl.doReceive(SenderChannelImpl.java:263)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.receive(ChannelImpl.java:437)
        at com.sap.aii.adapter.jms.core.connector.MessageListenerImpl.onMessage(MessageListenerImpl.java:36)
        at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:399)
        at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:904)
        at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4249)
        at com.ibm.msg.client.wmq.v6.jms.internal.SessionAsyncHelper.run(SessionAsyncHelper.java:537)
        at java.lang.Thread.run(Thread.java:770)
    Caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
        at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:714)
        at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:538)
        at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:528)
        at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:471)
        at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:364)
        ... 36 more
    Caused by: sun.io.MalformedInputException
        at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:270)
        at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
        at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
        at java.io.InputStreamReader.read(InputStreamReader.java:208)
        at java.io.BufferedReader.fill(BufferedReader.java:153)
        at java.io.BufferedReader.readLine(BufferedReader.java:316)
        at java.io.LineNumberReader.readLine(LineNumberReader.java:176)
        at com.sap.aii.messaging.adapter.Conversion.convertPlain2XML(Conversion.java:310)
        at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:709)
        ... 40 more
    Any ideas?
    Kind regards, Stefan

    Hi Stefan,
    for the first MTB now we are using only one parameter: Transform.ContentType = text/plain;charset="ISO-8859-1"
    The second MTB, which does the XML-Wrapping, is configured like this:
    Transform.Class = com.sap.aii.messaging.adapter.Conversion
    Transform.ContentType = application/xml
    xml.conversionType = SimplePlain2XML
    xml.fieldNames = value
    xml.fieldSeparator = §%zulu§%
    xml.processFieldNames = fromConfiguration
    xml.structureTitle = payload
    Both CCSID configuration parameters from the "Source"-Tab we've set to 850.
    Now, we don't get an error anymore - sun.io.malformedInputException - , but, unfortunately, now special character conversion succeeded (we need an "ß" and we get an ISO-HEX-E1 -> á).  E1 is (different from ISO) an "ß" in 850.
    Any ideas?

  • Encoding problem in call-back to hook URL (post parameters)

    Hello all,
    I'm encountering a character encoding problem while retrieving the content of the shopping basket from one of our provider.
    After the POST request is made by the provider to our system using the hook url, when debbuging I can see that some special characters are represented with the sign '#' (after the call the ITS_IMPORT_CONTEXT).
    In our case using the parameter http_content_charset with various values, including UTF-8, did not change the result.
    Inspecting the HTTP traffic has highlighted the following: the encoding received from the provider is related to UTF-8, but while we are expecting the hexadecimal values, we are receiving the "Unicode code points", which are not recognized by our SAP system. For more details look at the UTF-8 encoding table found here and compare the values under column "Unicode code point" with the one under column "UTF-8 (hex.)".
    As an example, for the character 'é', we are receiving the value "%E9" (the code point) instead of receiving the the hexa value : "%C3%A9".
    Do you have any idee if this can be corrected on our side or if the provider must addapt the way it's sending the POST parameters?
    Many thanks in advance for you help.
    Best regards,
    Jerome.

    Hi Jason,
    Indeed I had contacted the provider and informed them about the encoding problem and the fact that passing the parameter http_content_charset had no effect on the sent back encoding.
    They have taken into account my request and have changed the encoding used during the request to the HOOK_URL.
    Thanks to all of your for your help.
    Regards,
    Jerome.

  • Character encoding problem using XSLT and Tomcat on Linux

    Hi,
    I have an application running on a Tomcat 4.1.18 application server that applies XSLT transformations to DOM objects using standard calls to javax.xml.transform API. The JDK is J2SE 1.4.1_01.
    It is all OK while running on a development enviroment (which is Windows NT 4.0 work station), but when I put it in the production enviroment (which is a red hat linux 8.0), it comes up with some kind of encoding problem: the extended characters (in spanish) are not shown as they should.
    The XSL stylesheets are using the ISO-8859-1 encoding, but I have also tried with UTF-8.
    These stylesheets are dynamicly generated from a JSP:
    // opens a connection to a JSP that generates the XSL
    URLConnection urlConn = (new URL( xxxxxx )).openConnection();
    Reader readerJsp = new BufferedReader(new InputStreamReader( urlConn.getInputStream() ));
    // Gets the object that represents the XSL
    Templates translet = tFactory.newTemplates( new StreamSource( readerJsp ));
    Transformer transformer = translet.newTransformer();
    // applies transformations
    // the output is sent to the HttpServletResponse's outputStream object
    transformer.transform(myDOMObject, new StreamResult(response.getOutputStream()) );Any help would be appreciated.

    Probably you need to set your LANG OS especific environment variable to spanish.
    Try adding this line:
    export LANG=es_ES
    to your tomcat/bin/catalina.sh, and restart tomcat.
    It should look like this:
    # OS specific support.  $var _must_ be set to either true or false.
    cygwin=false
    case "`uname`" in
    CYGWIN*) cygwin=true;;
    esac
    export LANG=es_ES
    # resolve links - $0 may be a softlink
    PRG="$0"
    .(BTW, keep using ISO-8859-1 encoding for your XSL)
    HTH
    Un Saludo!

  • C# GWTypeLibrary - AddressBook Entry encoding problem

    Hello.
    I am using C#(Visual Studio 2005) and GroupWareTypeLibrary to develop for
    GroupWise Client 7.0.
    Working with AddressBook I have faced some problems.
    I am getting display name (AddressBookEntry.DisplayName) for all entries
    of AddressBook. Almost all DisplayNames are correct but there are some
    problems with two or three of them (there are some illegal char displayed
    instead of some char of real user DisplayName). I think it is local
    encoding problem bekause I see the same problem with the same users in
    GroupWise Client AddressBook.
    I thought display name is building not correctly but when I tried to get
    these users first and last name I have got the same problem with encoding
    in them.
    Please advice how to decide this problem.
    Regards,
    Alex.

    Sounds like a GW Client problem and not an API problem if you see it in the client address book. Technical Support should be able to help you.
    Glade,
    Novell Developer Support

  • Encoding Problems with WRT300N V2

    Hello guys,
    i have following problem:
    I have a WRT300n Router and it seems to have problems with WPA2 encoding. I have 2 different deviceses (a SMC Ethernet Bridge and a PS3) trying to connect to my Linksys wireless router. No chance in WPA2 mode but when I try in WEP-Mode, both devicec can connect to it.
    Are there known encoding problems?
    Any idea what i can do?

    It is able to use. But my router always drops the connection. WEP is no problem, but ... what about low security and Wirless N is not enabled ??

  • Encoding problem (via ORB)

    Hello,
    I posted this problem few months ago, but still havent been able to solve this.
    I have a Client Server program which communicates via ORB, i.e. using CORBA, with server running on Solaris OS and Client running on windows.
    The server returns string containing chinese characters to the client.
    However, my chinese characters dont appear properly on the client side.
    If i run the client on the Solaris OS there is no problem with it.
    I tried converting the encode of the string by getting its byte and creating
    a new string with encoding parameter. None of this seems to work.
    I can see the chinese character when the server is writing to OutputStream of CORBA, but on the InputStream of CORBA it does not
    show properly.
    Any ideas on how i can overcome this encoding problem where the C/S is
    communicating via CORBA (ORB)?
    Thanks in advance.

    Thanks for your reply
    Yes, i know the BIG5 is for Traditional Chinese and japansese is using like Shift-JIS or EUC.
    So when i try to post japanese in a BIg5 web page, i think it's normal that i can't see it in BIG5 encoding.
    But then i change the Safari default decoding to BIG5 HKSCS, the japanese appers! At the same time i can see the traditional chinese too!
    And if i use Firefox, i can both see the japanese and chinese at the default BIG5 encoding.
    So i simple think maybe safari translate my japanese into BIG5 HKSCS,not Shift-JIS. But if i use Firefox, i can get the same result with only BIG5 encoding, not BIG5 HKSCS. So i am just wondering why it's different between Safari and Firefox with the same BIG5 encoding.
    Following is a example URL
    It's a MAC discussing froum with BIG5 encoding in Taiwan.
    http://ubb.frostyplace.com.tw/viewtopic.php?t=19162
    It's a froum topic posted by me. I input some japanese into this topic
    If you browse this page with Safari BIG5 encoding, you can see a lot of question mark instead of the original japanese word that i and other people posted.
    But if you change the encoding to BIG5 HKSCS, the japanese appears. And if you using Firefox with BIG5 encoding, the japanese appears too.
    So is it someing wrong with Safari's BIG5 encoding or some other reason makes this happen?

  • View Object Encoding problem

    I'm using Jdeveloper version 11.1.2.1. I have a encoding problem when creating View Object based on a query. This is my query:
    select id, DECODE(id,'11','Индивидуално,'13','Semejno','14','Grupno') naziv
    from ins_type
    where class_id = '14' and id in ('11', '13', '14')
    It is a simple LOV query with cyrilic letters. When I save the ViewObject and re-open it im getting question marks(???????) instead of the cyrilic letters. This only happens in the view object. I dont have other encoding issues when working with cyrilic letters only when im trying to build a View Object based on a query that has cyrilic letters. If i read those values from the database everything is fine
    Thanks,

    Change the encoding of your application to UTF-8 which appears to be sufficient for cyrilic chars. Here is a quick guide on how to do this http://docs.oracle.com/cd/E17984_01/doc.898/e14693/appa_configuring_jdev.htm
    You may also need to update any pages that have encoding explicitly set

  • Czech characters encoding problem in RTFTemplate with Velocity engine

    Hi,
    I am trying to use your RTFTemplate project but I have trouble displaying Czech characters in the generated RTF document. Instead of characters like �čř� I get only questionmarks ????. I thought that this could be related to setting a wrong encoding in the velocity.properties file, so I set it to windows-1250 (support for Czech characters) but it didn�t help. Do you have any idea, what could be the problem? If this is not the right place to ask such question, please let me know about a better one.
    Thank you for your time,
    Ivo Jansky

    Hi Jason,
    Indeed I had contacted the provider and informed them about the encoding problem and the fact that passing the parameter http_content_charset had no effect on the sent back encoding.
    They have taken into account my request and have changed the encoding used during the request to the HOOK_URL.
    Thanks to all of your for your help.
    Regards,
    Jerome.

  • Urgent , encoding problem

    Hi ,
    i have received very important msg from ministry , but i cannot read it
    its be like this : 爀椀愀氀∀㸀
    i want to convert it to arabic chars ,
    any ideas ?

    Yes, it's an encoding problem. And no, the damagehas
    already been done by applying an incorrectencoding.
    This cannot be reversed.so there is no solution for this ?Yep you're fucked.
    The Ministry of Double Ungood Codings will be coming to collect you shortly so that you might be educated with the double plus good ways.

  • AC3 audio encoding problems

    Have been encoding ac3 without any problems until recently. Now all ac3 encodes just play back as digital "noise", and the problems exists with default as well as modified versions of the standard ac3 preset.
    I'm using latest versions of Compressor and Quicktime. Anyone seen this issue and know how to solve? I'm considering reinstalling Compressor, but that seems to entail a complete FCS2 reinstall...

    UPDATE: I rebooted my mac using my backup system disk, which has quicktime 7.1.6 installed. I found that under this configuration my ac3 files could be played back. So it's NOT an encoding problem after all. It seems to be a decoding problem. So next up I'll try reinstalling my current version of Quicktime on the main system disk (that's QT 7.2 of course.) If that doesn't work, I'll have to try reverting to Quictime 7.1.6 I guess...

  • PHP charater encoding problem.. i think

    Hi,
    IF I post a message through my form containing the Danish
    characters " �
    � � " and read it in my email client (TB 1.5 or
    OE) it has turned into
    this " ������ "
    instead of the � (or æ), � (or oslash;),
    � (or
    å).
    Does anybody know why? I know it must be a encoding problem
    and I tried
    to send a php header bore anything else but still no go.
    I'll appreciate any help.
    Thanks
    Kim

    Thanks both of you. I'm not quite sure about this "To control
    the
    encoding of an email sent by the PHP mail() function, you
    need to add an
    additional header in the fourth argument to mail()."
    This is the form...
    <?php
    if(isset($_POST['Submitted'])) {
    $Errors = Array();
    if(!trim($_POST['navn'])) $Errors[] = "Indtast venligst for
    og
    efternavn";
    if(!preg_match("/[a-zA-Z0-9._-]+@[a-zA-Z0-9._-]+\.[a-zA-Z0-9]{2,4}/",$_POST['email']))
    $Errors[] = "Indtast venligst en gyldig e-mail ";
    if(!trim($_POST['kommentar'])) $Errors[] = "Kommentar";
    if(strtolower(trim($_POST['spamtrap'])) != "syv") $Errors[]
    = "Stav
    tallet 7 med bokstaver - (syv)";
    if(!count($Errors)) {
    $SendTo = "[email protected]";
    $Subject = "mail fra hjemmesiden";
    $FromString = "Fra: ".$_POST['email']."\r\n";
    $additionalHeaders = "Content-Type: text/plain;
    charset=utf-8\r\n";
    $Indhold = "Der er blevet sendt flg. oplysninger:\r\n\r\n";
    $Indhold .= "Navn: ".$_POST['navn']."\r\n";
    $Indhold .= "Email: ".$_POST['email']."\r\n";
    $Indhold .= "Telefon nummer: ".$_POST['telefon']."\r\n";
    $Indhold .= "Adresse: ".$_POST['adresse']."\r\n\r\n";
    $Indhold .= "Postnummer og By:
    ".$_POST['postby']."\r\n\r\n";
    $Indhold .=
    "kommentar:\r\n".preg_replace("(\r\n|\r|\n)","\r\n",$_POST['kommentar'])."\r\n";
    $MailSuccess = mail($SendTo,$Subject,$Indhold,$FromString);
    header("Location:
    http://www.lazur.dk/tak.php");
    exit;
    ?>
    Is that correct?
    Kim
    Kim skrev:
    > Hi,
    >
    > IF I post a message through my form containing the
    Danish characters " �
    > � � " and read it in my email client (TB
    1.5 or OE) it has turned into
    > this " ������
    " instead of the � (or &aelig;), � (or oslash;),
    � (or
    > &aring;).
    >
    > Does anybody know why? I know it must be a encoding
    problem and I tried
    > to send a php header bore anything else but still no go.
    >
    > I'll appreciate any help.
    >
    > Thanks
    > Kim

  • H264 ENCODING PROBLEMS PLEASE SOMEONE REPLY

    I HAVE H264 ENCODING PROBLEMS TO ALL APLICATIONS
    FC PRO IMOVIE HD EVEN QT7.
    IT GOES VERY SLOW!!!!! FOR ENCODING AND CRASHES ALL THE TIME.
    FOR THE FIRST MIN GOES VERY FAST AND THEN DRAMATIC SLOW ANDIN HALF CRASHES -BY FOR PLAYING H264 GOES FAST FULL VIDEO CATCHES 30 FPS.
    I WANT TO KNOW WHY???????????????
    AND IF THERE IS ANOTHER SIMILAR FORMAT FOR EXPORTING WITHOUT LOSING
    VIDEO QUALITY

    Before we go any farther, please turn of you CAPS. It makes the post very difficult to read and is considered shouting in the internet world.
    Thank you.
    Now,
    Usually crashes in encoding can be traced back to:
    1. corrupted media files
    2. improper naming conventions
    3. disk storage issues.
    We need more information.
    What format is the original material?
    What Version of Final Cut Pro?
    What Verison of OSX?
    How many disks in the computer and how much space on the media drive? (you are keeping your media on a different drive than your OS, aren't you?)
    report back,
    x

Maybe you are looking for