Template talk:Japanese

A Few Things
I don't believe there was a Japanese template, so this is a very good idea. Firstly, I just changed the link color to the help page, to be consistent with the wiki. This of course leads to the need for a help page to be created for Japanese.

My main point is the name for this template. Considering Nihongo is the Japanese word for the Japanese Language, and that this is an English Wiki, it should probably be called 'Japanese', so that it fits the quality standards on language. Most editors will not be familiar with what a template called Nihongo could mean. I'll move this soon, unless there is a good reason for it being named so. 14:29, 24 December 2009 (UTC)


 * Move is done. 03:41, 25 December 2009 (UTC)

Macrons
There are no guidelines to use them in Romaji, at least I haven't seen any, but alot of people seem to care about Macrons when writing Romaji. I don't like them because they are annoying to type and more importantly, it makes a huge difference whether you write 'oo' or 'ou' when typing japanese. So I was wondering if we are able to program the template in a way that long vowels in Romaji get converted automatically to the corresponding Macrons. I don't know how a template works on a wiki or what programming-language is used to interpret them but if it is possible, this should be a rather easy change. It would help to keep things consistent. Bakeneko 06:57, 8 December 2012 (UTC)
 * It's quite simple to use Google Translate in the meantime if you want to get easy macrons from the Japanese. It might be a bit difficult to implement something into the wiki itself, but I don't know how to write scripts or anything. 17:18, 18 December 2012 (UTC)
 * The general rule is: use macrons for extended vowels, use the expanded form (eg. ou) if it's a vowel change (eg. Koume). The proposed template would probably be a bit complicated to code for the previous reason, and would probably have a considerable performance cost when used in large scale. If you want to quick access to macrons, click the "[Click here to show more...]" link in the edittools box (the box right under the text field when editing an article). 18:40, 18 December 2012 (UTC)
 * When no one was answering at first, I checked the source code myself since I used to be a programmer. Kinda figured that it might be possible using parser functions but is probably too demanding on the sever. I'm now using a sophisticated text editor when doing bigger edits concerning Romaji. Using the Find & Replace feature is doing it for me. Anyways, it doesn't hurt to ask, so thanks for the info. Bakeneko 06:32, 19 December 2012 (UTC)
 * The simplest way I've seen is to just make quick double vowel templates, like "Template:AA", which produce the macron character.KrytenKoro 22:03, 3 May 2013 (UTC)
 * Alternately, you can add them to the character palette (the box below the edit box with easy-insert symbols). Bulbapedia does this for both macron letters, and the vital e-acute of Pokémon. -- Snorlax Monster  13:30, 4 May 2013 (UTC)
 * Macron and kana characters are already in the edit tools. At some point someone decided to have them hidden by default, so you have to click the toggle link at the bottom ("Click here to show more...") to see them. 20:22, 14 May 2013 (UTC)

Fix
Can you guys fix this so that it works like the general Nihongo templates, allowing for notes and lit. parameters?KrytenKoro 22:03, 3 May 2013 (UTC)
 * Did you have a specific format in mind? I don't know what you mean by "general Nihongo templates." 21:17, 9 May 2013 (UTC)
 * This in-depth version or this slimmed-down version.KrytenKoro 17:17, 14 May 2013 (UTC)
 * Well, I guess we can tack on a fifth parameter for literal translations. It'll be a little awkward coming after the "format" parameter instead of before, but short of rearranging the whole template—as well as its thousands of uses—I don't see how else we can do it (then again, I'm not a template expert). I suppose we could make a new template for Nihongo, for situations when literal translations are needed.


 * And then there's always the simpler option of throwing the literal translation in with the normal translation... Except for the problem that, for some reason, double quotes don't work in tooltips, so one would have to use apostrophes for formats 1 and 3... 21:23, 14 May 2013 (UTC)