Groups > alt.comp.os.windows-11 > #17744 > unrolled thread

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

Started by	micky <NONONOmisc07@fmguy.com>
First post	2025-03-13 19:59 -0400
Last post	2025-03-15 12:28 -0400
Articles	20 on this page of 28 — 9 participants

Back to article view | Back to alt.comp.os.windows-11

  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. 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

Page 1 of 2 [1] 2 Next page →

#17744 — Everything new, but still displayed incorrectly, FF, Chrome, and Edge.

From	micky <NONONOmisc07@fmguy.com>
Date	2025-03-13 19:59 -0400
Subject	Everything new, but still displayed incorrectly, FF, Chrome, and Edge.
Message-ID	<46s6tj5brurtndvke94hea1ik9nd4olpe2@4ax.com>

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?  

Latest or almost latest version of every browser.  Certainly newer than
the webpage itself which is from .... well they don't give the Last Rev.
Date, of course.  That would be asking too much.  But it was probably
years ago.

https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp

[toc] | [next] | [standalone]

#17745

From	"David E. Ross" <nobody@nowhere.invalid>
Date	2025-03-13 17:20 -0700
Message-ID	<vqvso6$65dp$1@dont-email.me>
In reply to	#17744

On 3/13/2025 4: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?  
> 
> Latest or almost latest version of every browser.  Certainly newer than
> the webpage itself which is from .... well they don't give the Last Rev.
> Date, of course.  That would be asking too much.  But it was probably
> years ago.
> 
> https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp
> 

How did you test this?

The "gold standard" for testing HTML is the W3C tool at
<http://jigsaw.w3.org/css-validator/>.  When I attempted to test the Web
page at
<https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp>,
however, I got the following:> 	Sorry! This document cannot be checked.
> 	    Error
> 	    I got the following unexpected response when trying to 
> 	retrieve <https://reflect.macrium.com/webtutorial
> 	/how_to_create_a_disk_image.asp>:
>         403 Forbidden
On the other hand, I waas able to test the CSS, which has 33 errors.

-- 

David E. Ross
<http://www.rossde.com/

History repeats --
Ukraine now: Czechoslovakia in 1938
Crimea: Sudetenland
Putin: Hitler
Donald Trump: Neville Chamberlain

[toc] | [prev] | [next] | [standalone]

#17746

From	"David E. Ross" <nobody@nowhere.invalid>
Date	2025-03-13 17:23 -0700
Message-ID	<vqvstk$65dp$2@dont-email.me>
In reply to	#17745

On 3/13/2025 5:20 PM, David E. Ross wrote:
> On 3/13/2025 4: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?  
>>
>> Latest or almost latest version of every browser.  Certainly newer than
>> the webpage itself which is from .... well they don't give the Last Rev.
>> Date, of course.  That would be asking too much.  But it was probably
>> years ago.
>>
>> https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp
>>
> 
> How did you test this?
> 
> The "gold standard" for testing HTML is the W3C tool at
> <http://jigsaw.w3.org/css-validator/>.  When I attempted to test the Web
> page at
> <https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp>,
> however, I got the following:> 	Sorry! This document cannot be checked.
>> 	    Error
>> 	    I got the following unexpected response when trying to 
>> 	retrieve <https://reflect.macrium.com/webtutorial
>> 	/how_to_create_a_disk_image.asp>:
>>         403 Forbidden
> On the other hand, I waas able to test the CSS, which has 33 errors.
> 
Oops!  I forgot.  My attempted testing indicates the problem is with the
Web page, not with any browser or any Windows version.  You might try
reposting your problem at the comp.infosystems.www.authoring.html
newsgroup.

-- 

David E. Ross
<http://www.rossde.com/

History repeats --
Ukraine now: Czechoslovakia in 1938
Crimea: Sudetenland
Putin: Hitler
Donald Trump: Neville Chamberlain

[toc] | [prev] | [next] | [standalone]

#17750

From	Jeff Barnett <jbb@notatt.com>
Date	2025-03-13 21:33 -0600
Message-ID	<vr082k$droj$1@dont-email.me>
In reply to	#17746

On 3/13/2025 6:23 PM, David E. Ross wrote:
> On 3/13/2025 5:20 PM, David E. Ross wrote:
>> On 3/13/2025 4: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?
>>>
>>> Latest or almost latest version of every browser.  Certainly newer than
>>> the webpage itself which is from .... well they don't give the Last Rev.
>>> Date, of course.  That would be asking too much.  But it was probably
>>> years ago.
>>>
>>> https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp
>>>
>>
>> How did you test this?
>>
>> The "gold standard" for testing HTML is the W3C tool at
>> <http://jigsaw.w3.org/css-validator/>.  When I attempted to test the Web
>> page at
>> <https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp>,
>> however, I got the following:> 	Sorry! This document cannot be checked.
>>> 	    Error
>>> 	    I got the following unexpected response when trying to
>>> 	retrieve <https://reflect.macrium.com/webtutorial
>>> 	/how_to_create_a_disk_image.asp>:
>>>          403 Forbidden
>> On the other hand, I waas able to test the CSS, which has 33 errors.
>>
> Oops!  I forgot.  My attempted testing indicates the problem is with the
> Web page, not with any browser or any Windows version.  You might try
> reposting your problem at the comp.infosystems.www.authoring.html
> newsgroup.
Or better yet, at macrium!
-- 
Jeff Barnett

[toc] | [prev] | [next] | [standalone]

#17751

From	Paul <nospam@needed.invalid>
Date	2025-03-13 23:57 -0400
Message-ID	<vr09fo$fea9$1@dont-email.me>
In reply to	#17750

On Thu, 3/13/2025 11:33 PM, Jeff Barnett wrote:
> On 3/13/2025 6:23 PM, David E. Ross wrote:
>> 
>> Oops!  I forgot.  My attempted testing indicates the problem is with the
>> Web page, not with any browser or any Windows version.  You might try
>> reposting your problem at the comp.infosystems.www.authoring.html
>> newsgroup.
> Or better yet, at macrium!

Normally, you navigate that site with a bit of Googling.

In your Google search, include the version of product
you are using, when looking for a particular procedure.

When "un-versioned" references to the Macrium site come
back, those are the old pages, and you don't use those.

*******

I sometimes make film strips for Macrium, but
these get out of date pretty quickly.  This is a disk image.

   https://postimg.cc/image/f664kgrzh/

This one shows a bare metal restore, using the Rescue CD.

   https://postimg.cc/image/458x0anpn/

This one is regarding making a Rescue CD (or ISO for Rufus),
and every version of Macrium will have some differences here.
This is likely to be useless.

   https://i.postimg.cc/054trNDv/make-rescue-cd-via-win-vm.gif

 Paul

[toc] | [prev] | [next] | [standalone]

#17753

From	micky <NONONOmisc07@fmguy.com>
Date	2025-03-14 01:22 -0400
Message-ID	<n1f7tj5288fqdmvo2rnli1th3hogtb964k@4ax.com>
In reply to	#17746

In alt.comp.software.firefox, on Thu, 13 Mar 2025 17:23:16 -0700, "David
E. Ross" <nobody@nowhere.invalid> wrote:

>On 3/13/2025 5:20 PM, David E. Ross wrote:
>> On 3/13/2025 4: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?  
>>>
>>> Latest or almost latest version of every browser.  Certainly newer than
>>> the webpage itself which is from .... well they don't give the Last Rev.
>>> Date, of course.  That would be asking too much.  But it was probably
>>> years ago.
>>>
>>> https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp
>>>
>> 
>> How did you test this?

By displaying it all 3 browsers. 
>> 
>> The "gold standard" for testing HTML is the W3C tool at
>> <http://jigsaw.w3.org/css-validator/>.  When I attempted to test the Web
>> page at
>> <https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp>,
>> however, I got the following:> 	Sorry! This document cannot be checked.
>>> 	    Error

Wow. 

>>> 	    I got the following unexpected response when trying to 
>>> 	retrieve <https://reflect.macrium.com/webtutorial
>>> 	/how_to_create_a_disk_image.asp>:
>>>         403 Forbidden

Wow. 

>> On the other hand, I waas able to test the CSS, which has 33 errors.

Wow. 
 
>Oops!  I forgot.  My attempted testing indicates the problem is with the
>Web page, 

I had not thought of that. I would expect them (the author and maybe
others) to look at their own page after they write it, but maybe not. 

>not with any browser or any Windows version.  You might try
>reposting your problem at the comp.infosystems.www.authoring.html
>newsgroup.

It's not at all that important.  It only matters if the browsers cannot
display proper code, and it did not occur to me that the code was
improper.

[toc] | [prev] | [next] | [standalone]

#17748

From	Paul <nospam@needed.invalid>
Date	2025-03-13 22:42 -0400
Message-ID	<vr051u$c5ng$1@dont-email.me>
In reply to	#17744

On Thu, 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?  
> 
> Latest or almost latest version of every browser.  Certainly newer than
> the webpage itself which is from .... well they don't give the Last Rev.
> Date, of course.  That would be asking too much.  But it was probably
> years ago.
> 
> https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp
> 

That's a web page intended for Internet Explorer. The
date the page was archived in archive.org , is not
representative of when the content was created. That's
an ancient page for Macrium 3 or Macrium 4 or so. The modern
product has better graphics than that for rendering a
representation of disk contents.

When Macrium web content has no version number on it, it
is ancient material. You sometimes run into this, looking
for references to a procedure in Macrium, and the old version
shows up in a Google.

Macrium has a PDF file and you would look for that, at a start.
It is only 485 pages.

https://updates.macrium.com/reflect/v8/user_guide/macrium_reflect_v8.0_user_guide.pdf

The document changes from dark theme to light theme, around
page 62 or so. It is possible the entire document did
not get re-written.

This one is 422 pages.

http://updates.macrium.com/reflect/v7/user_guide/macrium_reflect_v7_user_guide.pdf?src=sidebar

*******

It looks like the product might be up to version 10.
And it's not "free", this is likely a Trial version download.

https://www.techspot.com/downloads/5442-macrium-reflect-free.html

    Paul

[toc] | [prev] | [next] | [standalone]

#17749

From	Newyana2 <newyana@invalid.nospam>
Date	2025-03-13 23:26 -0400
Message-ID	<vr07io$dvno$1@dont-email.me>
In reply to	#17744

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?
> 
> Latest or almost latest version of every browser.  Certainly newer than
> the webpage itself which is from .... well they don't give the Last Rev.
> Date, of course.  That would be asking too much.  But it was probably
> years ago.
> 
> https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp
> 

   It looks fine to me with script disabled, with one minor
exception: Some bright bulb wrote it in UTF-8 but didn't
include a charset tag. So in Firefox I see junk characters
where every quote and apostrophe is supposed to be.

[toc] | [prev] | [next] | [standalone]

#17755

From	Andy Burns <usenet@andyburns.uk>
Date	2025-03-14 07:44 +0100
Message-ID	<m3i1idFa9ppU3@mid.individual.net>
In reply to	#17744

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?

Screenshot?

[toc] | [prev] | [next] | [standalone]

#17763

From	Paul <nospam@needed.invalid>
Date	2025-03-14 11:18 -0400
Message-ID	<vr1hbt$1i1th$1@dont-email.me>
In reply to	#17755

On Fri, 3/14/2025 2:44 AM, Andy Burns wrote:
> 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?
> 
> Screenshot?
> 

Re-enactment. No kittens were injured in the making of this picture.

   [Picture]

    https://i.postimg.cc/x8bYmGYr/old-webpage-is-old.gif

Some kind of character set thing.

  Paul

[toc] | [prev] | [next] | [standalone]

#17766

From	Andy Burns <usenet@andyburns.uk>
Date	2025-03-14 16:05 +0000
Message-ID	<m3j2e3Ff0rbU1@mid.individual.net>
In reply to	#17763

Paul wrote:

> Re-enactment. No kittens were injured in the making of this picture.
> 
>     [Picture]
> 
>      https://i.postimg.cc/x8bYmGYr/old-webpage-is-old.gif
> 
> Some kind of character set thing.
Yes, web browsers think it's best to not complain, just silently display 
what they can, but for ancient html such as this where there's not clue 
on character encoding,I think it would be fair game to pop-up a 
fluorescent pink banner saying ...

"WARNING: Badly written old webpage, will probably look shit,
complain to $WEBSITE, not to $BROWSER."

[toc] | [prev] | [next] | [standalone]

#17756

From	...w¡ñ§±¤ñ <winstonmvp@gmail.com>
Date	2025-03-14 00:26 -0700
Message-ID	<vr0lnn$rqae$1@dont-email.me>
In reply to	#17744

micky wrote on 3/13/2025 4:59 PM:
> 
> 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?
> 
> Latest or almost latest version of every browser.  Certainly newer than
> the webpage itself which is from .... well they don't give the Last Rev.
> Date, of course.  That would be asking too much.  But it was probably
> years ago.
> 
> https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp
> 

Consider using Macrium Reflect's most current documentation which is 
available in their Knowlege Base for version 8 or 7
  <https://www.macrium.com/knowledge-base
  Scroll down and choose 'Reflect 8' or 'Reflect 7'
  => For 'Reflect 8' choice use Edge, Firefox or Chrome

Note: For Reflect 8 instead of the entire 8.0 Knowledge Base, one can 
also go directly to the desired directions for imaging using version 8

-Creating a backup image of your computer, drive or partitions
 
<https://knowledgebase.macrium.com/display/KNOW80/Creating+a+backup+image+of+your+computer%2C+drive+or+partitions>
or
Creating a disk image of a single drive or partition
<https://knowledgebase.macrium.com/display/KNOW80/Creating+a+disk+image+of+a+single+drive+or+partition>


-- 
...w¡ñ§±¤ñ

[toc] | [prev] | [next] | [standalone]

#17764

From	Retirednoguilt <HapilyRetired@fakeaddress.com>
Date	2025-03-14 11:36 -0400
Message-ID	<vr1idf$1idkn$1@dont-email.me>
In reply to	#17744

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?  
> 
> Latest or almost latest version of every browser.  Certainly newer than
> the webpage itself which is from .... well they don't give the Last Rev.
> Date, of course.  That would be asking too much.  But it was probably
> years ago.
> 
> https://reflect.macrium.com/webtutorial/how_to_create_a_disk_image.asp
> 

The web page is not encoded in keeping with modern (current) standards.
Very easy to fix in current firefox for windows.  With the menu bar
displaying the menu bar, that the "file   edit   options    tools
save"  headers, click on the view header and then the "repair text
encoding" option.  Voila!  All done!

[toc] | [prev] | [next] | [standalone]

#17767

From	Andy Burns <usenet@andyburns.uk>
Date	2025-03-14 16:09 +0000
Message-ID	<m3j2m1Ff0rbU2@mid.individual.net>
In reply to	#17764

Retirednoguilt wrote:

> click on the view header and then the "repair text
> encoding" option.  Voila!  All done!

Well, repair'ish ... it just turns all the grot characters into
"the replacement character" � U+FFFD.

[toc] | [prev] | [next] | [standalone]

#17771

From	Retirednoguilt <HapilyRetired@fakeaddress.com>
Date	2025-03-14 12:33 -0400
Message-ID	<vr1lpn$1lmfh$1@dont-email.me>
In reply to	#17767

On 3/14/2025 12:09 PM, Andy Burns wrote:
> Retirednoguilt wrote:
> 
>> click on the view header and then the "repair text
>> encoding" option.  Voila!  All done!
> 
> Well, repair'ish ... it just turns all the grot characters into
> "the replacement character" � U+FFFD.
> 


True,  But do you dispute that it's now easier to read?

[toc] | [prev] | [next] | [standalone]

#17775

From	Newyana2 <newyana@invalid.nospam>
Date	2025-03-14 13:03 -0400
Message-ID	<vr1nf4$1nb22$1@dont-email.me>
In reply to	#17771

On 3/14/2025 12:33 PM, Retirednoguilt wrote:
> On 3/14/2025 12:09 PM, Andy Burns wrote:
>> Retirednoguilt wrote:
>>
>>> click on the view header and then the "repair text
>>> encoding" option.  Voila!  All done!
>>
>> Well, repair'ish ... it just turns all the grot characters into
>> "the replacement character" � U+FFFD.
>>

> True,  But do you dispute that it's now easier to read?
> 
     You get the Trump Logic Award for that one. :) It's
not repairing anything. It's just re-rendering in different
encoding. It sniffed the charcter encoding, recognized
likely UTF-8, and switched it. That's a nice function to
know about, but it's not repair. Repair would require full
English literacy. Repair will be when someone at Macrium
realizes their webpages have been broken for close to
20 years. I give them credit, though. Aside from that
mess-up, the page is clear and simple. (

   Well, except for the fact that they completely screwed up
the images unnecessarily, so that they don't show at all without
script. And check out the scrrript-type attributes:
type="8eadf7e62a08f178f0f17509-text/javascript"

This is actually a very weird webpage.

[toc] | [prev] | [next] | [standalone]

#17776

From	Retirednoguilt <HapilyRetired@fakeaddress.com>
Date	2025-03-14 13:40 -0400
Message-ID	<vr1pm8$1ortj$1@dont-email.me>
In reply to	#17775

On 3/14/2025 1:03 PM, Newyana2 wrote:
> On 3/14/2025 12:33 PM, Retirednoguilt wrote:
>> On 3/14/2025 12:09 PM, Andy Burns wrote:
>>> Retirednoguilt wrote:
>>>
>>>> click on the view header and then the "repair text
>>>> encoding" option.  Voila!  All done!
>>>
>>> Well, repair'ish ... it just turns all the grot characters into
>>> "the replacement character" � U+FFFD.
>>>
> 
>> True,  But do you dispute that it's now easier to read?
>>
>      You get the Trump Logic Award for that one. :) It's
> not repairing anything. It's just re-rendering in different
> encoding. It sniffed the charcter encoding, recognized
> likely UTF-8, and switched it. That's a nice function to
> know about, but it's not repair. Repair would require full
> English literacy. Repair will be when someone at Macrium
> realizes their webpages have been broken for close to
> 20 years. I give them credit, though. Aside from that
> mess-up, the page is clear and simple. (
> 
>    Well, except for the fact that they completely screwed up
> the images unnecessarily, so that they don't show at all without
> script. And check out the scrrript-type attributes:
> type="8eadf7e62a08f178f0f17509-text/javascript"
> 
> This is actually a very weird webpage.
> 

Using Trump, logic, and award all in the same sentence is incompatible
with my understanding of recent U.S. political history and the text that
provides the ground rules of our government.  See the following
reference:  U.S. Constitution.

[toc] | [prev] | [next] | [standalone]

#17777

From	Richmond <dnomhcir@gmx.com>
Date	2025-03-14 17:52 +0000
Message-ID	<86plijqz2g.fsf@example.com>
In reply to	#17775

Newyana2 <newyana@invalid.nospam> writes:


> This is actually a very weird webpage.

Maybe it is specially constructed to exploit vulnerabilities in
libfreetype6.

[toc] | [prev] | [next] | [standalone]

#17785

From	Retirednoguilt <HapilyRetired@fakeaddress.com>
Date	2025-03-15 09:39 -0400
Message-ID	<vr3vuq$3kcck$1@dont-email.me>
In reply to	#17777

On 3/14/2025 1:52 PM, Richmond wrote:
> Newyana2 <newyana@invalid.nospam> writes:
> 
> 
>> This is actually a very weird webpage.
> 
> Maybe it is specially constructed to exploit vulnerabilities in
> libfreetype6.

The trolls come out of their holes just as sure as day follows night.

[toc] | [prev] | [next] | [standalone]

#17768

From	Newyana2 <newyana@invalid.nospam>
Date	2025-03-14 12:12 -0400
Message-ID	<vr1kgd$1knce$1@dont-email.me>
In reply to	#17764

On 3/14/2025 11:36 AM, Retirednoguilt wrote:

> 
> The web page is not encoded in keeping with modern (current) standards.
> Very easy to fix in current firefox for windows.  With the menu bar
> displaying the menu bar, that the "file   edit   options    tools
> save"  headers, click on the view header and then the "repair text
> encoding" option.  Voila!  All done!
> 

   That's an interesting thing that I didn't know about, but it
doesn't work for me. It renders the page as UTF-8 instead
of ANSI, but the "repair" just means the funky characters
are replaced by black diamonds with question marks inside,
to indicate the character encoding is faulty. So now it's
proper UTF-8, but the original encoding was corrupted.
For FF to repair that it would have to parse the meaning of
the text and guess whether an ', a quote or a comma is called
for.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2 [1] 2 Next page →

csiph-web

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

Contents

#17744 — Everything new, but still displayed incorrectly, FF, Chrome, and Edge.

#17745

#17746

#17750

#17751

#17753

#17748

#17749

#17755

#17763

#17766

#17756

#17764

#17767

#17771

#17775

#17776

#17777

#17785

#17768