that's an interesting comment. Yes, it shouldn't be a problem. It is quite definitely a feature of SVG, an essential key to its flexibility. So even more than expecting it, I should have been looking forward to it.
I'm just looking for the right programming manner in which to express that flexibility. Many features become problems due to a context or situation with unaligned constraints. Choosing Image::LibRSVG and its comparatively small number of methods is just such a situation. And I mean my choice of the module, not the module itself ... I'm taking about the design decision.
I'm not sure I should apologise though. It's just far too common a perspective to take. At best I was cavalier in calling it a problem. At worst, careless. I could have made two spelling mistakes instead, I don't think it would be graver.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.