Use of Hawaiian diacriticals

Thought I’d start this thread to gather ideas on how to handle Hawaiian place names in WME.
Of course, at issue is the use of the 'okina only (represented in WME by an apostrophe), since the platform doesn’t support the kahako.

My opinion is that in general, we should be guided by signage, and since most major signs don’t include them, neither should Waze, to avoid unnecessary confusion. Of course, many newer subdivision do use street signs with diacriticals, and there including the 'okina seems appropriate.

Also, in Places, where it’s part of the proper name (according to its official website), we should follow that guidance.

I haven’t noticed an effect on TTS – has anyone?

I’ve had an 'okina (apostrophe) on my street name since day 1, and TTS just ignores it. But as far as matching signage, I’m all for it.

What happens when one side of the street the sign has diacriticals and the other side doesn’t?

Criterion for split road?

Nah. Yeah. Good question.

I think we need to address this in earnest. The new validator script flags the apostrophe ’ , but not back quote, `. I suppose we need to decide wither we are using diacriticals or not. If so, do we need to use back quote, or ask that validator not flag apostrophe.

I wouldn’t mind it but we gotta add it to the wiki to make sure guest and new editors don’t remove it. I think we can get letters with kahako by copying and pasting the character in. What about city names too if we’re making it ʻŌlelo Hawaiʻi compliant lol. I’ll test kahako if I can find a road that has it.

Sent from my SM-N910P using Tapatalk

That’s interesting. When we do an okina on Macs for work, that’s made with Alt and the right bracket. Like this: ‘

We need to experiment whether THIS has an effect on Validator or TTS, right?

And I’m really not sure now about the kahako. Type this into the WME search box, and Lihue appears with both the okina and kahako:

Nawiliwili Rd & Kukui Grove St, Līhuʻe, HI 96766

Just Google kahako and copy and paste the char out of it. That’s different from the accent above the tilde ~. On Android I have these options ’ ‘ ' when I long press apostrophe. I copied the Olelo Hawaii from a website and the ‘okina uses ‘ not ' or. Google keyboard also has the kahako’d chars but Tapatalk errors out when I type it lol

Sent from my SM-N910P using Tapatalk

¡™£¢∞§¶•ªº–≠œ∑´®†¥¨ˆøπ“‘«åß∂ƒ©˙∆˚¬…æΩ≈ç√∫˜µ≤≥÷

you just opened a whole new world for me. I did not know about alt-key combinations.

Yes. Time for selective edits and TTS tests. Going to look around my neighborhood for some of the newer signs that may have diacriticals.

Okay. I can unequivocally state that Po’olau produces “Pool-lau”. That’s with an apostrophe. I’ll change it to the alt-key ‘ and wait.

BUT, will searches require the correct punctuation to return the correct road? In other words, does the end user have to put in that correct diacritical to get the street they are looking for?

A critical consideration (no pun intended). I would imagine that the plain-vanilla place names, minus the diacriticals, would need to be there as an alt.

And, BTW, that’s Alt-right bracket. Still struggling to find a way to enter the kahako via the keyboard.

Search for the Unicode alt+xxxx (numbers). A another cheat way is to use insert symbol in Microsoft word. Would be hilarious if Jane pronounced Hawaiian words correctly with the diacriticals

Sent from my SM-N910P using Tapatalk

Ā

Sent from my SM-N910P using Tapatalk

Ēīōū

Sent from my SM-N910P using Tapatalk

G‘ō Āñdrōīd

Sent from my SM-N910P using Tapatalk

Yes. That’s how I got the ‘. I just typed in “alt-key” as a generic alt+{key}

Has there been any feedback on tts while adding diacriticals? I haven’t run into any roads with them on yet to see.

Sent from my SM-N910P using Tapatalk

Doing some tests on diacritials
using the official glyph for okina (UnicodeU+02BB) on Makapu’u Ave causes the Jane TTS in WME to say Makapoo-you but using the apostrophe makes it say it correctly with a glottal stop between the U
but I don’t know if it applies to in app
and it throws a highlight from validator for incorrectly abbreviated street name