Syntax Highlighting is sometimes wrong with strings / quotes / quotation marks

Notably, it fails to parse Python's triple-quote (''' or """) multi-line strings as such.

Thanks for letting me know!

I have also had problems syntax highlighting. Here is an example. Hope this helps!


http://i671.photobucket.com/albums/vv73/Calumks/photo.png


I don't think my coding is wrong. I'll feel so dumb if it is lol.

Thanks for the screenshot! Yes, the syntax highlighter doesn't like alphanumeric characters in front of quotes.

So, in your case, the syntax highlighter does the right thing when you insert a space after "echo" like this:

echo '<p align="center">'.$copyright.'</b>';

Sorry for the inconvenience.

That worked! Thanks :).

For me, slash escaping of quotes is where things are going wrong (Python source). Many of my source files have strings like "isn\'t" in them. All source below them is then incorrectly syntax highlighted.

I'm seeing this with java code: double quoted strings that contain single quotes (apostrophes). Highlighting is broken in subsequent text. I gunk ill be seeing a lot of code that suffers from this bug..

 The new highlighter with potential for code completion sounds exciting!

Ps: it's my iPad that likes to gunk things - personally i prefer to think I'll be seeing a lot of code that suffers from this bug.. (;

I haven't seen the new implementation but just in case...

The current one gets very confused on Perl regular expressions with single quotes.

For example

$str =~ s/\'/\\\'/g; # '# Convert all ' to \' '

I added the '# to get most of the comment rendered in grey and the trailing ' to make the number of quotes even so the following lines rendered correctly

This will work in Textastic 3.0.

Got the Same with PERL here...


$vRow =~ s/\!FOLDER_ID\!//cg;

after this line, no more Syntax is recognized :)

This works for me in the latest version of Textastic. Maybe there is another part in the file that causes this problem?

Not really- I changed that in the source and the Syntax was fine from that point on. It's the // that causes the trouble here.