So a couple hours ago i’d just installed Jitai and it wasnt quite working for me. I was using Chrome and Jitai v3.1.1 as I’d just installed it. I went ahead and sniffed around the code and the WK sources to try and find where did it break or what did I do wrong. As I was investigating I could not find a place where font-family was set to be --japanese-font-family, only --japanese-font-family-hover, when it was hovered. So I tried adding it to the style object just like that, just after line 362:
Interaction with written Japanese content via a computer/tablet/smartphone screen using a browser or application while residing outside of Japan?
Interaction with written Japanese content in the real world (when not looking at a screen) as you go about life living in Japan?
In the second case the number and variety is a lot more. Generally the hardest (for me) is handwritten. Depending on the writer of course and how often I read their content (e.g. my wife’s handwriting is easy (well easier) for me to read but I am used to it).
Having lived here for a long time and thus being surrounded by different fonts and writing every time I turn my head when out and about, I find that font does not matter (unless it is something really odd).
A lot of my practice reading is just reading the things I see around me as I go through the day. I find it very useful (and often times needed as I do need to know what it says). I had discussed with someone else the idea of starting a thread on the forum and I could take random pictures and post them here for folks not living in Japan to practice reading Japanese “in the wild” that is actually what it is in Japan.
From your description it does sound like you seeing the common issue, present since the last site update, that broke most all scripts that run on the lesson and/or review pages. I do not use this particular script, but use a couple of others that have the same issue. Whether they are active/run or not depends on how you got to the lesson/review page. If a script is not running, a page refresh would activate it.
Edit: Installed this user script and it does appear to be something else.
with va´s in all of the languages, but 100% both English and japenese. I’m not quite sure if the ppl i gotta contact can speak Spanish, so id have to teach em www
but like id va in all three, and most people will do enlgish and japenese and i might have to get like actual native Spanish speakers if the japenese peoples accento gets in the way www
Again, in case anyone else reads this thread: Jitai now pretty much works, just using the script as installed from Greasy Fork. However, there is a proviso: it only works after reloading the reviews page - that is, I choose the Reviews tab on the dashboard and the first review comes up in the standard WaniKani font, then I click the browser reload-page button and the reviews start again with Jitai running. This has been working solidly for a couple of weeks now. I don’t know why it behaves like that but it seems completely predictable: go to reviews, no Jitai; reload reviews, Jitai works. As far as I’m concerned, that’s pretty much problem solved. (For now!)
FWIW, if you go directly to wanikani.com/review rather than navigating there via the front page, you don’t have to reload the page. I typically get there by clicking on the WaniKani notifier browser addon, which goes to that page when reviews are available.
I have pushed a new update for Jitai v3 (not v2!). People that have applied the hot-patch must download the script from this link again, everyone else should have it updated automatically.
First of, it includes the fix from @chiaracoetzee, so the script should now work as it did before.
Second, I have included 4 new fonts from AdobeFonts (see below): a font you often see in Japanese shrines and temples, a brush-writing font, a ballpen font, and a more stylized font that somewhat reminds me of Jujutsu Kaisen.
Big shoutout to the people that stepped in and provided a quick hotfix to get the script running @chiaracoetzee@_josh. If anybody is interested in helping co-maintaining the repo, please let me know
New to WaniKani and I would love to try this as my first community-maintained add-on!
I’m using Chrome and have both Jitai v3.2.0 and WaniKani Open Framework v1.2.3 set up and enabled in my Tampermonkey, but on WaniKani site pages it only ever shows that Open Framework is the only active extension. I have tried force restarting my browser pages as well as the whole browser itself after installation of these, to no effect.
Does anyone with more experience here see anything obvious I might be missing? I’ve scanned through the last month of this thread and it seems pretty similar to what @Parusan23 may have been encountering a few weeks back, but it seems to have just resolved naturally for him after a bit. I’m also starting off with a very up-to-date Jitai version. Thank you in advance for any and all suggestions here!
I believe the Jitai userscript works on the reviews page, meaning you have to have reviews to see Jitai. I’m also using the latest Jitai userscript, and I have installed some extra fonts.
From what I could tell at a quick glance, the update that @marciska made didn’t make changes related to the page loading situation.
Though the recent updates to Open Framework (especially if/when all the kinks are sorted out) will make it easier to set up things without needing to worry about how it all works for each and every script. The scripts will still need to change their // @match directive to include any url on the main domain, and update the script logic with the understanding that the script will essentially persist throughout page navigation.
@alexphrodisiac: The issue has resolved itself for me, but with provisos. Firstly, as @maddness says, it only works on reviews, not lessons. Secondly, it is still the case for me that the script does not run if I go to Reviews from my Dashboard page: I have to first go to reviews, then reload that page, and then it works. A few replies up, someone says that if you go to the reviews from the WK email that tells you how many reviews/lessons you have, it works straight away, but I haven’t tried that because I just leave the Dashboard page permanently open in a browser tab. I have not tried this on Chrome, but it’s the same on both Safari and Firefox. Have you tried starting a review session and then reloading the page?
I seem to have made some slight progress in now that my browser seems to recognize the existence of the Jitai extension on review pages once I go to them and manually refresh the page once:
Previously I had only been trying out the extra study instead of reviews when I was finding it to not work.
My new issue now is that the extension doesn’t seem to do anything; the characters continue to only always appear in the default font. How does Jitai know what potential fonts to choose from? I’ve gone through and installed a few of the fonts suggested here already: Jitai (字体): A fairly full-featured font randomizer for WaniKani. · GitHub
Is there an additional manual step anywhere to update or inform my script installation of the fonts it should use?
If the script is running correctly and the only issue is that you aren’t getting the varied font, you should check the script settings via the settings cogwheel in the top left.
Ah yes that was it, now that the settings cogwheel appears (which I didn’t immediately notice), I can now enable all of the fonts that I’d like to potentially see from there. This solves all of my immediate questions regarding setup and usage of this. Thank you all!
Inside the script, there are already pre-defined fonts. The only thing to do is find those fonts (links are provided in the top post, I think, or in the cog wheel as @Inserio has mentioned).
You can edit the Jitai script using your userscript manger of choice (I use Tampermonkey). Just make sure that when adding a new font entry to the “Add fonts” section of the script, you will use the name (case-sensitive) you find on the title bar when you installed the font.
Changed Hotkey: ALT+J now re-rolls random font (before was CTRL+J)
New Hotkey: CTRL+Shift shows default font (alternative to hovering via mouse)
Added info box to notify if no fonts are selected at review start
Many things I shamelessly copied from @Inserio – thanks for your modifications, wouldn’t have understood the Turbo events without your code
One bug I am aware of: After closing the settings panel, the random font is not re-rolled. For some reason, the regex expression of this code results to false:
Hey, no problems with that from me. Just happy to be recognized for the contribution.
Oh, good catch. That was simply my mistake when updating my code from doing all the Turbo stuff myself to using the Open Framework to handle the page management. Open Framework tests only the pathname portion of the URL, so I had updated the regex to match, but clearly forgot to modify that section as well. The easiest and most appropriate change would be to switch document.URL to document.location.pathname.
