Jump to content

Are There More Markup Languages Other Than Html?


ferrari

Recommended Posts

XAML is proprietary markup used by Silverlight, WPF, and Windows 8 to denote where data bound, interactive elements are on a page. It's not an all-purpose markup language.

 

Again, the answer is HTML. It's one of the foundational technologies of the web, and there's no reason not to use it.

there's no reason not to use it.
My previous company actually did all their markup through XML and XSLT.  No "HTML" on the entire site, it was all translated by the XSLTs, mostly automatically by the generic "translate page" function.

My previous company actually did all their markup through XML and XSLT. No "HTML" on the entire site, it was all translated by the XSLTs, mostly automatically by the generic "translate page" function.

 

I'm assuming you didn't have your hands in the development of the XSL-T and aren't completely familiar with how it works.

 

XSL-T transforms XML into another format. Very commonly, it's used as a templating scheme to transform XML into HTML, which is likely what your previous employer was doing.

HAML seems cool I have to say.

 

Seems pointless to me. It's like CoffeeScript, or Hibernate, or any ORM in existence. Abstraction of a common language for the sole purpose of making it "pretty" does 2 things:

 

1. it requires developers in your group to double their knowledge-base, and

2. it slows down a) deployment time, or b ) website speed

 

EDIT: 3) It makes debugging a pain in the arse... because you have to manually map out the error in your translated code to the actual line of code that generated it.

yes, obviously XSLT was used to transform into HTML, that's how web pages are made.  We used XML so that we could build pages using SimpleXML and so all our documents would be well-formed.  XHTML would have been just as good, really, but there were other side benefits, like firefox opening up our source documents as traversable trees instead of pages.

yes, obviously XSLT was used to transform into HTML, that's how web pages are made. We used XML so that we could build pages using SimpleXML and so all our documents would be well-formed. XHTML would have been just as good, really, but there were other side benefits, like firefox opening up our source documents as traversable trees instead of pages.

 

Gotcha. Misunderstood what you were saying (seemed like you thought there was no HTML involved). So you did this in PHP? Did you use Sablotron to do server-side transformation for browsers that don't support XSL-T?

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.