CTAN Comprehensive TeX Archive Network

CTAN new pack­age: rvwrite

Date: Au­gust 28, 2010 9:12:01 AM CEST
This should be at your lo­cal mir­ror. Jim Hef{}feron Saint Michael's Col­lege ................................................................................ The fol­low­ing in­for­ma­tion was pro­vided by our fel­low con­trib­u­tor: Name of con­tri­bu­tion: rvwrite Ver­sion num­ber: 1.2 Author's name: CV Rad­hakr­ish­nan Lo­ca­tion on CTAN: /macros/la­tex/con­trib/rvwrite Sum­mary de­scrip­tion: This pack­age helps to fix in­suf­fi­cient num­ber of write reg­is­ters. Li­cense type: lppl An­nounce­ment text:
The io reg­is­ters in TeX are of­ten a mat­ter of se­vere lim­i­ta­tion. When we try to type­set a doc­u­ment that loads a lot of pack­age's, it be­comes a non-triv­ial task to sat­isfy reg­is­ter re­quire­ments of var­i­ous pack­age's that com­pete each other. It is fur­ther com­pli­cated, if re­fin­ing the type­set copy in­volves us­age of more cus­tom pack­age's which want to write out a few streams for read­ing dur­ing sub­se­quent TeX com­pi­la­tions. LaTeX needs a few reg­is­ters by de­fault, some of the pack­age's might need a few more streams thereby re­duc­ing the avail­able num­ber of reg­is­ters to less than ten. At times, we have been forced to com­ment out a few write reg­is­ters which are seem­ingly un­used for the doc­u­ment in ques­tion to make avail­able nec­es­sary reg­is­ters for our cus­tom pack­age's. But, this is not an el­e­gant way, also, it re­quires de­vel­oper in­ter­ven­tion dur­ing the pro­duc­tion pro­cess. A pack­age namely, rvwrite.sty, is writ­ten to solve this nag­ging prob­lem.
This pack­age is lo­cated at http://tug.ctan.org/tex-archive/macros/la­tex/con­trib/rvwrite . More in­for­ma­tion is at http://tug.ctan.org/pkg/rvwrite (if the pack­age is new it may take a day for that in­for­ma­tion to ap­pear). We are sup­ported by the TeX Users Group http://www.tug.org . Please join a users group; see http://www.tug.org/user­groups.html .

rvwrite – In­crease the num­ber of avail­able out­put streams in

The pack­age ad­dresses, for doc­u­ments, the se­vere lim­i­ta­tion on the num­ber of out­put streams that pro­vides.

The pack­age uses a sin­gle out­put stream, and writes “marked-up” out­put to this stream. The user may then post-pro­cess the marked-up out­put file, us­ing , and the doc­u­ment’s out­put ap­pears as sep­a­rate files, ac­cord­ing to the calls made to the pack­age.

The out­put to be post-pro­cessed uses macros from the widely-avail­able Pro pack­age.

Copy­right2010 C. V. Rad­hakr­ish­nan
Main­tainerC. V. Rad­hakr­ish­nan



Guest Book Sitemap Contact Contact Author