|
Re: BUG: code blocks don't retain literal formatting -- could they?
by kcott (Archbishop) on Sep 15, 2016 at 07:38 UTC
|
G'day perl-diddler,
Regarding what it says below the input window,
maybe changing "... put the characters ..."
to "... put these characters ..."
would clarify which characters this statement references.
The reason why things are the way they are, is to allow code like this:
sub amp { ... }
my $coderef = \&
Unfortunately, your request would render that as:
sub amp { ... }
my $coderef = \&
The workaround is to use 'pre' tags instead of 'code' tags for blocks
(and 'tt' tags for inline text):
This pi (π) using π does display correctly.
This pi (π) using π does display correctly.
This pi (π) using π does display correctly.
This pi (π) using literal pi character does display correctly.
[Note:
On previewing, I noticed that the literal pi character that I pasted into that last example
now appears as π in the textarea.]
Use this workaround sparingly as you don't get a [download] link.
Also, line wrapping (or absence thereof) can be problematic
so aim to keep lines short
(I think <= 72 characters is optimal, inasmuch as it doesn't mess up normal page layout).
| [reply]
[d/l]
[select] |
|
|
In regards to the rendering problem ... my 1st solution -- don't change user-input characters into HTML entities, wouldn't affect the ability to say 'amp' after a ampersand. Only if we went with the 2nd option of preserving roundtrip integrity. I preferred the 1st which had it not changing the user input, so it wouldn't need to change it the 2nd time, which caused the problem you mentioned.
I used a literal pi, which was changed into the #960 form in the edit buffer, but then didn't change it back on display. FWIW, all of the different renderings of pi you tried display as pi on my system. Maybe it's a matter of browser configuration? I have my browser's fallback character encoding for 'legacy content'sic that fails to specify a character encoding to UTF-8. It rarely fails -- indicating that even new pages that fail to specify content are usually UTF-8. I'd say <10% actually use western as a default...
| [reply] |
|
|
| [reply]
[d/l] |
|
|
Update: Corrected spelling and capitalization mistakes.
As best I can tell, with out use utf8; in your Perl5 program, the Perl5 compiler expects the source code to be 8 bit ANSI characters.1 With use utf8; in effect, you may have UTF8 encoded characters in your source code.
Quoted strings, by default, are treated a streams of 8 bit bytes. With use feature 'unicode_strings'; in effect, you can include UTF8 encoded characters in quoted strings.
If PM could store the characters/bytes within code tags as-is, then only apply HTML encoding when generating HTML output, I think that would achieve the desired result. (the download link could supply the "raw" bytes with Content-type: application/octet)
If that can't be done, maybe instead of HTML encoding, do \x encoding. Either way, non-7-bit-ANSI source code gets messed up, but at least double quoted strings might still be correctly interpreted by the Perl compiler.2
---
1 I haven't tried using characters in the range 0x80 .. 0xFF in identifiers in Perl5, but Perl5 keywords all use characters < 0x80.
2 The open question is, when use feature 'unicode_strings'; is in effect, would "\x80\x77" be interpreted as 2 characters ("\x80" "\x77") or 1 ("\N{U+8077}") ?
| [reply]
[d/l]
[select] |
|
|
|
|
|
|
|
|
|
In regards to the rendering problem ... my 1st solution -- don't change user-input characters into HTML entities, wouldn't affect the ability to say 'amp' after a ampersand. Thats done by your browser. See Re: Strange letters ...
| [reply] |
|
|
The reason why things are the way they are, is to allow code like this:
sub amp { ... }
my $coderef = \&
Unfortunately, your request would render that as:
sub amp { ... }
my $coderef = \&
This bug is caused by not encoding the semicolon and ampersand of the HTML entity. The encoding of the ampersand and semicolon must be done in the same code to not confuse from a past converted HTML entity and must be the first HTML filter.
Any filter for HTML code that does not encode ampersand and semicolon will have this problem.
This problem was addressed in a past version of my module AUBBC v4.01 - 11/08/2010
New version located at AUBBC2
The fix I use now looks like this.
s[(&|;)][$1 eq '&' ? '&' : ';']gex;
Update: spelling
Update: My bad! Because PerlMonks mixes the HTML entity's with HTML names, will always cause a problem somewhere and no one filter will work in every case. You have to type the HTML name or your S.O.L..
Hay, welcome to PerlMonks. The place where you need to learn HTML before you can post your Perl question. ッ
| [reply]
[d/l]
[select] |
|
|
> The place where you need to learn HTML before you can post your Perl question
Yeah, because knowing HTML is something absolutely pointless, while the knowledge of Markdown, or at least one of its dialects used at StackOveflow, is something most employers need badly.
($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
| [reply]
[d/l] |
|
|
|
|
|
|
Why would mixing HTML named entities, hex, numeric, and whatever is a legal char in the document’s charset cause any problems?
| [reply] |
|
|
| [reply] |
Re: BUG: code blocks don't retain literal formatting -- could they?
by choroba (Cardinal) on Sep 15, 2016 at 07:35 UTC
|
It's annoying, but I got used to it. When I need to post some Unicode (more often data than code), I use <pre> instead of <code> or <c>.
لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ
($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
| [reply]
[d/l]
[select] |
Re: BUG: code blocks don't retain literal formatting -- could they?
by Anonymous Monk on Sep 15, 2016 at 07:39 UTC
|
| [reply] |
|
|
| [reply] |
|
|
| [reply] |
|
|
|
|
|
|
|
| [reply]
[d/l] |
