To whom it concerns
Has there been a recent functionality change I’ve noticed since last week that the old method of typing “tt” to give the small version of tsu seems to no longer work.
This is causing issues using the tool as now it’s impossible to type in certain words correctly.
I’ve not made any changes to my browser or set up so wondering whats going on.
I remembered a thread from the other day about this that may help:
If I remember right, for example to get がっこう
gattkou no longer works,
gakkou should still work. (and is more in line with what input methods generally expect)
(gaxtsukou presumably works too but isn’t recommended)
Were… were people seriously typing a double T on its own to get っ? Why? Where did people learn this?
In most IMEs, “gattkou” is gonna get you がｔｔこう. Small っ doubles the next consonant. To type one in a word… just double the next consonant.
Yeah I had no idea this was a thing until these threads. I spent half the other one trying to figure out what exactly the issue was.
Yes, there have been a bunch of people complaining about it, which makes me think there are even more who didn’t come here to complain. I’m not sure where they would learn it either.
Maybe it’s a matter of uncertainty about what っ actually is in Japanese that have made people do this? 
also realised during a typo-laden session that l works the same way, so for がっこう you can type galtsukou. idk why you would, like, but you can 
Indeed, though not on WaniKani, which treats L as being the same as R.
Unless they changed that. It’s been a while since I checked…
I didnt even know double tapping T would become つ 
could’ve sworn that’s where i first noticed it, tho could equally have been kamesame currently got no reviews/lessons, i’ll check again later 
update: l and r are definitely differentiated now, i typed li and got ぃ
Now that I think about it, I’m pretty sure the teacher in the single Japanese course I’ve ever taken wrote “tt” when she romanized っ, even in words like がっこう. I don’t think I’ve ever run into it anywhere else except for this thread.
I just noticed this as well. It breaks words like しゅっけつ for me. I cant get the small tsu after the small yu. 
Are you typing “shukketsu” ?
Hmmm. I don’t think I am. I have been typing syuttketsu instead of syukketsu. It’s one extra character but my brain says says “t for tsu”. I’ll have to try that. 
Edit: Tried both ways on Google keyboard and both work but now on WaniKani only the syukketsu way works.
shukketsu (or syukketsu) is more in line with how it’s pronounced, anyhow! And more recognized by IMEs.
It’s the advisable way to go.
Interestingly, I was going to link the Wanikani knowledge article about this, How do I type…? | WaniKani Knowledge
… but it seems like by coincidence it illustrates the “double the following consonant” point only with つ, which seems like it might be one way the misunderstanding might arise for folks who ended up in the “double t” camp.
(incidentally as a bonus tip, “x” works to make following characters smaller, so “xtu” works in situations where for some reason you definitely don’t want to just double the following consonant. This is most useful for loan words with unusual combos like ティ, I’m not recommending it for typing っ normally, to be clear)
Maybe they changed that at the same time they changed tt=っ…
To be fair, the “double the next consonant” method doesn’t work for ending phrases with っ which you’ll see pretty often in manga and other informal contexts, but “xtu” works there. I wonder how people originally learned to type tt… i’d never heard about this method but i’m curious what sources advise this
@rodan made a pretty good point above that every example the WaniKani “how to type” guide gives for typing っ is with a っ that’s duplicating the T in a regular-sized つ.
Interesting theory. I wonder if that’s where I came up with it? I’m going to try and see if I can’t retrain myself to use the other method.
It just makes me wonder why they would make this change if it wasn’t doing any harm and the fact that other IMEs like Google still accept it as valid.
It looks like it doesn’t work with microsoft ime, so they probably are trying to stick to the way accepted by a larger number of IMEs.