Talk:Sagittal notation: Difference between revisions

Line 54:

: Setting aside that wiki talk pages are usually reserved for discussion about the wiki (description of existing work), not the topic itself (I suppose the best place would be the Sagittal forum), I believe that simply using a natural accidental followed by a restatement of whichever accidental needs to be carried over should suffice. That logic could be applied to any combination of two accidental symbol sets, although I know the rules for Kite's ups and downs are slightly different, e.g. an arrow alone implies a natural accidental, cancelling any prior sharp or flat. Furthermore, I think the Sagittal notation system is largely flexible enough to accommodate rank-3 tunings without any other symbols, especially the revo set. --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 14:31, 21 July 2026 (UTC)

::Thanks, Fredg999, that's well answered. Yes, Lucius, please post suggestions like this to https://forum.sagittal.org in future, when they are not about this wiki article. There are in fact two purely-Sagittal naturals that you could use for this purpose, although they were not intended for it. They are the bare shafts up and down, {{Sagittal||}} and {{Sagittal|!}}. See https://w3c-cg.github.io/smufl/latest/tables/herculean-sagittal-extension-very-high-precision-accidental-diacritics.html. [[User:Dave Keenan|Dave Keenan]] ([[User talk:Dave Keenan|talk]]) 01:36, 28 July 2026 (UTC)

Revision as of 14:31, 21 July 2026 view source Fredg999 (talk \| contribs) autopatrolled, Bureaucrats, Interface administrators, Sysops 6,817 edits →Hybrid of Revo Sagittal with HEJI, Sagittal Natural?: Re ← Older edit		Revision as of 01:36, 28 July 2026 view source Dave Keenan (talk \| contribs) autopatrolled, emailconfirmed 2,271 edits Thanked Fredg99 and told Lucius about Sagittal naturals. Newer edit →
Line 54:		Line 54:

	: Setting aside that wiki talk pages are usually reserved for discussion about the wiki (description of existing work), not the topic itself (I suppose the best place would be the Sagittal forum), I believe that simply using a natural accidental followed by a restatement of whichever accidental needs to be carried over should suffice. That logic could be applied to any combination of two accidental symbol sets, although I know the rules for Kite's ups and downs are slightly different, e.g. an arrow alone implies a natural accidental, cancelling any prior sharp or flat. Furthermore, I think the Sagittal notation system is largely flexible enough to accommodate rank-3 tunings without any other symbols, especially the revo set. --[[User:Fredg999\|Fredg999]] ([[User talk:Fredg999\|talk]]) 14:31, 21 July 2026 (UTC)		: Setting aside that wiki talk pages are usually reserved for discussion about the wiki (description of existing work), not the topic itself (I suppose the best place would be the Sagittal forum), I believe that simply using a natural accidental followed by a restatement of whichever accidental needs to be carried over should suffice. That logic could be applied to any combination of two accidental symbol sets, although I know the rules for Kite's ups and downs are slightly different, e.g. an arrow alone implies a natural accidental, cancelling any prior sharp or flat. Furthermore, I think the Sagittal notation system is largely flexible enough to accommodate rank-3 tunings without any other symbols, especially the revo set. --[[User:Fredg999\|Fredg999]] ([[User talk:Fredg999\|talk]]) 14:31, 21 July 2026 (UTC)

			::Thanks, Fredg999, that's well answered. Yes, Lucius, please post suggestions like this to https://forum.sagittal.org in future, when they are not about this wiki article. There are in fact two purely-Sagittal naturals that you could use for this purpose, although they were not intended for it. They are the bare shafts up and down, {{Sagittal\|\|}} and {{Sagittal\|!}}. See https://w3c-cg.github.io/smufl/latest/tables/herculean-sagittal-extension-very-high-precision-accidental-diacritics.html. [[User:Dave Keenan\|Dave Keenan]] ([[User talk:Dave Keenan\|talk]]) 01:36, 28 July 2026 (UTC)