[Egyptian] Repeating operators

[Nigel Strudwick]

1. Is it possible to have an explanation of this system not intended for specialists? I have tried to read these reports and I do not understand a word. Or were there some diagrams I have missed?

2. I feel Ptolemaic hieroglyphs should be completely omitted from this system as they are a total "niche market”. As I recall in Cambridge, we agreed we would concentrate on the basic set of characters and minimise extensions to it. Do remember that the hieroglyphica extended set was only really developed for the IFAO producing typeset texts of Ptolemaic inscriptions.

Nigel


On 5 Aug 2016, at 00:50, Mark-Jan Nederhof <mn31 at st-andrews.ac.uk> wrote:

> On Thursday 04 Aug 2016 21:06:52 Serge Rosmorduc wrote:
>> On a practical level, due to the size of the gap, it’s also the one where the lack of a proper mechanism hurts most. I guess using 
>> PastedGraphic-4.pdf
>> 
>> instead of 
>> PastedGraphic-5.pdf
>> 
>> does not hurt scholars sensitivity as much as 
>> [...]
> 
> I see what you mean with 4 and 5.
> 
> But have you considered the raised arms (kA) ? Lots of groups can be put within the raised arms. 
> If  a horizontal group, or even a vertical group is being inserted, and one wants to do this using
> vertical grouping + JOIN, there is no guarantee the result will be close to what one expects
> (the group being actually inside the bounding box of the raised arms). For me, it feels
> right to fit the Hm sign inside kA using VERT+JOIN, which might well 'stick out' above.
> But not say the 't', which one expects properly inside, and which moreover is being read 
> phonetically after the kA (if that means anything).
> 
> This is why I think we should reconsider using insert-inside for such cases. Then also the cobra
> could be seen in a new light.
> 
> For the syntax without brackets, see attachment. I'm not sure that for simple machinery this is any easier
> to process than a bounded number of bracket nestings. Note there are 12 binding values hidden in this
> model.
> 
> I have left open the exact notation for operator precedence. I see at least four possibilities, as listed in the
> document.
> 
> Mark-Jan
> <paper.pdf>_______________________________________________
> Egyptian mailing list
> Egyptian at evertype.com
> http://evertype.com/mailman/listinfo/egyptian_evertype.com