Martin Fowler and Ruby

W

Weirich, James

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------=_NextPartTM-000-dba69d8f-3c50-41a8-9def-03ecbb0a1309
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C38130.4C02C24A"

------_=_NextPart_001_01C38130.4C02C24A
Content-Type: text/plain

Here's an interesting link...

http://martinfowler.com/bliki/MovingAwayFromXslt.html
<http://martinfowler.com/bliki/MovingAwayFromXslt.html>

--
-- Jim Weirich / Compuware
-- FWP Capture Services
-- Phone: 859-386-8855



------_=_NextPart_001_01C38130.4C02C24A
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2657.19">
<TITLE>Martin Fowler and Ruby</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Here's an interesting link...</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://martinfowler.com/bliki/MovingAwayFromXslt.html"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://martinfowler.com/bliki/MovingAwayFromXslt.html</FO=
NT></U></A>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">-- </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">-- Jim Weirich / Compuware</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">-- FWP Capture Services</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">-- Phone: 859-386-8855</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C38130.4C02C24A--

------=_NextPartTM-000-dba69d8f-3c50-41a8-9def-03ecbb0a1309--
 
J

James Britt

Gour said:
James Britt ([email protected]) wrote:




Thanks. Nice reading.
Thanks.


What do you think about using the same technology for transforming DocBook
documents into Latex-like ones?

I'm not that familiar with Latex, but from what I understand it should
be quite doable. The difficulty may reside in how much (or little) the
two formats map to each other.

In Rimport I use a somewhat different approach (perhaps similar to what
Fowler describes) where the code manually walks the tree, passing
elements and subtrees off to dynamically-invoked methods based on
element name and context. This may give you better control that
straight stream parsing, plus it saves you the trouble of having to
build your own subtrees.


James Britt
james_b AT neurogami DOT com
 
G

Gour

James said:
I'm not that familiar with Latex, but from what I understand it should
be quite doable. The difficulty may reside in how much (or little) the
two formats map to each other.

This doesn't bother me too much since it's always possible to map some
DocBook tags in some LaTeX-like equivalent. Actually, I'm thinking about
ConTeXt package.
In Rimport I use a somewhat different approach (perhaps similar to what
Fowler describes) where the code manually walks the tree, passing
elements and subtrees off to dynamically-invoked methods based on
element name and context. This may give you better control that
straight stream parsing, plus it saves you the trouble of having to
build your own subtrees.

Thank you for pointing me at Rimport. I'll take a look in order to learn
something :D

Sincerely,
Gour
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Members online

Forum statistics

Threads
473,968
Messages
2,570,153
Members
46,699
Latest member
AnneRosen

Latest Threads

Top