-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"data[c]" in c code showed as "data1" #26
Comments
Hmm, works fine for me: http://alexpublictest.wordpress.com/2013/10/22/syntaxhighlighter-evolved-issue-26-test/ |
Could you help me on this? It's strange. Why I always get "1" for "[c]" or "[cpp]" or "[php]" in the source code highlighting here? |
Can you provide a URL to where this is happening for you? It's hard to debug without seeing it for myself. |
Please see https://96.126.98.8/blog/?p=1837 |
Check out the HTML source code of the page -- the "data1" there as well so the issue is NOT with the highlighting package. The problem is either with my plugin or another plugin you have enabled. I recommend you start by disabling all other plugins that you have active (except mine) to see if that resolves the issue. You can also check the database to see what the |
Thanks. I have disabled all other plugins besides yours, but the problem wasn't fixed. And I also checked the post_content value, it looks like this, it's "data[c]" there: [c] for (c=0;c<=100;c++) for (c=0;c<=100;c++) |
The "<" and '"' in pervious comment are both converted to html's "&" format in the post_content. |
I just realized what's going on. You're using the shortcode Try doing this instead:
|
I have tested surrounding my code with [code lang="c"] and [/code]. But [c] is still showed as 1. In the mean time, I have disabled other plugins. |
Hello,
When trying to highlight c language code with syntaxhighlighter, the "data[c]" is showed as "data1". Something like this:
[code lang="c"]
char data[100];
int cpp;
for (c=0;c<100;c++)
data[c]="a";
[/code]
will be showed as this:
The text was updated successfully, but these errors were encountered: