And this question is probably more for Erwin:
- Are there tags that are mutually-exclusive - not logically, but programmatically - in that using both in one definition will result in error?
- If you open CompositeData.xml in a browser it will be parsed and will stop at syntax errors.
because I meant conflicts that will arise from FC, not syntax errors, but more like:
IIRC one may use either glyph names or glyph mappings in defining a glyph member, but not both.
Glyphs mappings are always processed first, then the glyph names.
No, it usually will not generate errors, but there is a strict order in the positioning.
Although Complete Composites can be of great use, we nowadays prefer the Anchor based approach.
Wonderful, thank you.
I think I got what I needed.
In spare time (sic!): I put together an xml file with what I understood about the CompositeData.xml and its rules. If it’s correct, maybe it will help others.
structure.xml (4.41 KB)
Yes, that seems to cover it all.
And the famous last question:
Copy the user data files to the user data folder and edit the copy. If it exists, FontCreator will use it in preference to the default CompositeData.xml file.
As in > instead of> , or > will use both> , and if there are definitions for the same composites, the user-created one will be used first?
It will use the one found in the user data folder.
Thanks.
That’s not so good. Have you considered an option where the user can select which xml file will be used, as in user, default, or both? Then in the case of both, all the default defs would be loaded, unless they also appeared in the user file, which would be used instead. Just an idea.
I suggest you post your suggestion to the FontCreator - Requests and Enhancements forum. If more people respond positive to it, we are likely to further improve it.
If you copy the CompleteComposites.xml file to the User Data Folder all of the defaults will be used anyway as they exist in the copy. If you want more, just add your own. If you want to change any, then edit the copy. If you want to disable any, just delete them.
Keep a backup of your user data files. Use a product like Exam Diff to compare the default and custom files.
Use a product like Exam Diff to compare the default and custom files.
Good to know, thank you.