Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.software.firefox > #12719

Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge.

From micky <NONONOmisc07@fmguy.com>
Newsgroups alt.comp.software.firefox, alt.comp.os.windows-11
Subject Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge.
Message-ID <m9dctj5hd6ilgdpet7nagb11lrr8aa726n@4ax.com> (permalink)
References <46s6tj5brurtndvke94hea1ik9nd4olpe2@4ax.com> <vr1k0q$1kaq7$1@dont-email.me>
Organization Tweaknews
Date 2025-03-15 22:20 -0400

Cross-posted to 2 groups.

Show all headers | View raw

In alt.comp.os.windows-11, on Fri, 14 Mar 2025 12:04:36 -0400, Newyana2
<newyana@invalid.nospam> wrote:

>On 3/13/2025 7:59 PM, micky wrote:
>> 
>> Everything new, but still displayed incorrectly
>> 
>> Whether looking with Firefox, Edge, or Chrome, there are errors in the
>> 2nd, 7th, 8th, and other lines.  Why?
>> 
>
>    I checked into this further. The characters are UTF-8
>EF BF BD. According to what I could find, it's a replacement
>character, a ? inside a black diamond, which is used when an
>"illegal" character code is encountered.
>
>   So there are two problems. First is that the page is UTF-8
>but is not marked as such. It should have <META charset="UTF-8">
>So it's rendering as English ANSI. The second problem seems to
>be that some editor or conversion process somehow created
>these characters. Perhaps there were illegal characters like
>some kind of ANSI character codes for curly braces, which then
>got transposed to UTF-8 in an editor that, rather than dropping the
>illegal characters, replaced them with the "illegal" marker of the
>3 bytes EF BF BD.
>
>   In some cases on my system, the characters get replaced with
>spaces if I start to edit. I don't understand the details of how
>that's working. It seems to be somehow connected to ANSI/UTF-8
>back and forth.
>
>   In ANSI English, bytes over 127 have specific character correspondence.
>In other languuages the characters are different. In UTF-8, bytes over
>127 are used in a system of up to 4 bytes to accomodate all languages
>into one system that's still compatible with ASCII (the characters
>represented by bytes 0-127).
>
>  So this is not a browser problem. The webpage seems to have
>gone through conversions, by someone who didn't know about encoding
>and somehow hasn't noticed. The javascript refers to checking for
>a userAgent "Netscape", so I'm guessing it's not a recent webpage. :)
>It says it was created by RoboEditor. That's probably the culprit.
>
>   If you download the webpage and insert a UTF-8 marker into the
>source code you'll see the black diamond ?s. It's still perfectly
>readable, just faulty encoding.
>
All very interesting.  I went to school with a guy from Boston, Rob
O'Editor, but I don't think he would make mistakes like these.

Back to alt.comp.software.firefox | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Everything new, but still displayed incorrectly, FF, Chrome, and Edge.  micky <NONONOmisc07@fmguy.com> - 2025-03-13 19:59 -0400
  Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. "David E. Ross" <nobody@nowhere.invalid> - 2025-03-13 17:20 -0700
    Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. "David E. Ross" <nobody@nowhere.invalid> - 2025-03-13 17:23 -0700
      Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Jeff Barnett <jbb@notatt.com> - 2025-03-13 21:33 -0600
        Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Paul <nospam@needed.invalid> - 2025-03-13 23:57 -0400
      Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. micky <NONONOmisc07@fmguy.com> - 2025-03-14 01:22 -0400
  Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Nobody <jock@soccer.com> - 2025-03-13 18:23 -0700
    Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Frank Miller <miller@posteo.ee> - 2025-03-14 02:44 +0100
      Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. micky <NONONOmisc07@fmguy.com> - 2025-03-14 01:22 -0400
        Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Andy Burns <usenet@andyburns.uk> - 2025-03-14 07:15 +0000
          Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. micky <NONONOmisc07@fmguy.com> - 2025-03-15 12:23 -0400
  Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Paul <nospam@needed.invalid> - 2025-03-13 22:42 -0400
  Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Newyana2 <newyana@invalid.nospam> - 2025-03-13 23:26 -0400
  Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Andy Burns <usenet@andyburns.uk> - 2025-03-14 07:44 +0100
    Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Paul <nospam@needed.invalid> - 2025-03-14 11:18 -0400
      Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Andy Burns <usenet@andyburns.uk> - 2025-03-14 16:05 +0000
  Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-14 00:26 -0700
  Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Retirednoguilt <HapilyRetired@fakeaddress.com> - 2025-03-14 11:36 -0400
    Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Andy Burns <usenet@andyburns.uk> - 2025-03-14 16:09 +0000
      Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Retirednoguilt <HapilyRetired@fakeaddress.com> - 2025-03-14 12:33 -0400
        Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Newyana2 <newyana@invalid.nospam> - 2025-03-14 13:03 -0400
          Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Retirednoguilt <HapilyRetired@fakeaddress.com> - 2025-03-14 13:40 -0400
          Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Richmond <dnomhcir@gmx.com> - 2025-03-14 17:52 +0000
            Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Retirednoguilt <HapilyRetired@fakeaddress.com> - 2025-03-15 09:39 -0400
    Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Newyana2 <newyana@invalid.nospam> - 2025-03-14 12:12 -0400
      Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Andy Burns <usenet@andyburns.uk> - 2025-03-14 16:16 +0000
        Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Newyana2 <newyana@invalid.nospam> - 2025-03-14 12:45 -0400
  Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Newyana2 <newyana@invalid.nospam> - 2025-03-14 12:04 -0400
    Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Andy Burns <usenet@andyburns.uk> - 2025-03-14 16:18 +0000
      Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Newyana2 <newyana@invalid.nospam> - 2025-03-14 12:41 -0400
    Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. micky <NONONOmisc07@fmguy.com> - 2025-03-15 22:20 -0400
      Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge. Paul <nospam@needed.invalid> - 2025-03-15 23:02 -0400
  Re: Everything new, but still displayed incorrectly, FF, Chrome, and Edge.  micky <NONONOmisc07@fmguy.com> - 2025-03-15 12:28 -0400

csiph-web