From: Martin H. <mar...@si...> - 2012-11-20 14:15:56
|
Dear Shriramana, > > Anyway my proposal is to add a slot attribute class .ref as in: > > > > cBase cAttach { ref1=@1 }; > > ... > > What do people think? Would you rush out and use/abuse this feature? If so, what would your use case be? > > Hi Martin. As you can see I cut out all the opcode etc implementation > details which I am not interested in / knowledgeable about. I am only > interested in the functionality. Unfortunately I did not understand > your proposal very well. Could you please give an example of what you > intend to provide and how it would help (which) users? Thanks! imagine in one pass, I want to keep track of a particular glyph so that I can attach to it later: cBase cAttach {ref1 = @1} / _ [lots of complex optional glyphs] _; then when it comes to attachment time in a subsequent pass in the positioning table, I would be able to do: cAttach {attach {to = ref1; with = UM; at = US}}; hmm. the ref1 there may need some refinement syntactically, but you get the idea I hope. If you don't then don't worry too much about it. It's a pretty corner case for most font applications. Yours, Martin |