Space between value and unit?
No tragic error, but between value and unit (e.g. in inspector X/Y values, percentage values) there should be a space, right? I didn't notice this in MuseScore 2, it was probably the case there, too.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4785, revision: c1a5e4c
Comments
It's a stylistic decision, kind of like Oxford commas and the neverending debate about whether to apostrophes when forming the plural of numbers.
In reply to It's a stylistic decision,… by Marc Sabatella
not only that, it is also forced on if from Qt, when using suffix and not manually adding a space (which would be bad for translations)
I remember a (very!) heated discission about this topoc some years ago...
In reply to not only that, it is also… by Jojo-Schmitz
Sorry, I had searched the forum and didn't find anything and didn't even notice it all those years (I only read your last sentence now)!
As for QT, Scribus uses it too, but an older version (5.6.3 or so) and they use spaces. So, and now I will keep silent on this subject.
In reply to It's a stylistic decision,… by Marc Sabatella
I wouldn't call it stylistic, but rather artistic or programmer's freedom. Typographically, it does not correspond to conventions, the same applies to scientific specifications ("The International System of Units (SI) prescribes inserting a space between a number and a unit of measurement").
Of course, it is up to the programmer to make such decisions when problems arise, e.g. with translation or QT or something else. I suddenly noticed it and thought it was no big deal.
Thanks for reporting this. It also bugged me, and I recently found the SI reference, and today by happenstance found the Qt5 reference indicating that, yes, Qt5 very much wants the programmer to ensure there’s a space there.
PR created: https://github.com/musescore/MuseScore/pull/4672
See https://musescore.org/en/node/23591 http://musescore.org/node/23621, #23622: Missing spaces between numbers and units in spinboxes, with very heated discussions ...
In reply to See #23622: Missing spaces… by Jojo-Schmitz
I see that back in 2013 I wrote, "I hope to not respond on this topic again", but I guess six years is long enough :-)
Back then I had said I personally didn't think it was important enough to be worth spending time on, but that if someone else were to feel otherwise and were to actually do the work, I wasn't about to argue against it based only on my own personal preference. That remains true. My personal preference remains to see no space in UI design even though the space might make sense in the sort of ordinary writing contexts discussed by various standards bodies. But that's just my own personal preference. If the consensus is that the right thing to do is to adopt the attitude that (in this instance at least) ordinary writing rules should prevail for UI design as well (even though they clearly don't elsewhere), then I'm all in favor of seeing some sufficiently motivated person spend their time on this. Since this has now already happened, great, I applaud the effort, and I'm happy to see MuseScore be part of this eventual worldwide move toward UI standardization.