Menu

Cannot modify header information in norwegian

Help
Anonymous
2004-02-09
2004-02-11
  • Anonymous

    Anonymous - 2004-02-09

    I wonder if any of you good folks may help me with a minor problem.

    When I change the language to norwegian, I get the following message on top of the page:

    Warning: Cannot modify header information - headers already sent by (output started at /home/hasse/public_html/slekt/languages/facts.no.php:1) in /home/hasse/public_html/slekt/functions_print.php on line 465

    None of the other languages creates this warning message, and I'm lost.

    I have installed the patch pvg_2653_lang_no.zip and all language files have been uploaded in ASCII mode.

    (The url for the site is http://stave-teigen.net/slekt/ )

    Thanks!
    Hasse Teigen

     
    • Arne Eckmann

      Arne Eckmann - 2004-02-10

      Hi Hasse

      When I look at your tree I see character codes like they look when UTF-8 characters are viewed in ANSI (ISO-8859-1).

      Even if I change to Danish, or Swedish or German, it still looks as if it is UTF-8 characters viewed in ANSI (ISO-8859-1).

      When I try to remedy this situation in my viewer, your pages keeps forcing the situation back to
      the ANSI (ISO-8859-1) situation.

      When looking at your pages sources I find:

      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />

      where the same line in my pages reads:

      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

      If you want your pages to display the Norwegian and other international characters correctly, this line has to say:

      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

      The Norwegian update pvg_2653_lang_no.zip looks alright to me, and facts.no.php are not part of that package.

      To my knowledge there are no need to upload language files in ASCII. I always leave it to the FTP program to decide, and my FTP program always upload the files in binary mode.

      If you have edited any of the files yourselves in an ordinary text editor, you probably need to check these files for the notorious three "invisible" bytes at the very start of the files.

      Try replace facts.no.php with a fresh one straight from the package.

      Otherwise you perhaps only need to go to the gedcom setup page and change the charset from ISO-8859-1 to UTF-8

      Best regards,

      Arne
          

       
    • Patrik Hansson

      Patrik Hansson - 2004-02-10

      I think this is problem with some chars on line 1 in the facts.no.php file. If you open the file in an editor that shows the file as it is like Crimson editor or any like that you will see some odd looking chars at the start of the file before the php statement. remove this chars and save the file then i think it should work.

      Regards
      Patrik

       
    • Arne Eckmann

      Arne Eckmann - 2004-02-10

      Hi Patrik

      Did you fetch http://eckmann.dk/patrik.zip ?

      Best regards,

      Arne

       
      • Patrik Hansson

        Patrik Hansson - 2004-02-11

        Yes I fetch the files. I have been busy so I havn't had time to test.

        Ha en bra dag

        Patrik

         
    • Anonymous

      Anonymous - 2004-02-10

      Hi guys!

      And thanks a lot for the help so far. It was the notorious three invisible bytes that caused the warning message I received when changing to norwegian.

      After uploading a clean facts.no.php and getting rid of the invisible bytes, I replaced all files in the language folder, and all files in the main dir with fresh ones, all of them warm from the .zip file, except authenticate.php and config.php.
      I then changed the charset to utf-8 in the gedcom setup page.
      Everything looks ok with norwegian selected, except the data from the gedcom file: All norwegian special characters still look odd....

      Then, like a bolt of lightning from a pissed off roman god, it strikes me: Hasse, when you exported the gedcom file, which charset did you choose?

      I couldn't remember selecting a charset during the export, so I went back and checked, and ANSI is the default set. I made a new export, with UTF-8 selected, uploaded and imported the gedcom file.

      Everything is working perfectly, just like the brilliant minds behind the script meant things to work.

      Thank you very much for you help and guidance guys. It's highly appreciated!

      I'm off to do my happy dance now....

      Cheers!
      Hasse Teigen

       

Log in to post a comment.