Correct Manifest Syntax for font named "A%20Charming%20Font%20Expanded.ttf"

%3CLINGO-SUB%20id%3D%22lingo-sub-1669010%22%20slang%3D%22en-US%22%3ECorrect%20Manifest%20Syntax%20for%20font%20named%20%22A%2520Charming%2520Font%2520Expanded.ttf%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1669010%22%20slang%3D%22en-US%22%3E%3CP%3EApplications%20sometimes%20install%20font%20files%20with%20special%20characters%20in%20the%20file%20name%2C%20such%20as%20using%20the%20%2520%20escape%20in%20the%20ACTUAL%20filename%20of%20the%20font%20file%20(instead%20of%20the%20'space'%20equivalent).%26nbsp%3B%20I%20have%20also%20seen%20%25C3%2C%20%2586%2C%20%252c%2C%20and%20%2526%20in%20font%20names%20added%20by%20applications.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20natively%20installed%2C%20the%20font%20installer%20keeps%20the%20%2520%20in%20the%20registry%20string%20and%20the%20font%20works.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUnder%20MSIX%2C%20the%20font%20must%20be%20added%20to%20the%20manifest%20using%20the%20UAP4%20reference%20schema%2C%20however%20the%20%25%20character%20is%20not%20allowed%20in%20the%20relative%20file%20reference.%26nbsp%3B%20Replacing%20such%20escapes%20in%20the%20reference%20(but%20leaving%20the%20captured%20font%20filename%20as%20is)%20causes%20the%20font%20to%20not%20work%20(as%20in%20missing%20without%20error%20and%20a%20different%20font%20replace%20for%20it).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20believe%20that%20the%20schema%20should%20be%20modified%20to%20accept%20all%20filenames%20supported%20natively%20by%20the%20OS.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
MVP

Applications sometimes install font files with special characters in the file name, such as using the %20 escape in the ACTUAL filename of the font file (instead of the 'space' equivalent).  I have also seen %C3, %86, %2c, and %26 in font names added by applications.

 

When natively installed, the font installer keeps the %20 in the registry string and the font works.

 

Under MSIX, the font must be added to the manifest using the UAP4 reference schema, however the % character is not allowed in the relative file reference.  Replacing such escapes in the reference (but leaving the captured font filename as is) causes the font to not work (as in missing without error and a different font replace for it).

 

I believe that the schema should be modified to accept all filenames supported natively by the OS.

0 Replies