If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
UTF-8/ASCII, not UTF-16, is the standard.
On 7/11/19 2:19 PM, Siri Cruise wrote:
In article , nospam wrote: In article , Siri Cruise wrote: Why the heck would you use the high bit on a ASCII web page, because the desired characters aren't available otherwise. The HTML source can and should be ASCII only. You can use entity references for anything outside of ASCII. That lets the browser know what character is intended and present it as the browser pleases rather than make the browser guess what octets 80 to FF mean. no need to guess when done correctly. Just ASCII with entity references in ASCII is always correct. And it's easy to do. Good luck getting web programmers to follow that! At times, I have masked off the high bit to tame the ridiculous Byte AND 0b0111 |
Ads |
#17
|
|||
|
|||
UTF-8/ASCII, not UTF-16, is the standard.
On 7/11/19 2:21 PM, Siri Cruise wrote:
In article , T wrote: On 7/11/19 11:59 AM, Siri Cruise wrote: In article , nospam wrote: In article , wrote: Why the heck would you use the high bit on a ASCII web page, because the desired characters aren't available otherwise. The HTML source can and should be ASCII only. You can use entity references for anything outside of ASCII. That lets the browser know what character is intended and present it as the browser pleases rather than make the browser guess what octets 80 to FF mean. Ya, you think? "Suppose to" and "does" are two different things. And good luck complaining to the web site about it. I see a lot of a href=/downloadsdownloads[trash][trash][trash]/a On any sites not using microsoft? I have never checked what created the site. I do find cr and crlf as line terminators all the time, but that is a non-issue. 0x00 (0b0000) really blows my mind when I come across it. But, regex's are fun! I find what I want and drop all the rest. I only want revision number and link to the download |
#18
|
|||
|
|||
UTF-8/ASCII, not UTF-16, is the standard.
In article
, Siri Cruise wrote: Why the heck would you use the high bit on a ASCII web page, because the desired characters aren't available otherwise. The HTML source can and should be ASCII only. You can use entity references for anything outside of ASCII. That lets the browser know what character is intended and present it as the browser pleases rather than make the browser guess what octets 80 to FF mean. no need to guess when done correctly. Just ASCII with entity references in ASCII is always correct. And it's easy to do. it's also very limiting and obsolete. using unicode is easy and always correct. there is *no* excuse for not being able to read or write unicode anymore. all platforms support it, and have for many, many years. |
#19
|
|||
|
|||
UTF-8/ASCII, not UTF-16, is the standard.
UTF-8/ASCII, not UTF-16, is the standard for:
-- FileNames ( all operating systems ). -- CommandLine Utilities ( e.g. "YouTube-DL.EXE" ). -- The Internet ( e.g. ".HTML" files ). Hence ( http://Jeff-Relf.Me/Win10.REG.TXT ): [HKEY_CURRENT_USER\Software\Microsoft\Command Processor] "autorun"="C:\\__\\_Source\\Init-CMD.BAT" "Init-CMD.BAT": @chcp 65001 @prompt $P$_$g Also, I wrote my own console ( http://Jeff-Relf.Me/X.HTM ). Mostly it's used for my Visual C++ routines, but it also runs "YouTube-DL.EXE" directly, without "CMD.EXE". From "X.CPP" in "http://Jeff-Relf.Me/X.ZIP": SECURITY_ATTRIBUTES Inherit = { sizeof( SECURITY_ATTRIBUTES ) }; Inherit.bInheritHandle = 1 ; static HANDLE r, w ; CreatePipe( &r, &w, &Inherit, 0 ); SetHandleInformation( r, HANDLE_FLAG_INHERIT, 0 ); STARTUPINFO SU ={ sizeof( STARTUPINFO ) }; SU.dwFlags = STARTF_USESTDHANDLES | STARTF_USESHOWWINDOW; SU.wShowWindow = SW_HIDE, SU.hStdOutput = SU.hStdError = w; SU.hStdInput = GetStdHandle( STD_INPUT_HANDLE ); |
#20
|
|||
|
|||
UTF-8/ASCII, not UTF-16, is the standard.
Siri_Cruise:
The HTML source can and should be ASCII only. Yes, and all puppies should go to heaven. |
#21
|
|||
|
|||
The CharSet is "UTF-8".
View Source the Korean on this page:
"BTS (방탄소년단) - MIC Drop": https://Youtube.COM/watch?v=RgFHvg8WSxg Like most webpages, the CharSet is "UTF-8". meta charset="UTF-8" |
#22
|
|||
|
|||
UTF-8/ASCII, not UTF-16, is the standard.
On 7/11/19 10:01 PM, Melzzzzz wrote:
On 2019-07-11, Siri Cruise wrote: In article , Jeff-Relf.Me @.@ wrote: Siri_Cruise: The HTML source can and should be ASCII only. Yes, and all puppies should go to heaven. They do. There is no heaven in the sky... But, But, But, where do puppies go? |
#23
|
|||
|
|||
UTF-8/ASCII, not UTF-16, is the standard.
On 7/11/19 5:32 PM, Siri Cruise wrote:
In article , T wrote: On 7/11/19 2:19 PM, Siri Cruise wrote: In article , Jeff-Relf.Me @.@ wrote: Siri_Cruise: The HTML source can and should be ASCII only. Yes, and all puppies should go to heaven. They do. How about old dogs? They get soft slippers. :-) |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|