Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
XHTML compliance
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
mhavila  
View profile  
(1 user)  More options Oct 21 2007, 1:08 pm
From: mhavila <mhav...@gmail.com>
Date: Sun, 21 Oct 2007 17:08:56 -0000
Local: Sun, Oct 21 2007 1:08 pm
Subject: XHTML compliance
I've just start using SyntaxHighlighter and loved it! Thanks for the
great work.

The only issue is it not being XHTML compliant, since NAME is not a
valid attribute in PRE as of XHTML 1.0.
Use the CODE tag, or use "code" as an additional class attribute
value, would suffice to identify the code blocks to be formatted, in a
valid HTML and XHTML strict syntax.

This topic was already covered by Ernest in the following post, and I
endorse his words entirely:
http://groups.google.com/group/syntaxhighlighter/browse_thread/thread...

Best Regards,
Marcio
Brazil


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
kevin@centropy.com  
View profile  
(1 user)  More options Nov 29 2007, 9:20 pm
From: "ke...@centropy.com" <ke...@centropy.com>
Date: Thu, 29 Nov 2007 18:20:42 -0800 (PST)
Local: Thurs, Nov 29 2007 9:20 pm
Subject: Re: XHTML compliance

On Oct 21, 9:08 am, mhavila <mhav...@gmail.com> wrote:

> The only issue is it not being XHTML compliant, since NAME is not a
> valid attribute in PRE as of XHTML 1.0.

I noticed this problem today and fixed it for myself. Hopefully it
works for others and maybe it can be included in the dist.

http://kev.in/2007/11/29/using-dpsyntaxhighlighter-with-valid-xhtml/

$ diff shCore.js.orig shCore.js
618c618
<                       if(tags[i].getAttribute('name') == name)
---

>                       if(tags[i].getAttribute('name') == name || tags[i].className.indexOf(name)==0)
627a628
>       FindTagsByName(elements, name, 'code');
657a659
>               options = options.replace(new RegExp("^"+name+"\\s"), ''); // Turn 'dp-hilite ruby:option1:option2' into 'ruby:option1:option2'

~Kevin

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
WishMaster  
View profile  
 More options Dec 29 2007, 8:04 pm
From: WishMaster <Goo...@noname-development.de>
Date: Sat, 29 Dec 2007 17:04:43 -0800 (PST)
Local: Sat, Dec 29 2007 8:04 pm
Subject: Re: XHTML compliance
If you use <textarea> instead of <pre>, name can be used without
making the (X)HTML invalid.

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google