hello,
I imported a file via music.xml format.
In the composer field a line break was shown - as in the imported file.
I looked up the project info in Dorico.
Here I could only see empty spaces (probably with some hidden info about the line break).
Anyway, I started to experiment:
If I put into the project info field {n} I would get a line break - but with {n} visible at the end of the first line.
If I put into the project info field [n] I would get a line break - but with [n] visible at the beginning of the second line.
So I guess there must be some (hidden) commands we could use to get line breaksā¦
Off the top of my head I canāt tell you what the character codes are. What I do know is that Iāve happily been copying and pasting both line break characters and tab characters from Microsoft Word into the various Project Info fields in Dorico, and they seem to display correctly in the score itself.
Yep. What Iām saying is that you create the line break or tab space in Word. With āparagraph marksā visible in Word, line breaks (for example) show as a kind of arrow, similar to the arrow that exists on the Return/Enter key on certain computer keyboards. If you paste that paragraph mark into Dorico from Word, it will remain invisible but force the next character(s) onto the following line.
This certainly works for the āmore informationā field - I canāt speak for the ācomposerā field as Iāve not tried there.
I am searching for a native solution to solve this issue as well. I do not see how old this post is. Sometimes composer or lyricist text ist colliding in my project with a text of the flow name. I would like to be able to decide where a would break a line without opening third part application like Word etc. For example:
pianoleo, sorry, I am still hanging on this topic as I need a solution. I opened Word on my Mac any way I am not able to find this setting. Would help me please what exactly I do have to check? I am on a newest Word 2019ā¦
Thank you very much for your idea. This could be a solution any way a quite unintuitive one. How many FlowHeadings would you create when there is some collision between more than 2 elements? For example FlowName, Composer and Lyricist? I would still suggest - Dorico team do have to take it in considerationā¦ Conceptually it seams Dorico creates a rule first and then on top of it comes with a solution as exception. Like hiding staves. You must hide all empty staves and then āallowā not to be hidden some of them instead just to choose what you would like to hide. I miss somehow simplicity hereā¦
It totally depends on the context. Usually I create my Headings in a way that no collision is possible, so I donāt usually need any additional flow headers.
But again, this is exremely context dependend. I would create a new one for any case that the existing one doesnāt work. But I would also consider using only the adjusted one for consistency throughout the whole file.
As for hiding staves: AFAIK you donāt need to enable āhide stavesā in Layout Options first but can just hide any staff by double clicking system breaks.
Yes; this is why I requested a year or two ago that two or three generic data fields would be added too. My poor little brain sometimes gets confused when I use a clearly labeled token for something it is not meant for; conversely I have an easier time when I just use āother infoā. Iād just also love an āother info 2ā and āother info 3ā for instance. Also, if I had my druthers ācomposition yearā would be changed to āComposition dateā too. I often mark specific dates if I write the whole thing in one day. Thatās a little thing, but it just feels weird typing in a month and day into a āyearā category. We artists are āsensitiveā soulsā¦ lol
I agree. I also misuse some fields sometimes (mostly the lyricist because I usually donāt have one ). Some more āother infoā or āgeneric token fieldsā would be really nice, but itās not a big hustle.
True, and no doubt the team will rightly ask, ābut where does it end?ā And then the only sufficient (if unreasonable?) answer I could give would be user definable fields/tokens. But that would open up whole cans of worms which I doubt are very worth tackling right now.
While I certainly agree that line breaks should be possible in any field (pro tip: you donāt need to outsource to word to insert one; just use the āother fieldā to format the line breaks where you want them and then copy that field up to its final target field) donāt forget that thereās also a composer dates token (which should probably be put up next to the composer field). Hereās a little mockup of what I mean.
I want to support the request for line breaks in tokens and/or for flexible flow headers (and footers).
I do a lot of collections with very different pieces. Some have only one movement, some have two or more movements and need subtitles. Some have only a composer and some also have an arranger and so on. It would be very time saving, if Dorico could have flexible flow headings, where empty fields are left out and/or line breaks automatically adjust the height of a text field.
A big problem are copyright entries. Some copyrights only need one line, but there are a lot of companies, who demand an epic copyright notice with a lot of lines. A flexible flow footer would be brilliant! Just dreaming ā¦
So far I normally end up with lotās of flow heading changes and with lotās of red triangles and all the magic of Doricoās automatisms is gone.
flow footers have also been requested in the past and this is something I would really welcome.
I would LOVE flexible flow headers where you could define the order the fields should appear if data is assigned to them for that flow but that remain hidden if there is no data. I suppose in theory you could craft a flow header to achieve this already, but it would leave all sorts of blank space on the ones that only have a little bit of text. Still though, this would be rather clever.
). Some more āother infoā or āgeneric token fieldsā would be really nice, but itās not a big hustle.