|
From: | Urs Liska |
Subject: | Re: ugly default output |
Date: | Sun, 01 Mar 2015 09:53:52 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 |
Am 01.03.2015 um 02:39 schrieb Steve
Lacy:
No, it is not. You completely misinterpreted this because you seem not to have read my prior comment to this thread (indicated by "repeat"). I'll put it another way. Say you were entering a _text_ document and have typed one sentence which is slightly too long for a line. If you're using a simple word processor it will probably break the last word to a second line, if your tool is smarter it may squeeze it to one line, which may looked cramped (-> this would be the case comparable to the OP's example). Now I'd say: If you intend to continue entering text then simply don't bother because the problem will go away. This is in no way equivalent to saying: sorry, the tool just isn't meant to typeset short texts. The other thing I said is: If the content of your document just doesn't fit on one line, given a page/line width and font size it isn't the fault of the tool but a problem inherent in the task. If you (and I _did_ write this in the current thread) _have_ to typeset exactly this sentence you'd have to edit the line width or the font size. And this is exactly what you'd have to do with the given score: - if the piece isn't complete then simply continue entering the music and _then_ look at the results. - if the piece were complete then you'd have to change the global staff size or the line width. Urs
|
[Prev in Thread] | Current Thread | [Next in Thread] |