To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.publishOpen lugnet.publish in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Publishing / 976
975  |  977
Subject: 
Re: Just testing character codes
Newsgroups: 
lugnet.off-topic.test, lugnet.publish
Date: 
Tue, 28 Sep 1999 18:51:40 GMT
Viewed: 
47 times
  
In lugnet.off-topic.test, Todd Lehman writes:
Nope, there aren't any HTML entities (numeric or non-numeric) that are
handled.  By design, if you type '&', it's *always* converted to '&'
by the web display interface, meaning that if you type 'æ' in your
article, then the HTML generated is 'æ' -- which is exactly how
it should be, because netnews articles are supposed to be plaintext, not
HTML.

So, for news articles, just use the plain raw 8-bit ISO-8859-1 encoding:

  Don't write     Do write
  -----------     --------
    æ          æ
    ø         ø
    ®            ®
    £           £

Then it will come out correctly.  For example, if you write 'æ' in your news
article, then it will be sent to newsreaders as 'æ' and to web browsers as
'æ' (so that it may display properly as 'æ').  But if you accidentally
write 'æ' in your news article, then it will be sent to your newsreader
as 'æ' but to your web browser as 'æ' in order that it may
display exactly properly as you wrote it, e.g., 'æ'.

Again, this is by design.  It would be a bug not to convert '&' to '&',
just as it would be a bug not to convert '<' to '&lt;', etc...

--Todd

Hmm.... maybe it's something to do with how you're parsing web-input? I'm using
the web interface to enter messages, and I'm typing:
& # 1 6 3 ;
(but without the spaces) and it comes out as a single character (the pound
sign: "£") when I view the message. Also, it comes out as the same single
character when I click on "view raw message". When I type:
& p o u n d ;
(without the spaces) it just comes out as "&pound;", it doesnt come out as the
pound sign. So I'm thinking that maybe what happens is when you read in the
web-input, you read it in as a single character? The 'traditional' "ReadParse"
routine in 'cgi-lib.pl' takes care of it nicely, but I don't know about other
stuff... But the only thing I can think of is that the $ENV{'QUERY_STRING'} is
being parsed as just 1 character for numeric entities... I've actually used
this a couple times for footnotes†... comes in handy :)

DaveE

† O'Reilly says the conformence on symbols like this is "!!!", though...
watch out!



Message has 1 Reply:
  Re: Just testing character codes
 
(...) Thanks for reporting this. When I said earlier that it "didn't" convert stuff like that to raw form, I meant that I believed that didn't, because it shouldn't (it wasn't supposed have been). Alas, I did something dumb in a regex: In an (...) (25 years ago, 2-Oct-99, to lugnet.off-topic.test, lugnet.publish, lugnet.admin.general)

Message is in Reply To:
  Re: Just testing character codes
 
(...) Nope, there aren't any HTML entities (numeric or non-numeric) that are handled. By design, if you type '&', it's *always* converted to '&amp;' by the web display interface, meaning that if you type '&aelig;' in your article, then the HTML (...) (25 years ago, 28-Sep-99, to lugnet.off-topic.test, lugnet.publish)

5 Messages in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR