Hello, you have come here looking for the meaning of the word Module talk:ja-usex. In DICTIOUS you will not only get to know all the dictionary meanings for the word Module talk:ja-usex, but we will also tell you about its etymology, its characteristics and you will know how to say Module talk:ja-usex in singular and plural. Everything you need to know about the word Module talk:ja-usex you have here. The definition of the word Module talk:ja-usex will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofModule talk:ja-usex, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.
Removing transliteration for full-width characters in Japanese usexes
Latest comment: 11 years ago1 comment1 person in discussion
Latest comment: 7 years ago9 comments2 people in discussion
This way of allowing translations to be empty does not currently work. If the third parameter is empty, the module assumes the second parameter is translation. (And if you just remove the translation, you end up with a transliteration that's a weird mixture of kanji and romaji, and a "translation" that's kana.) So, script detection should be used to determine what each parameter is. — Eru·tuon08:30, 21 August 2017 (UTC)Reply
If you want to trigger an error for a kanji+kana parameter but no kana parameter, it can be done now. At the moment, it just doesn't try to generate ruby. — Eru·tuon09:14, 21 August 2017 (UTC)Reply
Latest comment: 5 years ago2 comments2 people in discussion
Hello folks --
I just noticed over at Japanese母艦 that the instance there of {{ja-usex}} is outputting a bit oddly.
The Latin text, both romaji and translation, are larger than they used to be. This looks weird.
The romaji is no longer italicized. This makes it harder to visually distinguish the romaji from the translation.
It also looks like there's no longer any whitespace between the romaji and the translation, which also makes it harder to tell the two apart. Padding or margins of a few pixels would help.
I tried manually adding ''double apostrophes'' around the value passed to rom= and previewed, but I found that it did nothing. Examining the rendered markup, I discovered that the romanization is indeed output in italics tags, but it's still rendered upright. Examining the CSS, I found that the entire usex is called "Japanese" -- even the translation -- and the related CSS rule of font-style: normal; means that none of it is allowed to be italics.
@Eirikr: The issue was that {{ja-usex}} was inside the "text" parameter of {{quote-book}} (parameter 7), so it was being tagged as Japanese. It was also incorrectly enclosed in a span tag, which shouldn't be placed around block elements. Fixed. — Eru·tuon22:04, 2 October 2019 (UTC)Reply
iPhone bolding issue
Latest comment: 5 years ago7 comments4 people in discussion
中二病 on Windows 10, Google Chrome中二病 landscape on an iPhone 7+, Firefox中二病 portrait on iPhone 7+, Firefox令色 on Windows 10, Google Chrome令色 desktop on iPhone 7+, Firefox令色 landscape on iPhone 7+, Firefox令色 portrait on iPhone 7+, Firefox
Viewing Wiktionary on an iPhone 7+. While it's fine on my Windows 10 laptop, {{ja-usex}} (and probably other modules/templates) seems to have an issue on iPhones. There is a closing parenthesis on the bolded area. ~ POKéTalker(═◉═) 21:35, 2 May 2020 (UTC)Reply
@Poketalker: I see a misplaced rp tag containing ) in the HTML: <b><ruby>令<rp>(</rp><rt>れい</rt><rp>)</rp></ruby><ruby>色<rp>(</rp><rt>しょく</rt></ruby></b><rp>)</rp> It should be inside the ruby tag. Apparently this causes the rp tag to be shown in the browser in the iPhone 7+, but for whatever reason the browser in Windows 10 ignores the placement of the rp tag and hides it. Maybe User:Huhu9001 can fix the position of the tag; I'm not familiar with Module:ja-ruby, which I guess generates the markup. — Eru·tuon07:44, 3 May 2020 (UTC)Reply
@Poketalker: Apologies. I remember copying the syntax from, or modeling it on, some other page that I cannot recall now; but there's no telling for me now if this was inherited from that page. In general, I am not good with code. Draco argenteus (talk) 19:22, 4 May 2020 (UTC)Reply
Problem when there is Latin-script text right after a wikilink
Latest comment: 2 years ago1 comment1 person in discussion