Lack of pasting Japanese lyrics is expelling Japanese Dorico users (who engrave lead sheets) to Cubase.
(They were taught to use Cubase to make lead sheets, but to me it is far less efficient than using Dorico to make high quality lead sheets… except lyrics input.)
I know you Dorico team have your reasons of prioritizing the sequence of function development.
I am just addressing this fact here to let you people beware of that.
Is this what YAMAHA Japan really want to see?
What’s the problem with pasting Japanese lyrics, Shiki? You mean the fact that Dorico doesn’t automatically paste each ideograph from the clipboard to each rhythmic position and advance automatically? Or something else?
I embolded the issue from the quoted text above.
I tested in Dorico 3.5.0 release:
For pure-latin contents in clipboard (only half-width characters are used), Dorico behaves well in doing that. (ex.: copy something like “a i u e o” and continue pressing CMD+V produces ideal results, seeing each content section (separated by spaces) were put per note.)
For CJK contents (including Japanese contents), Dorico was doing well in Dorico 1 and 2, but is not doing well since Dorico 3.0 till now 3.5.0 release. (ex.: copy something like “あ い う え お” or “あ い う え お” and continue pressing CMD+V won’t produce the same ideal results.)
In principle we’d like to make this feature available to users writing in CJK scripts, but there is quite a bit of complexity inherent in this kind of thing, due to the vagaries of text encoding. Even the workaround suggested here by JesterMusician may not work reliably depending on the encoding of the text you are using. Whether the text is encoded as UTF-8 or UTF-16 and which specific space character is used (there are 25 different whitespace characters defined in the Unicode standard). We could even potentially take the approach of ignoring whitespace altogether and automatically pasting the next character at the next position, but this also requires that different text encodings are handled gracefully.
All of this is possible, of course, but it is non-trivial and takes time. Hopefully we can put some more time into this area in future.
At this moment I guess Dorico can only treat U+3000 and U+0020 as spaces for parsing lyric contents from Clipboard and the batch lyric input box.
Others are too unpopular to be used in lyrics.
Regarding UTF-8 and UTF-16, I guess an option can be placed in Dorico Preferences to do any of the following choices:
Specifically treat lyrical data input as UTF-8 (including Clipboard);
Specifically treat lyrical data input as UTF-16 (including Clipboard);
Do nothing specific to lyrical data encoding identification.