Nathan Chou writes:
> Thanks David and Urs for replying.
>
>>> There is a detail I would like to clarify. David suggested allowing \=
>>> to optionally specify the parent context in which a cross-voice
>>> spanner's information is shared (although I am not sure how that would
>>> be done with a k
Urs Liska writes:
> Am 01.07.2016 um 09:28 schrieb Jan-Peter Voigt:
>>> Hm. If this is a limitation required by the implementation then it's
>>> acceptable. But from a user perspective I would be very surprised if an
>>> ID isn't recognized without an explicitly named context around it. Isn't
>>>
Am 01.07.2016 um 09:28 schrieb Jan-Peter Voigt:
>> Hm. If this is a limitation required by the implementation then it's
>> acceptable. But from a user perspective I would be very surprised if an
>> ID isn't recognized without an explicitly named context around it. Isn't
>> that the (one) idea of
Am 01.07.2016 um 09:21 schrieb Urs Liska:
Am 01.07.2016 um 09:01 schrieb Nathan Chou:
Thanks David and Urs for replying.
There is a detail I would like to clarify. David suggested allowing \=
to optionally specify the parent context in which a cross-voice
spanner's information is shared (alt
Am 01.07.2016 um 09:01 schrieb Nathan Chou:
> Thanks David and Urs for replying.
>
>>> There is a detail I would like to clarify. David suggested allowing \=
>>> to optionally specify the parent context in which a cross-voice
>>> spanner's information is shared (although I am not sure how that wo
Thanks David and Urs for replying.
>> There is a detail I would like to clarify. David suggested allowing \=
>> to optionally specify the parent context in which a cross-voice
>> spanner's information is shared (although I am not sure how that would
>> be done with a key-list, since I think the sp
