[FIXED] From some characters not make composite characters

[LisanAlGaib]

I have a "middledot" a "L" and a "l" character when push the button "make composite" (automatic) nothing happens. I want to make "Lmiddledot" and "lmiddledot" characters with this function.

[Bhikkhu Pesala]

There may be a bug here. Using CompositeData also fails. The definition is present in CompositeData.xml and the period centre glyph exists in my test font. This works in FontCreator 14.

Code: Select all

<Composite><!-- L Middle Dot -->
<GlyphMapping>319</GlyphMapping>
	<Member id="1">
	<GlyphMapping>76</GlyphMapping>
		<UseMetrics>TRUE</UseMetrics>
	</Member>
	<Member id="2">
	<GlyphMapping>183</GlyphMapping>
	</Member>
	<AlignHorizontal>
		<Source>
			<Member>1</Member>
			<Position>Right</Position>
		</Source>
		<Dest>
			<Member>2</Member>
			<Position>Right</Position>
			<Offset>30%</Offset>
		</Dest>
	</AlignHorizontal>
	<AlignVertical>
		<Source>
			<Member>1</Member>
			<Position>Middle</Position>
		</Source>
		<Dest>
			<Member>2</Member>
			<Position>Middle</Position>
		</Dest>
	</AlignVertical>
	</Composite>
<Composite><!-- l middle dot -->
<GlyphMapping>320</GlyphMapping>
<InheritLSB>108</InheritLSB>
<RSB>0</RSB>
	<Member Id="1">
	<GlyphMapping>108</GlyphMapping>
	</Member>
	<Member Id="2">
	<GlyphMapping>183</GlyphMapping>
	</Member>
	<AlignHorizontal>
		<Source>
			<Member>1</Member>
			<Position>Right</Position>
		</Source>
		<Dest>
			<Member>2</Member>
			<Position>Left</Position>
			<Offset>-100%</Offset>
		</Dest>
	</AlignHorizontal>
	<AlignVertical>
		<Source>
			<Member>1</Member>
			<Position>Middle</Position>
		</Source>
		<Dest>
			<Member>2</Member>
			<Position>Middle</Position>
		</Dest>
	</AlignVertical>
	</Composite>

[Erwin Denissen]

Confirmed. This bug will be fixed with the next upcoming release.

[Erwin Denissen]

We have just released an update which fixes this bug.

[LisanAlGaib]

Sorry, but the problem is not fixed. Something more bad happened after the update. I send you a picture.

[Erwin Denissen]

Can you please send us the font project file, so we can look into this?

[LisanAlGaib]

Of course. I will send you private.

[LisanAlGaib]

I can't attach file in private message?

[Erwin Denissen]

The auto complete composites feature will use Composite Data and for dieresiscomb it takes dotaccentmod and if that one is not available, it uses periodcentered.

Some things to reconsider:

1. Should it override an existing glyph outline, or should it assume the outline is just fine?
2. Should it reposition existing anchors?
3. If it uses dotaccentmod as a composite, should it position it correctly, e.g. move it above x-height and set aw to zero?

Your feedback is greatly appreciated!

[LisanAlGaib]

In my file, every existing character is perfect, but some compose character not existing after pressing the button make composite automatic.
After the update, the software has made more composite characters but overrides every existing composite automatic. Automatic override is a very bad solution. In every case, the user should have to choose that the software can override or keep the existing glyph.

In my file, every character with diacritics or accents made correctly with the older software version (before the latest), but some composite characters are not made, but have to because the part of these composite are made. For example if I have "L" and "l" and "middledot" (UNICODE Character 00B7) it should have created "Lmiddledot" and "lmiddledot". I haven't created anchors, the software has created anchors when I copied my character from Affinity Designer because I don't know why anchor correctly position and I don't know when repositioned an anchor and saved the file the new anchor position coordinates not saved. There has to be a way in this software to save new anchor positions.

I want all accents or diactritics to be positioned perfectly as composite. Some is perfect in the sent file. The others will be perfect in the next of this software.

[Bhikkhu Pesala]

You can apply Complete Composites (Auto) to selected glyphs if you wish to avoid overriding existing composites with new versions.

Perfection is impossible because every font design is unique. The feature may be nearly perfect on standard Serif or Sans Serif fonts, but script fonts will often need anchors to be adjusted manually to make composites look correct.

The CompleteComposites.xml can be modified by the user to tweak manual composition to suit the user's preferences, but the Anchor-based composition is more reliable in most cases.

The periodcentred glyph (183 decimal) is found much more frequently in fonts than is the modifier dotcentred glyph accent (729 decimal), so I chose to use that (back in the days before Anchor-based positioning). Since CompositeData.xml positions the accent, the only thing that matters about the glyph is its shape and size.

[Erwin Denissen]

We intend to make some changes to the auto complete composites feature.

For all selected glyphs:
- If available, perform Anchor Based Reposition
- Otherwise, if available, perform Composite Data, but only if the glyph outline is empty. In this case all anchors will be removed

All affected glyphs will remain selected.

[Erwin Denissen]

We have just released an update with the proposed changes.

Let us know if this works for you.

[Bhikkhu Pesala]

I noticed that L middledot only composes with CompleteComposites, not with Auto or Anchor-based composition.

Another small point, the button on the download page default to downloading the 32-bit version, but you recommend installing the 64-bit version of the user's OS supports it.

Wouldn't it make more sense for the button to download the 64-bit version by default, and the message says: “Please download the 32-bit version if your OS does not support 64-bit applications.”

[Erwin Denissen]

I noticed that L middledot only composes with CompleteComposites, not with Auto or Anchor-based composition.

That is correct. I am not sure if it is useful to support anchors.

Another small point, the button on the download page default to downloading the 32-bit version, but you recommend installing the 64-bit version of the user's OS supports it.

Wouldn't it make more sense for the button to download the 64-bit version by default, and the message says: “Please download the 32-bit version if your OS does not support 64-bit applications.”

On my system Firefox shows 64-bit as default, but for some reason it does show 32-bit with Edge. What web browser do you use?