Fussy Syntax Highlighting Problem
-
Hi, I spotted a minor (very minor) issue with your syntax highlighting for <pre> blocks:
var variable1=new string();
var variable2 = new string();Notice that the first 'new' keyword is not the right colour, presumably because there is no space before the keyword. As I said, a very fussy thing to point out, and definitly not very important...
-
Hi, I spotted a minor (very minor) issue with your syntax highlighting for <pre> blocks:
var variable1=new string();
var variable2 = new string();Notice that the first 'new' keyword is not the right colour, presumably because there is no space before the keyword. As I said, a very fussy thing to point out, and definitly not very important...
similar things happen with single quotes and double quotes. I suspect a Regex is used which ignores newlines. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
-
similar things happen with single quotes and double quotes. I suspect a Regex is used which ignores newlines. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
If we were ignoring newlines they wouldn't work at all. eg multiline comments. We'll check.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
If we were ignoring newlines they wouldn't work at all. eg multiline comments. We'll check.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
obviously, you can't completely ignore newlines, as they terminate single-line comments (// style). I apologize, almost nothing wrong with syntax coloring and quotes any more; I remember it being much worse. Right now the one mistake I see is VB should not escape within string literals. Here is a test without any lang="..":
this is a "string"
for a 'string' in some languages
this could be a "for now an ' embedded single quote in a string" and for more text
this could be a "for now an ' embedded single quote in a string" and for more text
for a "for now an ' embedded single quote in a string" and // for more text
this could be a "for now an ' embedded single quote in a string" /* and for more text */ here
this could be a "for now an ' embedded single quote in a string" /* and for
this could be a "string with an escaped double quote \" inside"
wow */ going well
this could be a "string with an escaped double quote \" inside"and now re repeat all the above once more:
this is a "string"
for a 'string' in some languages
this could be a "for now an ' embedded single quote in a string" and for more text
this could be a "for now an ' embedded single quote in a string" and for more text
for a "for now an ' embedded single quote in a string" and // for more text
this could be a "for now an ' embedded single quote in a string" /* and for more text */ here
this could be a "for now an ' embedded single quote in a string" /* and for
this could be a "string with an escaped double quote \" inside"
wow */ going well
this could be a "string with an escaped double quote \" inside"Here is a test using lang="cs":
this is a "string"
for a 'string' in some languages
this could be a "for now an ' embedded single quote in a string" and for more text
this could be a "for now an ' embedded single quote in a string" and for more text
for a "for now an ' embedded single quote in a string" and // for more text
this could be a "for now an ' embedded single quote in a string" /* and for more text */ here
this could be a "for now an ' embedded single quote in a string" /* and for
this could be a "string with an escaped double quote \" inside"
wow */ going well
this could be a "string with an escaped double quote \" inside"and now re repeat all the above once more:
this is a "string"
for a 'string' in some languages
this could be a "for now an ' embedded single quote in a string" and for more text
this could be a "for now an ' embedded single quote in a str -
obviously, you can't completely ignore newlines, as they terminate single-line comments (// style). I apologize, almost nothing wrong with syntax coloring and quotes any more; I remember it being much worse. Right now the one mistake I see is VB should not escape within string literals. Here is a test without any lang="..":
this is a "string"
for a 'string' in some languages
this could be a "for now an ' embedded single quote in a string" and for more text
this could be a "for now an ' embedded single quote in a string" and for more text
for a "for now an ' embedded single quote in a string" and // for more text
this could be a "for now an ' embedded single quote in a string" /* and for more text */ here
this could be a "for now an ' embedded single quote in a string" /* and for
this could be a "string with an escaped double quote \" inside"
wow */ going well
this could be a "string with an escaped double quote \" inside"and now re repeat all the above once more:
this is a "string"
for a 'string' in some languages
this could be a "for now an ' embedded single quote in a string" and for more text
this could be a "for now an ' embedded single quote in a string" and for more text
for a "for now an ' embedded single quote in a string" and // for more text
this could be a "for now an ' embedded single quote in a string" /* and for more text */ here
this could be a "for now an ' embedded single quote in a string" /* and for
this could be a "string with an escaped double quote \" inside"
wow */ going well
this could be a "string with an escaped double quote \" inside"Here is a test using lang="cs":
this is a "string"
for a 'string' in some languages
this could be a "for now an ' embedded single quote in a string" and for more text
this could be a "for now an ' embedded single quote in a string" and for more text
for a "for now an ' embedded single quote in a string" and // for more text
this could be a "for now an ' embedded single quote in a string" /* and for more text */ here
this could be a "for now an ' embedded single quote in a string" /* and for
this could be a "string with an escaped double quote \" inside"
wow */ going well
this could be a "string with an escaped double quote \" inside"and now re repeat all the above once more:
this is a "string"
for a 'string' in some languages
this could be a "for now an ' embedded single quote in a string" and for more text
this could be a "for now an ' embedded single quote in a strThanks Luc - I've added this to our todo.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Thanks Luc - I've added this to our todo.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
It's no biggy. Zero priority would be fine by me. I'd rather see you fix the HTMLtag+newline issue in the message editor (newline getting eaten). :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).