It handles namespace prefixes exactly as I wanted it to
So? All I did was identify the features others might have to add to suit their needs.
It would be totally useless to me, for example, since the prefix isn't uniform across the documents I deal with. In fact, I've never encountered a situation where it was better to keep the prefixes.
For example, supporting comments is 2 minutes' work
I'm well aware that the changes are easy.
There is no need to do anything in a pre-/post-processor
Duh. There are many ways of changing it. I just suggested one.
So it shouldn't be surprising that I didn't bother to implement them in the code that implemented just what I needed for one project.
It's not. Why are you so defensive when I tell other people what they might need to adjust to suit their needs?
-
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.
|
