There’s an option for each database column to “Show Bigger”, which is said to be useful for Chinese.
I need an option to “Show Smaller”, so I don’t risk long words getting cut off - or alternatively a “don’t use two-column layout in quizzes”. Greenlandic has looooong words.
In this case there’s only one long word, but if both Akunnittarfimmiippoq and Akunnittarfimmiippa, or perhaps Akunnittarfimmiippit or Akunnittarfimmiippugut, had been present, good luck picking the correct answer…
I think this should be something that Memrise could fix with CSS, so that the word wraps to the next line instead of getting cut off.
If you don’t get a reply in a couple of days, feel free to post here again and I might be able to write a userstyle to fix this on your computer, at least.
I’m not sure that css would be able to wrap correctly for Greenlandic though (I did some quick googling, which suggests that it primarily works for English, and on one mozilla page, Greenlandic wasn’t even listed among that languages that are not supported :(). I’d not be too keen on having incorrect hyphenation in a language course…
The hyphenation rules for Greenlandic are reasonable simple though, and I already have a python script that does it, so if there’s any way to specify the hyphenation rules to be used, I’ll be happy to supply them in whatever format is needed :).
I think overflow-wrap is the CSS property that you’d want to use. It should just break words across multiple lines, without introducing hyphens into the words.
I’m still not convinced I’ll love it as a solution, but I guess it could be an ok workaround :). So if you do have the time, I’d appreciate it :).
I still think the solution on Memrise’s part should be to make a smaller font option, which should be easy enough since they already offer a larger font option, but I also know that it isn’t likely to happen in this century ;).
Yeah, memrise should fix this (the system is basically broken for long words), so it wouldn’t be necessary to use userstyles for this :).
I ended up using this code (just because it’s cleaner to limit the css to be applied to memrise.com, even though the risk of collisions is minimal (I’m on firefox, obviously ;))
@-moz-document domain(www.memrise.com) {
.garden-box.multiple_choice ol.choices li .val {
float: none;
overflow-wrap: break-word;
font-size: 80%;
}
}
And here’s how it looks when even the smaller font isn’t enough, so it also applies the word-wrap:
(the word is really aningaasarsissanngilatit (which means something like you will not paid/you will not receive your paycheck))
I do not want a smaller font, but to be able to see the whole word; as strange as might seem, i am not the only one taking the courses i’ve created, therefore a local script is of no use These two paralles columns were a change introduced by the team, without second thoughts “wasted” over longer words/sentences
I would also prefer to see the whole word/get rid of the two columns. BUT I think that’s unlikely to happen - they aren’t going to give up the two columns in general (in most cases it works well), and making a setting for it would be a certain amount of work.
Making an option for a smaller font however, should be a pretty simple thing to do, because there already exists an option for a larger font, which should make it easy to identify all places where it occurs. If such an option is introduced, you’ll still be perfectly able to not use it.
I am also not the only one taking my courses - in fact I raised this issue because a friend was complaining about it. A local user script is never a solution to anything, HOWEVER, the way memrise is currently functioning, it isn’t designed for languages with long words (even though German is a much larger language than Greenlandic), so realistically, I think users interested in such languages will de facto be stuck with a choice between malfunction or userscript.
Let’s not discard a realistic 90% solution just because we can’t have the perfect solution.
You use the code I posted, but leave out the one line about font-size.
In the code you pasted, you also forgot some curly braces at the end - not sure if that was just a copy-paste error, but they need to be present…
.
