Plugin "Show Mark Preview"


#1

Plugin “Show Mark Preview” is not previewing for mark to mark.
it works only for mark to base.

Please review.


#2

Works for me:

37

Do you have all anchors set? And which glyphs are you previewing?

Edit: I made some changes last night. Make sure you have the latest versions of both app (enable cutting edge versions) and plugin (uninstall and reinstall).


#3

My mistake I didn’t full details

  1. the glyph is “Mark SpacingCombining” I add anchor “bottom”
  2. the glyph is “Mark NonSpacing” I add anchor “_bottom”

The plugin is not previewing. “bottom” has to be an glyph with “letter” Type to preview function


#4

The plug-in only checks if its category is Mark, no matter which subcategory.

Which glyphs are you using? I would like to be able to reproduce the problem, otherwise I cannot fix the issue.


#5

I have added.
“bottom” mark to knJac2
“_bottom” mark to knNuktac2 which is a copy of knNukta


#6

Do they have Unicodes?


#7

yes, still no luck

with three knNukta knNuktac2 knNukta.alt all carrying 0CBC
I get this error at output
image


#8

You can use a Unicode only once. I still cannot reproduce it.

Edit: thanks for the font, just received it in dm; will have a look.


#9

I had a look at the file. The plugin cannot preview mkmk because the marks in question are lacking the necessary anchors. For building and previewing mkmk, the marks need both a _bottom and a bottom anchor for the next mark to connect to.


#10

I am using botnukta to connect. I have adding botnukta n _botnukta in both marks.

still its failing to preview


#11

I checked again. In the file that I received, all the marks only had one anchor each, either _bottom or _botnukta. Adding bottom anchor makes it work as described.

  1. Any particular reason for botnukta instead of bottom? At first glance I see no reason for a separate anchor chain. Also no base letter has botnukta.
  2. You can keep the marks with a width and positive sidebearing values. Makes editing way easier. They will be exported with zero width anyway.

#12
  1. If I use bottom is defined in knJA and _bottom in knJAc2, then I would need to use the same mark to mark approach for all below form and sub.
    Right now it is functional all below form and below sub is functional with space combining.
    I want to use only mark method for nukta.
    Is it a wrong approach?

It works with Harfbuzz, when I output it.

Can we get this to preview with plugin please.

  1. I will do that.

#13

Not sure I get it. What would break if you switched them all to simply bottom/_bottom? You never have both concurrently next to each other in the same glyph anyway, do you?

The preview also works with alternative anchor names. But you also need at least one letter that connects. You could even have:

  • a letter with bottom,
  • a mark with _bottom and a second anchor with a different name,
  • and then another mark with an underscore anchor that connects to that different name.

#14

My problem is the first mark (below form knJAc2) attaching to letter with bottom mark,
all letters have bottom mark, I don’t want that to happen. I want to use spacing for it.

It’s not needed in open Type feature, I suppose.
It’s working in the final font.


#15

It should not connect to anything?

Two ways to deal with that: (a) define it as letter (select it in Font tab, and press cmd-opt-I) or (b) take out the underscore anchor.


#16

no not as a mark to mark to attachment but placed by spacing

(a) it is not an option. I need it as mark in definition, to allow ignoremarks in certain feature.
(b) It is working in final font, when I add both anochors botnukta and _botnukta in both the marks and not bottom anchor in either. I have checked in both Harfbuzz(chrome) and Coretext(Safari).
Show mark preview plugin is not previewing. Its Ok, I can deal without the preview for this one.

Request: Please advise if this is a bad approach by definition. and if you think this is working in final font by chance.


#17

Not sure, but I guess it is OK. I would do a lot of testing, not only in browsers. If it works, it works. If it doesn’t, expect a lot of support mails. :slight_smile:


#18

I am collecting test cases in web pages. I am planning to test in IE, Edge, Chrome, Safari (in mac) is it not sufficient?
do I need to test all my cases in word processors also?


#19

Also, abvm, blwm, are written during exporting by glyphs.
Is it possible see it before exporting?


#20

No, that is not possible because the pos values are interpolated. Export and inspect features.fea in the Temp folder of the respective instance.