Gilgamesh: Enough expository banter!
This talk page is used for discussing improvements to the page "Luxerion". It is not the place for general discussion or sharing stories about the topic of this article.
Take a good look. Isn't it beautiful?
FF5Crystal.gif Behold! This article has been chosen as the Featured Article of February 2015!
Even so, if you wish to improve the article, do not hesitate! You can also nominate your favorite articles to be featured here!

Can anyone get the two kanji letters before the "ルクセリオ" part from here?—Kaimi (999,999 CP/5 TP) 15:19, January 12, 2013 (UTC)

This: 光都? 15:31, January 12, 2013 (UTC)
Thank you, that is indeed correct. I'd got them myself, but I have never learnt Japanese and I can only operate on katakana and thus I need to rely on others when I need.—Kaimi (999,999 CP/5 TP) 16:03, January 12, 2013 (UTC)
Google Translate+guessing and List of kanji by stroke count works wonders. I found the first on there, and the second by translating "city" to Japanese on Google Translate (as I took a guess at what the kanji may be). :) 16:20, January 12, 2013 (UTC)
"Good one, Fang!" That "list of kanji by stroke count" is a bit overwhelming as I have no freaking idea how does stroke counting is done there.—Kaimi (999,999 CP/5 TP) 16:37, January 12, 2013 (UTC)

I would never use Google Translate for wiki purposes. The kanji does indeed translate to light city, but it is not hikari-to. It would more correctly be kouto. Hikari is the way the kanji is pronounced when it is used on its own. Ie, if the word was "光の都" or "city of light", then it would be pronounced "hikari no to". When combined with other kanji to form a new word, it is pronounced other ways, and in this case would most likely use the on reading, which is "kou". Although there's no way to be 100% sure unless we see how they want to pronounce it. For example, 光都 is also a family name in Japan, and in that usage it is pronounced "mito". As you can see, this stuff gets complicated and even Japanese people can need help clarifying pronunciation of new words like this. In this case, I suggest no trying to romaji-fy it at all. Just leave it Lua error in package.lua at line 80: module 'Dev:Arguments' not found..

Another example of google translates foibles I saw elsewhere on the wiki is on the Final Fantasy Dimensions enemies talk page. On there someone said that the katakana for Diabolos somehow meant "advocate" in Japanese, due to google translate saying so. This is, of course, completely silly and nonsensical. I still have no idea where google pulled such a random translation from. Perhaps it's somehow getting the latin term for devil's advocate, "advocatus diaboli" mixed up and fused? I dunno, but there's a lesson here. Don't mess with Japanese unless you are reasonably sure of what you're doing. Also, use this site instead of google if you must: I find it much easier for simple romaji>kana>kanji converting purposes when typing things, and it is quite accurate in its word meanings. You can't translate bodies of text, just single words, but bodies of text should never be auto-translated anyways, especially in a language as context-heavy as Japanese. Espritduo (talk) 17:05, January 12, 2013 (UTC)

No, I insert English into Google translate to try and return the Kanji I'm looking for. I also sometimes use this website but I don't know stroke order so it rarely returns what I want. 17:21, January 12, 2013 (UTC)
Ah, well the denshi jisho (the site I linked) is excellent for that too. You can look for kanji by radical (the simpler shapes that make up the kanji) so you don't need to know stroke order or anything ( As long as you can break apart a kanji into its smaller parts, you can find what you're looking for. Knowing how to count strokes does help here, but you can get by without it easily enough, I think. Espritduo (talk) 17:32, January 12, 2013 (UTC)

Quote[edit source]

Lua error in package.lua at line 80: module 'Dev:Arguments' not found.

Lua error in package.lua at line 80: module 'Dev:Arguments' not found. Lua error in package.lua at line 80: module 'Dev:Arguments' not found. Lua error in package.lua at line 80: module 'Dev:Arguments' not found.

Quests[edit source]

Since the quests are going to make the page suuuuuuper long (since we are no longer using tabbers *sob*) can't we just move them to a page called like Luxerion/Quests (like the D's Journal pages if you get what I mean) and also do the same for the other location pages Wildlands, Dead Dunes, and Yusnaan. Just a suggestion.--Xion V. (talk) 21:28, October 10, 2016 (UTC)

I think that's a good idea. There might be other articles that could be divided as well. There are quite many links to the quests here though.Keltainentoukokuu (talk) 23:10, October 10, 2016 (UTC)

It may take a bit of time but I could probably do this myself, making the page and then changing all the links for all the areas though not at the same time of course. If this is alright to do I can actually get started either later today or tomorrow and maybe finish at least the Luxerion set of quests over the next few days.--Xion V. (talk) 18:01, October 11, 2016 (UTC)

Personally, I'd go with "List of Lightning Returns: Final Fantasy XIII quests/<subpage name>" unless "<Location name>/Quests" is what our policies say should be the way to name it.—Kaimi (999,999 CP/5 TP) ∙ 18:51, October 11, 2016 (UTC)

I'm not sure what the policy is really, I went with Luxerion/Quests since it would not only be easier to edit but easier to search for (from a normal non-editor readers point of view) since the name is not only shorter but straight to the point, Quests in Luxerion.--Xion V. (talk) 20:08, October 11, 2016 (UTC)

Quests belong to location I think Location/Quests is good. The list of quest page should maybe link to every individual quest in the location subpages, as well. Nice if you can be bothered to do this!Keltainentoukokuu (talk) 20:34, October 11, 2016 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.