Administrator
|
One of the remaining tasks blocking a stable 1.0 release is the creation
of the promised classes JSON file. I've now put together a classes file and I'd like to solicit the feedback of the community in advance of the next release (0.9), the distribution for which will include the classes.json file for the first time. The purpose of the classes file is to provide useful groups of glyphs for consuming applications. Classes are entirely optional, so it is not required that a glyph should be in any class. Likewise, glyphs can be in multiple classes. Consuming applications can choose to use the classes metadata to help work out how to handle different glyphs within a SMuFL-compliant font. You can download a preliminary classes.json file from the following URL: http://www.smufl.org/files/classes-0.84.zip The classes included in the preliminary file are as follows: combiningStaffPositions Contains glyphs that are available in ligatures with the "combining staff position" glyphs, in fonts intended for use in text-based applications. (N.B. not implemented in the current Bravura font, which is intended for scoring applications.) forTextBasedApplications Contains glyphs that scoring applications can generally ignore, i.e. these are useful for text-based applications (or for runs of normal text in scoring applications). This contains glyphs like the "Beamed groups of notes" range, pre-composed stems, pre-composed staff lines, etc. stemDecorations Contains glyphs that are designed to be positioned on stems. This is a useful class, because the individual glyphs that are intended to be drawn on stems are dotted around various ranges. multiGlyphForms Contains all glyphs that are designed to be used in combination to produce larger forms, e.g. ornaments, wiggly lines, etc. wigglesQuasiRandom wigglesVibratoVariable wigglesCircularMotion wigglesVibrato wigglesArpeggiato wigglesArpeggiatoDown wigglesArpeggiatoUp wigglesTrill These classes contain useful subsets of the "Multi-segment lines" range. ornaments Contains all pre-composed ornament glyphs, excluding the component parts in the "Combining strokes for trills and mordents" range. rests Contains all rests glyphs. pauses Contains all fermatas/caesuras, regardless of whether they are intended to be positioned above or below the note/staff. pausesBelow pausesAbove Contains only those fermatas that are positioned either above or below the note/staff, as appropriate. articulations Contains all articulations, regardless of whether they are intended to be positioned above or below the note/staff. articulationsBelow articulationsAbove Contains only those articulations that are positioned either above or below the note/staff, as appropriate. accidentals Contains all glyphs in all accidentals ranges. accidentalsPersian accidentals53EDOTurkish accidentalsAEU accidentals72EDOWyschnegradsky accidentalsSagittalDiacritics accidentalsSagittalPromethean accidentalsSagittalTrojan accidentalsSagittalAthenian accidentalsSagittalPure accidentalsSagittalMixed accidentalsHelmholtzEllis accidentalsJohnston accidentalsSims accidentalsSteinZimmermann accidentals24EDOArrows accidentalsStandard These classes contain useful subsets of accidentals, each class essentially providing all of the accidentals glyphs required for a given convention or system. noteheads Contains all glyphs in all noteheads ranges. noteheadSetSacredHarp noteheadSetNamesPitch noteheadSetNamesSolfege noteheadSetSquare noteheadSetRoundSmall noteheadSetRoundLarge noteheadSetSlashHorizontalEnds noteheadSetSlashVerticalEnds parenthesesNotehead noteheadSetHeavyX noteheadSetLargeArrowDown noteheadSetLargeArrowUp noteheadSetCircled noteheadSetDiamondOld noteheadSetDiamond noteheadSetSlashed2 noteheadSetSlashed1 noteheadSetTriangleDown noteheadSetTriangleRight noteheadSetTriangleLeft noteheadSetTriangleUp noteheadSetWithX noteheadSetCircleX noteheadSetPlus noteheadSetX noteheadSetDefault These classes contain useful subsets of noteheads, each class providing a set of noteheads, e.g. the notehead to be used for quarter notes and shorter, for half notes, for whole notes, etc., for different conventions. Are these classes useful? Are there any other obvious classes that should be included? Thanks in advance for your feedback, Daniel - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Steinberg Media Technologies GmbH, Frankenstrasse 18b, D-20097 Hamburg, Germany Phone: +49 (40) 21035-0 | Fax: +49 (40) 21035-300 | www.steinberg.net President / Managing Director: Andreas Stelling Managing Director: Kazunori Kobayashi, Hiroshi Sasaki Registration Court: Hamburg HRB 86534 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ############################################################# This message is sent to you because you are subscribed to the mailing list <[hidden email]>. To unsubscribe, E-mail to: <[hidden email]> To switch to the DIGEST mode, E-mail to <[hidden email]> To switch to the INDEX mode, E-mail to <[hidden email]> Send administrative queries to <[hidden email]> |
Free forum by Nabble | Edit this page |