I wish I had the time to help you solve the MORE / CONT'D feature. That's be pure awesomenesses.
Can you explain this issue? Maybe someone will take up the charge.
When either a scene or a bit of dialogue spans a page-break indicators are placed in the scene and in the dialogue that tell you the scene, or bit of dialogue, continues on the next page. It looks like this:
INT. STORE ROOM - NIGHT
Darcy sits alone.
DARCY I can't stand just waiting here. (more)
(CONT'D)
-----------------Page-Break-----------------------
(CONT'D:)
DARCY (CONT'D) Give me something, anything...
The only place this pops up in is when printing to PDF. As of now the PDF creation is handled by PrinceXml, so prince determines where the page-breaks should go. Because prince is deciding where the page- breaks go prince would need to determine when it needs to place the "continued" indicators.
I'm using Prince because it's easy to install and I can leverage the HTML conversion I can do to create the PDF. People have suggested that I could get much more sophesticated odcuments using LaTex but I've found it to be a large download, a pain to install, and yet another document language I'd have to learn. So, I'm not too interested at this point.
But to be frank, this issue is not a priority.
On Mar 15, 2007, at 2:38 PM, Oliver Taylor wrote:
I wish I had the time to help you solve the MORE / CONT'D feature. That's be pure awesomenesses.
Can you explain this issue? Maybe someone will take up the charge.
When either a scene or a bit of dialogue spans a page-break indicators are placed in the scene and in the dialogue that tell you the scene, or bit of dialogue, continues on the next page. It looks like this:
INT. STORE ROOM - NIGHT
Darcy sits alone.
DARCY I can't stand just waiting here. (more) (CONT'D)-----------------Page-Break-----------------------
(CONT'D:)
DARCY (CONT'D) Give me something, anything...The only place this pops up in is when printing to PDF. As of now the PDF creation is handled by PrinceXml, so prince determines where the page-breaks should go. Because prince is deciding where the page-breaks go prince would need to determine when it needs to place the "continued" indicators.
I'm using Prince because it's easy to install and I can leverage the HTML conversion I can do to create the PDF. People have suggested that I could get much more sophesticated odcuments using LaTex but I've found it to be a large download, a pain to install, and yet another document language I'd have to learn. So, I'm not too interested at this point.
But to be frank, this issue is not a priority.
I know you could use some of the fancier page layout capabilities of CSS3 to dynamically insert this stuff. Then you could just print to PDF from Safari of FireFox.
http://alistapart.com/articles/boom
thomas Aylott — subtleGradient — CrazyEgg — sixteenColors
Thomas Aylott (subtleGradient) wrote:
I know you could use some of the fancier page layout capabilities of CSS3 to dynamically insert this stuff. Then you could just print to PDF from Safari of FireFox.
Oh man! That cross reference stuff is hot! Does that work in current webkit nightlies?
Can we come up with a way to make things like the TextMate documentation work with this stuff?
Can we get bundle documentation, cheat sheets, etc. all styled for screen and print?
Because that would be absolutely awesome. Users could get a paper copy of the documentation for their favorite bundles, including cheat sheets, etc.
Are any others interested in figuring out guidelines and stylesheets for such things?
-Jacob
-
Jacob Rus -
Oliver Taylor -
Thomas Aylott (subtleGradient)