Are you rich?
Here's strategy, build a tree using TreeBuilder,
yank out all the unique font tag combinations, make each a classid, make the appropriate substituions, and you're done.
Then do the same for other tags, such as P or Table , Td ... you get the picture.
The big problem curious bit as I see it is generating meaningful names for the class id's,
especially if humans are gonna be looking after this later.
update: CountZero interesting, but font tags are <font> tags, not h2 or h1 or whatever. One thing he needs for sure is to identify similar markup(whatever that may mean) and translate that into a css equivalent. However exactly he decides that is up to him (he has the tree so he can go buck wild).
MJD says you
can't just make shit up and expect the computer to know what you mean, retardo!
I run a Win32 PPM
repository for perl 5.6x+5.8x. I take requests.
** The Third rule of perl club is a statement of fact: pod is sexy.
|
-
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.
|
