trioshed.blogg.se

Macjournal data
Macjournal data











  1. #Macjournal data update
  2. #Macjournal data windows

#Macjournal data update

For that reason no past entries can be considered definitive, and I find it easier to update them within the scope of a single document

  • It isn't just a diary of ongoing events - I also continuously insert and update early entries, based on various sources from that large chunk of my life when word-processors, and indeed computers, didn't exist.
  • Up to now I have had two reasons to keep my document in a single file: Needless to say, as time goes by, my masterpiece can only get longer! I too keep a daily diary - nowhere near as long as Ken's but long enough to cause a longish "typsetting text" phase while opening it, which I always do in draft mode. This topic encapsulates a number of concerns I've had for a while. Hi (and a very Happy New Year to all Nisus users and official persons), So if you are seeing big(ger) differences that might indicate that there is something wrong with your file perhaps?
  • Nisus ≈ 10-12 secs (zrtf only a smidgen faster).
  • Nisus probably can't be optimized for everything.Īnyhow here are my (anecdotal) comparisons (hand-timed by stopwatch): So in the end it probably comes down to the old question of using the right tool for the job. In Nisus scrolling seems completely smooth and effortless to me. OO is pretty fast opening, but it does something really strange with scrolling: it allows you to grab the slider and scroll when you are at the beginning of the file, but if you are in the middle, you can no longer "grab" the scroll-slider at all! Scrolling in Pages also seems somewhat jerky.

    macjournal data

    (Nisus of course saves in rtf, which perhaps requires some translation at opening time?) Saving that way can certainly be a way to speed up loading.

    macjournal data

    Pages and OpenOffice save the file in their own dedicated formats, and Pages format causes the file size to balloon. Having said that, there are probably other points to consider. Switching to page view with Nisus is almost interminable (and seems to only work well if you first place the cursor at the beginning, so that it can 'start from the beginning').

    macjournal data

    What's more, both Pages and OO go directly to a page view. And it is true that Pages (but not OpenOffice, don't have Word) is somewhat quicker at opening this, than Nisus even in Draft view. I downloaded several novels from Project Gutenberg and combined them into a single file to get a 5 Mio character file (about 2000 pages). Size is tolerable up to a point, but one does have to wonder why it is important to keep this all in a single file, which you then want to use for daily editing.īut returning to the real question: I tried the following experiment. I don't have a lot of experience with files that size. You might switch to using Draft View for some documents. One final tip: Draft View's typesetting is a lot simpler because there's no need to consider pagination, footnotes, etc.

    macjournal data

    If the delay in a particular document seems inexplicably long, you might send us the file so we can see if there's anything amiss, or something we can optimize to speed the typesetting time in the future. That's just a partial list, but as you can see, there's a lot going on.

    #Macjournal data windows

    Preventing windows & orphans and enacting other layout options. Deciding where tables, floating graphics, footnotes, etc, should be placed and then wrapping text around them.ĥ. Calculating the way lines of text are laid out on the page, and wrapping them based on the margins, indents, etc.Ĥ. Taking text character codes (ie: Unicode) and mapping those to glyphs in the final display font.ģ. Calculating the final displayable formatting for each bit of text, eg: combining paragraph styles, character styles, and attribute overrides.Ģ. There's a lot to that, but here's a rough overview of some of what goes on:ġ. Hi Ken: typesetting is the process by which your document's content is prepared for display on screen.













    Macjournal data