Live data from Hacker News

Tō Reo – A Māori Spellchecker

xn--treo-l3a.nz

31–40 of 45 posts

Re: Tō Reo – A Māori Spellchecker

#33

Earlier quoted context omitted.

I was going to disagree with you, because most kiwis have no idea how to write the special o (myself included), so they’d end up typing toreo.nz instead. Which as it turns out, redirects to xn--treo-l3a.nz anyway. Nice!

> kiwis have no idea how to write the special o (myself included) I’m in New Zealand too. I work in MRI and have to type ‘TE’ (echo time) regularly, as well as the Māori word ‘te’. Whatever secret sauce Apple sprinkles into iOS is actually malignant and it takes about 3 edits to type te/TE whenever I try.

Yeah, Apple's autocorrect implementation is shockingly bad. Android is much better in this regard.

Re: Tō Reo – A Māori Spellchecker

#34
post #21

Earlier quoted context omitted.

Seeing the Punycode link is actually a security feature, because it means you aren't tricked into visiting, say, pple-06g.com (apple with a Cyrillic a).

There are conventions around that. https://chromium.googlesource.com/chromium/src/+/main/docs/i... Generally, if all the characters are from one script, then it is decoded. There are lots of exceptions detailed there, but it's harder to make a homoglyph attack work using only characters from one script to impersonate another.

That's not a convention, it's a specification for how Google Chrome does it.

And it's not even a full specification. Several of its 13 steps link to other documents that need to be read to implement the spec fully. Step 12 refers to a list of "dangerous patterns" which appears only to exist in the Chromium source. Step 5 refers vaguely to "any characters used in an unusual way".

It's not OK to say that because Chromium does it, it's some internet standard that random website maintainers should implement.

Re: Tō Reo – A Māori Spellchecker

#35

Earlier quoted context omitted.

> kiwis have no idea how to write the special o (myself included) I’m in New Zealand too. I work in MRI and have to type ‘TE’ (echo time) regularly, as well as the Māori word ‘te’. Whatever secret sauce Apple sprinkles into iOS is actually malignant and it takes about 3 edits to type te/TE whenever I try.

Yeah, Apple's autocorrect implementation is shockingly bad. Android is much better in this regard.

I’m 2y into having an iPhone, generally liking it better but autocorrect alone keeps me on the edge of switching back to android, that’s how bad it is. It’s not even about comparing to android, it’s just that iOS is bad. If I had a bigger phone I’d turn it off entirely but on a mini it’s juuuust useful enough that it makes me want to throw my phone against the wall _less_ than if it was off.

I honestly want to have a coffee chat with the PM in charge of autocorrect at apple, I need to understand what the hell they are thinking!

Re: Tō Reo – A Māori Spellchecker

#36
post #34

Earlier quoted context omitted.

There are conventions around that. https://chromium.googlesource.com/chromium/src/+/main/docs/i... Generally, if all the characters are from one script, then it is decoded. There are lots of exceptions detailed there, but it's harder to make a homoglyph attack work using only characters from one script to impersonate another.

That's not a convention, it's a specification for how Google Chrome does it. And it's not even a full specification. Several of its 13 steps link to other documents that need to be read to implement the spec fully. Step 12 refers to a list of "dangerous patterns" which appears only to exist in the Chromium source. Step 5 refers vaguely to "any characters used in an unusual way". It's not OK to say that because Chromi…

I think you're ignoring the conversation. There is a lot of discussion to be had, and we don't have to say that decoding punycode is a security risk and simply do without. I also said "conventions" specifically to avoid meaning that these are hard-and-fast rules. And Firefox does something pretty similar. https://wiki.mozilla.org/IDN_Display_Algorithm#Algorithm

Re: Tō Reo – A Māori Spellchecker

#37

Earlier quoted context omitted.

Yeah, Apple's autocorrect implementation is shockingly bad. Android is much better in this regard.

I’m 2y into having an iPhone, generally liking it better but autocorrect alone keeps me on the edge of switching back to android, that’s how bad it is. It’s not even about comparing to android, it’s just that iOS is bad. If I had a bigger phone I’d turn it off entirely but on a mini it’s juuuust useful enough that it makes me want to throw my phone against the wall _less_ than if it was off. I honestly want to have a…

I type what I want then add a sacrificial letter at the end, then delete it, then carry on.

- I just tested and this is the way, but it still took me a couple of tries due to it thinking it screwing with the capitalisation.

Re: Tō Reo – A Māori Spellchecker

#40

Is this true that Maaori is crapped by Ænglish spelling? In all other languages long vowel is just two wovels, not some stupid umlaut on top.

Yes, says ChatGPT:

The Māori word "Māori" can be transcribed into the International Phonetic Alphabet (IPA) as:

/ˈmaːɔɾi/

Here’s a breakdown:

  /ˈ/ – indicates primary stress on the first syllable
  /m/ – a voiced bilabial nasal, like the "m" in "man"
  /aː/ – a long open front unrounded vowel, similar to the "a" in "father," but held longer (the macron indicates length)
  /ɔ/ – a mid-open back rounded vowel, like the "o" in "thought"
  /ɾ/ – a tapped or flapped "r," similar to the quick "r" sound in Spanish "pero"
  /i/ – a close front unrounded vowel, like the "ee" in "see"
  This transcription represents the most common pronunciation of the word "Māori."
Post reply on HN