Text with a resizable extention line? Possible?

I’d like to create some text in a score that has a line (preferably dashed with a hook).

Something like this : “multiphonique” - - - - - - -\

I can’t find a way to do this ? Any ideas ?

Build a custom playing technique, and read the Dorico 3 Version History for how to add continuation lines etc.

I’ve read the manual for over a half hour. I’m finding the on-line help manual very incomplete !!

In the search box I write “playing technic continuation line” or “playing technic line”, and lots of items appear, but not what I’m looking for.

So frustrating !!!

I said read the Version History, not read the manual.

So I have to read a 74 page document to find something !
So on page 47 this is called “Grouped playing techniques”. If Dorico on-line help, I type “Grouped playing techniques”, no correct answers appear.

I type “continuation line” THAT’S HOW THE VERSION HISTORY CALLS THESE, and in the help manual they speak about pedal lines, but nothing else that I can see.

The manual is VERY poorly written !!!


rant over, Many thanks @Pianoleo

The whole reason the Version History exists is that the manual can’t keep up with the pace that the software is updated. I told you that what you were looking for was Playing Techniques, and Continuation Lines, and I told you where to look for it. If I had it in front of me I’d give you a page number, but I thought you’d want an answer quicker than I could stop what I was doing and grab a computer.

If you happened to be asking for functionality that hadn’t been added to the software in the past month, the manual would be a very good place to look. As it happens, you were asking for a recently-added feature, and as such, the best documentation is the Version History.

I said “many thanks” @Pianoleo !!

It’s been over 1 or 2 months that Dorico 3 is out, and the manual isn’t complete ? I wonder what take more time, coding new technics or just explaining them in the manual. I guess the Dorico team has enough people to code the program (I’m loving it), but nobody to just friggen copy and paste the version history explanation in the manual ? Incredible !!!

The Version History is written by Daniel. The Manual is updated by Lillie Harris. It’s not as simple as “copying and pasting the friggin’” anything, because The writing style is somewhat different. The Version History gives basic details of everything, but not the same number of simple tutorials detailing the minutiae of how to do each little thing. Also, there’s ongoing stuff with regard to various translations of the manual.

There’s no need to throw stones about this; it’s always been that new functionality is explained in the Version History. Seriously, for the first year there wasn’t a manual at all. We managed :wink:

jamwerks, please don’t shout. [All caps and excessive exclamation points.] Shouting’s only constructive purpose is to warn someone they’re in imminent danger, like if a piano’s about to fall on their head. In every other context, it’s uncalled for and destructive (not to mention self-defeating). Please show everyone the respect you yourself would wish to receive.

jamwerks, I understand your frustration that not every feature in Dorico 3 is yet documented in its online help. Lillie is working hard to catch up, but she is also playing an important role in managing the updating of the non-English documentation, and she also splits her time between working on Dorico and her own career as a composer and a copyist. We’re fortunate to have somebody with Lillie’s skills and experience on the team, but she is just one person.

I am also sorry that the online manual doesn’t yet include everything released in Dorico 3, and I am indeed working to fill in the remaining gaps as quickly as possible whilst also ensuring that what I write is as accurate, helpful, and sufficiently cross-referenced as possible.

Here’s a little more information about how Steinberg manuals work in case it helps you understand the process (and why it’s not quite as simple as copying and pasting text).

We write the manuals in XML, as this allows us to write content that can be published as both a PDF and in the online help format from the same source. This involves carefully marking up text using a different element according to its function: titles, index entries, menu options, quotations, and so on all have their own tags and correct placement in the file, so the authoring experience is very different to writing in a word processor; for a start, every separate page in the online help is its own file with its own title, body, index entries, related links - etc. In order to maintain as much control and accuracy as possible over not just a single manual (and the Dorico manual is already edging towards 400,000 words despite mine and the Steinberg editor’s best efforts to keep it succinct) but all the manuals for all Steinberg products, we in the manuals team have strict rules for what content goes where, what markup to use, and what agreed terminology and phrasing to use; it’s vital that I’m bearing these rules in mind at all times.

This means that although I use basically everything in the comprehensive version histories in the manual (which definitely speeds up the documentation process enormously), I still have to parse out the content Daniel has carefully written for each feature into the suitable DITA categories, condense information down in some places and expand in others. To make sure I’m explaining any necessary steps correctly, I always double-check by doing the thing I’m describing in Dorico myself, and sometimes this prompts questions for my colleagues where I want to clarify something’s behaviour/restrictions etc. I also have to take suitable screenshots of notations, dialogs, and buttons with the image file type and resolution that is required by our publication processes in order to produce correctly-sized images (harder than it sounds). It is also necessary to comb through the existing manual when I add new content, to check for any knock-on effects a new feature might have to existing features/documentation (which is quite hard to automate).