Note: non-ascii characters have indeed been widespread for a long time, but here's an example: if you get a bunch of attached files in Yahoo mail and choose a bulk download, yahoo zips them up for you. Then you unzip the file and find that the non-ascii characters have been corrupted.
Yahoo is probably the second or third biggest email provider in the world and they don't support non-ascii characters... I think I can get away with doing the same in my hobby project, even though I did attempt to one-up them. Spaces are less of an issue. I personally think it's not a good idea to use spaces in a filename, but they don't seem to cause a problem in the aligner.
-
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.
|