User talk:Yoko Harukaze

Welcome
Hi, welcome to ! Thanks for your edit to the File:Tiny-bird-falls.png page.

Please leave a message on my talk page if I can help with anything! Kozakuu (talk) 19:17, June 9, 2013 (UTC)

RE:New Templates
Thanks for contributing to the Quote templates and others you've designed for this wiki. :) I will try to make those templates tie in with the color scheme of the wiki, so is it okay to change things a bit, just enough to implement style changes to the templates? heraldofmeridian♣ 13:36, June 25, 2013 (UTC)


 * Of course it's ok. By the way, I think it would be useful if furigana would be shown only when kanji is hovered/clicked/something for it to be hidden when it's not necessary. I recommend either css for hover or active (so "as long as the mouse button is held down"), mw-collapsible or Checkbox for clicked. Depends on what you think would be the best solution. — Yoko Harukaze はなしある？ 05:59, June 26, 2013 (UTC)

I think the easiest method would just be using Ruby tags for the furigana, although it requires people to install a Ruby support addon to view those text properly or otherwise they would be rendered as characters after the kanji like this: 友情(ゆうじょう). Javascript may help too, but that is a weakness of mine. heraldofmeridian♣ 14:02, June 26, 2013 (UTC)


 * It's very simple, it would work pretty much like in Template:Quote. But Ruby is also a good idea. The only problem is that not all browsers can read it. I wonder if we should make some alternative (an mw-collapsible block, for example) for others or not. That do you think? — Yoko Harukaze はなしある？ 18:32, June 26, 2013 (UTC)
 * Ruby may be a bad idea due to it's accessibility, so we need to implement something that is supported by default in most browsers without slowing down load times. But I don't have any idea about which option to go, so I'll just have to give that decision to you, sorry. heraldofmeridian♣ 11:18, June 29, 2013 (UTC)
 * Not a problem at all.

 .kanji+rp,.kanji+rp+rt,.kanji+rp+rt+rp { font-size:0px !important; line-height:0px; vertical-align:middle; margin:0em; transition:0.6s; } .kanji:hover+rp,.kanji:hover+rp+rt,.kanji:hover+rp+rt+rp { font-size:60% !important; transition:0.5s 0.2s; }
 * When you copy this style to the Common.css it should make furigana visible only when kanji is hovered.
 * By the way... I think the following style would be usefull too:
 * .mw-collapsible-toggle { margin-left:-100% !important; }

It makes mw-collapsible similar to collapsible in its non-jumping any contents when clicked (even when contents are aligned to center or right). — Yoko Harukaze はなしある？ 14:18, June 29, 2013 (UTC)

Problems with Kanji Template
Hey, there seems to be a problem with the kanji template on my part. I'm seeing the characters (both the ruby and kanji) stacked on one another and I don't know what's wrong with it. heraldofmeridian♣ 13:29, July 3, 2013 (UTC)
 * Well, I guess it's due to problems with reading Common.css in the Wikia skin, so the first thing is adding a style to Wikia.css. I don't have the same problem on any of my browsers but I guess this style should help (copied both to Common.css and Wikia.css, instead of the previous one):

 .kanji+rp,.kanji+rp+rt,.kanji+rp+rt+rp { font-size: 0px !important; line-height: 0px; vertical-align: middle; margin: 0em; transition: 0.6s; } .kanji:hover+rp,.kanji:hover+rp+rt,.kanji:hover+rp+rt+rp { font-size: 60% !important; line-height: normal; vertical-align: bottom; transition: 0.5s 0.2s; } .mw-collapsible-toggle:not(.mw-collapsible-toggle-inline) { margin-left:-100% !important; }
 * If it won't work, I'll try changing line-height or padding but I hope this would be enough. — Yoko Harukaze はなしある？ 10:18, July 4, 2013 (UTC)

Is it working now? In your browser, I mean? — Yoko Harukaze はなしある？ 16:41, July 4, 2013 (UTC)


 * [[File:Error-filled_snippet.jpg]] Not really. :/ By the way, isn't the template with your name on it on the Tiny Bird & the Colors article too much? Just speaking out my mind. heraldofmeridian♣ 02:56, July 5, 2013 (UTC)


 * Talkings about the "care box"... I don't really know if it is or isn't on this wiki as I saw something like that a few times on other wikis. Do you think it would be better if it wouldn't be there or if I put it after the actual content instead of before it?
 * And about your problem... Can you tell me what browser do you use? It would be much easier if I could use the same one when trying to solve this problem. For now, try this:

.kanji-box { ruby-overhang:auto; ruby-align:distribute-space; ruby-position:before; }

.kanji-box rp,.kanji-box rt { font-size: 0px !important; line-height: 0px; margin: 0em; padding: 0em; transition: 0.6s; } .kanji-box:hover rp,.kanji-box:hover rt { font-size: 60% !important; line-height: 0.9em; transition: 0.5s 0.2s; }

.kanji-box:hover rp:first-child { padding-left:0.1em } .kanji-box:hover rp:last-child { padding-right:0.3em }
 * I hope it'll help. — Yoko Harukaze はなしある？ 08:18, July 5, 2013 (UTC)

I'm using the latest version of Firefox. I don't have the Ruby plugin installed. And nope, the last attempt for a remedy didn't work. heraldofmeridian♣ 14:30, July 5, 2013 (UTC)


 * You actually haven't tried it so we still don't know if it works. And you haven't tried because you added the style instead of replacing the old version with the new one (like you did before and like I expected you to do), so I'm not surprised it's not working. It means the whole section should look like that:

/* Ruby text CSS */ .kanji-box { ruby-overhang:auto; ruby-align:distribute-space; ruby-position:before; }

.kanji-box rp,.kanji-box rt { font-size: 0px !important; line-height: 0px; margin: 0em; padding: 0em; transition: 0.6s; } .kanji-box:hover rp,.kanji-box:hover rt { font-size: 60% !important; line-height: 0.9em; transition: 0.5s 0.2s; }

.kanji-box:hover rp:first-child { padding-left:0.1em } .kanji-box:hover rp:last-child { padding-right:0.3em }

/* Collapsibility CSS. */ .mw-collapsible-toggle:not(.mw-collapsible-toggle-inline) { margin-left:-100% !important; }
 * I can see you answered about three minutes after changing the Common.css & Wikia.css. To make sure, you should wait about ten minutes if you don't see any changes. If you do, inform me about them.
 * And the browser... That's interesting as I tried it on Firefox too. No Ruby, of course, but works ok. For now, try "the last attempt for a remedy". ;) — Yoko Harukaze はなしある？ 15:18, July 5, 2013 (UTC
 * It's not working, even though I removed all of the newer code, waited one hour, added the new snippet of code and waited some more. It has been hours since the changes has been done to the CSS files, but there are no improvements with the problem. (Complex code like this is one of my biggest weaknesses as a Wikia contributor.) heraldofmeridian♣ 09:58, July 6, 2013 (UTC)
 * I see... Well, I'm afraid it's a defect in your Firefox then. It looks like your browser tried to read Ruby but failed instead of not reading it at all (so writing just: 花 (はな) ). All Ruby's parameters, including the default ones, seem to be correct.
 * I think I should advise you just changing the browser or installing some plug-in... But can you send me some pictures of the effect when hovering? And if other ruby works the same? To tell you the true, I'm just curious as I guess it won't work either way. — Yoko Harukaze はなしある？ 10:54, July 6, 2013 (UTC)

I checked out the template using Chrome. It looks fun, but may be annoying when one ends up nudging those lines one kanji at a time. In my Firefox, the hover effect (the gradual font growth/shrinkage) doesn't work. The top text in the "other ruby" works. heraldofmeridian♣ 12:15, July 6, 2013 (UTC)


 * I've also noticed it can be irritating to check every kanji separately. I think it's a good time to think about a different solution, other than hovered Ruby, I mean.
 * As far as I remember, I've already mentioned the mw-collapsible solution, haven't I? It could be a bar in the bottom of the screen which would have a few options like, let's say: "no furigana", "no-ruby furigana", "ruby furigana". All the kanji on the page would be affected when using this option, so it would be easier if one wants none or all the furigana. And if somebody would like to see furigana when hovering (one knows kanji a little, but not all of them), there could be an option "hovered only".
 * The whole system can be made using mw-collapsible and css (or maybe some simple javascript, depending on the exact options) and I think it would be the best choice as everybody could use the setup they like. And I could make a list of styles for users' common.css/monobook.css/wikia.css for all the options so that they can have one global setup on all the pages.
 * What do you think? — Yoko Harukaze はなしある？ 14:40, July 6, 2013 (UTC)
 * What was the non-hover ruby format? Actually, I prefer that. Much simpler too. heraldofmeridian♣ 05:45, July 7, 2013 (UTC)
 * The non-hover Ruby have two disadvantages:
 * If one's browser reads Ruby, it makes lines with kanji wider which makes the text look much worse.
 * If one's browser doesn't read Ruby, it's shown as kanji with furigana after it which can disturb in some texts when you know most of used kanji, like here:
 * 小鳥遊 (たかなし) さんは 全然 (ぜんぜん) 小鳥 (ことり) じゃない.
 * 私 (わたし) は 色 (いろ) んな 色 (いろ) 見 (み) る 為 (ため) に 飛 (と) ぶ.
 * And about simplicity... The simplest is using "title", like this:
 * 私 は色 んな<span class="kanji" style="border-bottom: 1px solid  #202020; margin:1px;" title="いろ">色 <span class="kanji" style="border-bottom: 1px solid  #202020; margin:1px;" title="み">見 る<span class="kanji" style="border-bottom: 1px solid  #202020; margin:1px;" title="ため">為 に<span class="kanji" style="border-bottom: 1px solid  #202020; margin:1px;" title="と">飛 ぶ.
 * Maybe it's also a bit irritating if one doesn't know kanji at all, but it doesn't change lines' height, doesn't take extra space and all browsers can read it. <span style="font-size:110%; font-family:Comic Sans MS; font-weight: bold; text-shadow: 1px 1px 1px #d9a300">— Yoko Harukaze はなしある？ 09:02, July 7, 2013 (UTC)
 * What's it gonna be, then? @_@ Each of the options have a rather annoying disadvantage. I'd choose using titles since it manipulates character layouts the least. The one I'm using for Japanese characters is Firefox's Rikaichan, though. The non-hover Ruby is a decent alternative. heraldofmeridian♣ 12:12, July 7, 2013 (UTC)
 * Here we have the advantages and disadvantages of the solutions we mentioned...


 * As you pointed, all of them have both good and bad sides. Which do we choose? <span style="font-size:110%; font-family:Comic Sans MS; font-weight: bold; text-shadow: 1px 1px 1px #d9a300">— Yoko Harukaze はなしある？ 16:51, July 7, 2013 (UTC)
 * I'm going for the Setup Bar, but I'll leave the JavaScript stuff to you. :P Have you shown me what that looks like? heraldofmeridian♣ 00:59, July 8, 2013 (UTC)
 * I haven't. How it's looks like isn't that important as it can be changed easily. I'm just in the middle of tests. I'll give you a sample when I'm finished. <span style="font-size:110%; font-family:Comic Sans MS; font-weight: bold; text-shadow: 1px 1px 1px #d9a300">— Yoko Harukaze はなしある？ 16:45, July 8, 2013 (UTC)
 * Ok, I've got it. If you copy my wikia.css and wikia.js and look at my test page, you should see a sample of the Setup Bar conception. <span style="font-size:110%; font-family:Comic Sans MS; font-weight: bold; text-shadow: 1px 1px 1px #d9a300">— Yoko Harukaze はなしある？ 18:33, July 9, 2013 (UTC)