Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add switch for HTML5 and XHTML5 #8

Open
designermonkey opened this issue Jun 13, 2013 · 11 comments
Open

Add switch for HTML5 and XHTML5 #8

designermonkey opened this issue Jun 13, 2013 · 11 comments

Comments

@designermonkey
Copy link
Member

We should have a switch to allow the use of XHTML5

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title></title>
<meta charset="UTF-8" />
</head>

<body>
</body>
</html>

The above is valid markup for XHTML5 and allows the use of namespaces in the HTML. This has been an issue raised on the forum for how to use namespaces like the (horrible) Facebook ones in HTML5.

A switch in the Preferences page would allow a choice in output, and would switch regular expressions.
@michael-e
Copy link
Member

I don't see the problem. Do you say that namespaces are not allowed in HTML5?

@designermonkey
Copy link
Member Author

They don't validate without the xmlns on the html tag.

@designermonkey
Copy link
Member Author

Do you say that namespaces are not allowed in HTML5?

I'm not going to say that again. o_O

@michael-e
Copy link
Member

Well, you are right. I just did some research on the matter. So it sounds like a good idea, if you really want HTML5 to validate. :-)

(I myself am somehow disappointed by the fact that it doesn't need to validate. So why should I try?)

I somehow feel bad about changing the extension just because someone invents his own namespaces. Can you give an example of FB namespaces that are useful to a document???

@designermonkey
Copy link
Member Author

None. There are no useful Facebook anythings.

Just thought that it might be useful to some.

@michael-e
Copy link
Member

So shouldn't we wait for a useful example before hacking the extension? :-)

@bauhouse
Copy link
Member

Or we could hack it and make it available as an alternate branch: xhtml5

@designermonkey
Copy link
Member Author

Bonza!

@michael-e
Copy link
Member

:-)

@designermonkey
Copy link
Member Author

I've been reading a lot more about XHTML, polyglot syntax, HTML5 etc etc, and it is correct to leave the xmlns attribute at least, as we are using a system that deals with XML to output HTML5, we should definitely change the behaviour of this extension.

Personally, I would now just make the change without any kind of choice, but in favour of not ruffling feathers, it should be a choice in the preferences.

I will make the change in a branch, and ask for support before merging.

@designermonkey
Copy link
Member Author

Nope, the work was already done.

I've been away too long :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@michael-e @bauhouse @designermonkey