comment on

My profession started out with grafic design and typography is one of my passions. Now I'm working with monospaced code most of my time, and I'm often trying to link those fields in one way or another.

Considering the rational, informational aspect of visual/written communication, I think that less is more. We need only a few simple, structural elements and one most readable font family. Data structures might be POD (very sexy ;), XML (flexible), HTML (quick & dirty), you name it... To keep things straight, most of the actual visual interpretation should be left to the user. He's interested primarily in the information, not our visual style.

When you're up for individual, high quality design however, you will need specialized tools that let you do the design, not the markup (thinking of QuarkXpress, Freehand, Photoshop etc.)

Keep it straight and simple!

^~Django

"Why don't we ever challenge the spherical earth theory?"

In reply to Re: Perl Typesetting by Django
in thread Perl Typesetting by crenz

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.


Don't ask to ask, just ask
	PerlMonks