comment on

Text markup, whether it's in human readable format such as HTML, or in a machine readable format such as with MS Office, targets a particular rendering engine. HTML targets web browsers (among other entities) that understand HTML. Let's say you manage to come up with a whiz-bang markup language that fits some well-defined niche. What use is it if there is no tool that knows how to render it?

Once you decide what you want to target (a browser, ...or who-knows-what else), then the markup language is already decided for you.

Perhaps you want to translate one simplistic markup language of your design into a more complex one that already exists; perl-j-markup2html, perl-j-markup2pod... whatever. What makes your new language better or more practical, and for what application, than what's already out there? Why would I want to learn perl-j-markup when I already know HTML?

Maybe you already have answers to these questions. If you do, you are well on your way to defining the problem and the use case. But with no use case, you're just in search of a problem that doesn't need a solution.

Dave

In reply to Re: Make a Markup Method in Perl? by davido
in thread Make a Markup Method in Perl? by perl.j

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks