[developers] ACE input for non-English Text (and general)

[Woodley Packard]

I believe LUI handles unicode properly on Linux.  There are many things 
wrong with LUI on Mac, I will be the first to agree.

-Woodley

On 08/02/2017 02:58 PM, David Inman wrote:
> Ah, so it looks like the problem is with the LUI display and it was in fact
> unrelated. I am somewhat relieved. Thank you!
>
> Although it does seem like it would be nice for LUI to handle full Unicode.
>
> On Wed, Aug 2, 2017 at 2:52 PM, Woodley Packard <sweaglesw at sweaglesw.org>
> wrote:
>
>> Hi David,
>>
>> Yes, ACE should be able to handle that.  I wonder whether the string you
>> see in the parse chart might be a red herring, i.e. whether there is an
>> unrelated problem in rendering the string back out again via LUI on the
>> Mac.  If you add -vv to the ACE command-line, the first line of the output
>> will show the input sentence, tokenized (and with /(null)? appended to each
>> word, probably).  Can you confirm that this is corrupt?
>>
>> Thanks,
>> Woodley
>>
>>
>> On 08/02/2017 02:41 PM, David Inman wrote:
>>
>>> This is probably directed to Woodley,
>>>
>>> I am trying to run ACE locally on my Mac to parse Nuuchahnulth. However I
>>> am running into the same problem I am currently having on Ubuntu, which is
>>> that it cannot handle my special characters in interactive mode (in Ubuntu
>>> I have the somewhat worse problem of available keyboards). I load my
>>> grammar in interactive mode, and then type in:
>>>
>>> haʔuk
>>>
>>> It does not parse.
>>>
>>> I type :c for the parse chart, and the parse chart believes it has read
>>> in :
>>>
>>> HA îuk
>>>
>>> which of course does not exist in the lexicon.
>>>
>>> I know that ACE is used for Japanese and other languages, and OSX is
>>> Unicode throughout: is there anything I need to do so that I can input my
>>> alphabet?
>>>
>>>