d.d.d.:

@anonymous
Is that a hagwon? I thought that's where No-Rae works lol

That's what the sign says: 학원.

https://en.wikipedia.org/wiki/Hagwon

Actually, I'm a bit unclear about the detail (though trivial in the story) of whether No-rae did go out with her coworkers or did not go out with them.

In taeyeonlikesgirls's original phrase, it sounds like her coworkers asked her to go with them, but she turned them down. But in your typeset, it sounds like she did go with them.

last edited at Jun 8, 2015 8:57AM

@ d.d.d.

Again, good job!

Also, it's now like a game to find all the... "Easter eggs" that you've put in your typesets, lawl.
I've spotted 3 so far. :3 What a coincidence that the hospital, the hagwon (학원) and the bus line all share the same name!

BTW, I noticed that you fixed up the English a little bit. I really appreciate the effort!

last edited at Jun 8, 2015 2:21AM

Chapter 38 translation... actually, translation and rough typeset by taeyeonlikesgirls:
http://taeyeonlikesgirls.tumblr.com/post/120992447089/fluttering-feelings-38th-ch-trans

last edited at Jun 7, 2015 11:45PM

kith:

This is random....but the nurse is exactly like the store clerk from Their Story. Dat indulgent yuri smile XD

Lawl.

From why-because-idk:

http://why-because-idk.tumblr.com/post/120975292472/fluttering-feelings-fandom-be-like

I have updated the webpage with instructions for the Overtooning (overlay) method for reading the FF translated typeset directly on Comico. I had previously talked about this webpage in this post.

I had actually wanted to get this done in time for last week's chapter but didn't have the time to finish it, unfortunately.

Here's the page:
bit.do/ffovertoon

Changes:
* Did a few minor updates of how to set up the bookmarklet.
* Added a troubleshooting section.
* Added a new section detailing how Comico works. This includes a visual guide showing how to sign up and how to unlock chapters, complete with screenshots.

Feel free to let me know what you think. (Good, bad, easy/hard to follow, etc.)

last edited at Jun 7, 2015 4:13AM

Some news

taeyeonlikesgirls is going to be doing a translation of chapter 38 and will post it on her Tumblr blog.

http://taeyeonlikesgirls.tumblr.com/tagged/fluttering-feelings

last edited at Jun 6, 2015 7:09PM

Fan art by rainfallsuniverse:

I am so fangirling over this cute couple, it’s my first time to draw the two of them. Get married alreeaadyy. LOL They look like Asami and Korra BTW.

Source:
http://rainfallsuniverse.tumblr.com/post/120816379154/i-am-so-fangirling-over-this-cute-couple-its-my
http://41.media.tumblr.com/699d7df1c7bd7e66d3b3c2a3ea7f4989/tumblr_npi0d9pcpw1utwff2o1_1280.jpg

 
 
The standalone portraits:

 
No-rae (previously posted):

I’ve drawn soft looking No-rae with her easy to trust brown eyes. Love this baby.

Source:
http://rainfallsuniverse.tumblr.com/post/120685783904/ive-drawn-soft-looking-no-rae-with-her-easy-to
http://41.media.tumblr.com/958720f90428865293a76a0a0f7044dc/tumblr_npf25lgYSz1utwff2o1_1280.jpg

 
Seol-a:

ORIGINAL FULL SIZE: http://s30.postimg.org/9dv48vmtd/tumblr_nphvt9b9_T61utwff2o1_1280.jpg

And of course Seol-a too, the raven-haired beauty.

Source:
http://rainfallsuniverse.tumblr.com/post/120810563159/and-of-course-seol-a-too-the-raven-haired-beauty
http://40.media.tumblr.com/7dfda073220f1624c0d138abe882be97/tumblr_nphvt9b9T61utwff2o1_1280.jpg

 
'Tis a good day to be a FF fan. :3

last edited at Aug 18, 2015 3:47AM

Jaismot:

@anonymous

You are truly something, I think you post this just a few minutes after I create my tumblr post. O.O

I'm not actually a human being.
I'm in fact an automated web crawler. Like Google's.
... Err... except only for FF fan art. Or something.

And actually, for some reason, I totally forgot to include the source URL to your blog post in my post above. Sorry about that. Edited my post to include it. I usually always make sure to give proper credit to the original author/artist and link back to their original page.

Jaismot:

Anyway, thanks anon', I think you gave me the little push I needed to publish these somewhere on a blog.

Yeah, honestly, I'm really glad you put your work on your own site.

As mentioned before, having your work only here would really not do it enough justice. Also, site and forum data can be lost. (Has happened before to this very forum, from what I understand.) So if you only posted it here and only here, then a week/month/whatever later, the forum or site crashes with all posts lost, your work would essentially "disappear forever" off the face of the Web. Which would be unfortunate as hell.

So yeah, I'd give this advice to anyone else creating fan art, such as lildevilinhell and his/her work, as I wouldn't want anyone's efforts to go to waste.

Jaismot:

(Thank you also for the imgur updates!)

I have no idea what you're talking about. :3

 
The drawing, the shading, the "emotion" are truly remarkable. The coloring in particular is especially striking. Really... vivid. Almost surreal.

Trois fois bravo + vingt fois chapeau.

last edited at Sep 8, 2015 3:22PM

Fan art by maestronot / Jaismot:

“Cling onto me.”

So, I think I will start to post here my fan-arts of Fluttering Feelings (a korean webcomic) by Ssamba.

Source:
http://maestronot.tumblr.com/post/120781126809/cling-onto-me-so-i-think-i-will-start-to-post
http://41.media.tumblr.com/d529deb07fc4c8f541336a582a4e7918/tumblr_nph9yztX951skmkkao1_1280.jpg

 
DAT COLORING

This is by Jaismot, who previously posted these 2 pieces of fan art.

Edit: Forgot to include the source URL before for some reason. Corrected and added.

last edited at Aug 18, 2015 3:10AM

100 pages. :3

 
 
The FF thread has now joined the proud ranks of other glorious series such as Stretch and Citr-- eh... other ones.

last edited at Jun 4, 2015 9:26PM

Thiron:

So, uh, if the chineese names sound completely different than the way they're written...
Why the hell are they romanized like that? Who the hell thought it's a good idea to write "TS" sound as "Q" or "SH" sound as "X"?
Even knowing it's different, I can only read english letters in english sentences in the way english language is supposed to sound...

Though pinyin, the standard romanization scheme for Mandarin, is not perfect, I don't think there is any possible way to properly romanize Chinese in a completely elegant and intuitive way while also accurately expressing and differentiating all the sounds of Chinese.

Unless Japanese's relatively simple soundset, Mandarin Chinese has many more sounds (both consonants and vowels), meaning any Chinese romanization scheme has the unwieldy task of representing more sounds than there are letters in the alphabet. An older scheme called Wade-Giles was arguably easier for a foreign person who is reading it for the first time to pronounce things closer to how they are supposed to be pronounced. However, it made use of weird letter combinations such as "hs" and also added apostrophes and umlauts to some letters to differentiate between different sounds. And the problem is that the apostrophes and umlauts would commonly be dropped (hard to type, laziness), in which case you cannot tell which sound it was meant to be.

So I personally prefer pinyin's simplicity and conciseness. Yes, you have to learn a few "weird" things, such as j -> j (sorta), q -> ch (sorta), x -> sh (sorta), zh -> j (but different from j), z -> dz (different from j), c -> ts (different from q). And 3 "shorthands": iu -> iou, un -> uen, ui -> uei. But once you know them, I find pinyin fairly efficient and concise.

last edited at Jun 4, 2015 9:36PM

Alextasha:

st/u/pid people...

But honestly I'm not surprised because of things some /u/sers were doing

I doubt she's doing this to "punish" the slightly unpleasant minority at the expense of all the others. And yes, those g/u/ys are a minority compared to the thousands of other English-reading FF fans on various sites (here, Tumblr, Facebook, so on) who act more like, how should I put this... normal human beings.

She likely does have something to do IRL. (Whoa, "IRL", imagine that.)

last edited at Jun 4, 2015 5:32PM

ON THE BRIGHT SIDE, LOOKS LIKE THOSE ENTITLED "OMG OMG 3 DAYS COMPLETELY UNACCEPTABLE WAHHH WAHHHHH" PEOPLE ARE GON BE DISAPPOINT ROFLFLOLO

last edited at Jun 4, 2015 4:48PM

Possible heads-up from halmoni (unless something changes):

I won't be doing any translations until Friday or Saturday of next week due to irl matters.

Erm... don't shoot the messenger?

last edited at Jun 4, 2015 4:42PM

Fan art by rainfallsuniverse:

I’ve drawn soft looking No-rae with her easy to trust brown eyes. Love this baby.

http://rainfallsuniverse.tumblr.com/post/120685783904/ive-drawn-soft-looking-no-rae-with-her-easy-to

 
 
... In loving memory.

LOLOLO

last edited at Jun 4, 2015 3:23PM

Here's one thing that's a bit unfortunate.

The period when this issue was present was from around May 31 (or possibly before that) till today, June 3, when the feeds were fixed. But if a user happened to have used the overtooning method during this period, it'll set something "bad" in their Local Storage, and so, even now that the feeds are fixed, the overtooning method still won't work for this user.

Example of a "bad" value in Local Storage:

For the domain http://comico.toast.com of course.

Key:
overloaderData

Value:
{"feedList":[{"url":"http://bumblebits.net/oddsquad/feed","name":"Oddsquad","lastUpdate":23885657,"teamUrl":"http://www.oddsquad.org"},{"url":"http://blackhorus.bumblebits.net","name":"BlackHorus Scans","lastUpdate":0}],"webtoonList":[]}

The way to fix this... well, the simplest way for a "normal" person is to clear cookies. That'll clear cookies and Local Storage. But of course, that signs you out of all sites you're signed into, which could be a bit annoying.

The "better" but more technical fix is to delete that specific faulty entry in Local Storage in the Developer Tools. But that might be a scary voodoo ritual to ask a "normal" person to do.

Another solution would be to go to any page on Comico (such as the FF chapter page), then in the address bar, type:
javascript: (you cannot paste this at least in Chrome and Firefox, so you have to type it)
Then right after that text, paste this:
localStorage.removeItem('overloaderData');
So it should look like this in the end:
javascript:localStorage.removeItem('overloaderData');
Then press Enter.
This would remove the faulty entry that prevents the overtooning method from working correctly.

 
BTW, just curious, what exactly is Local Storage used for in this case? I haven't looked at the whole code in great detail, so I'm not sure what exactly it's for, but I think it's to cache the feeds or something? Is it really necessary to be using Local Storage though?

Thanks!

last edited at Jun 3, 2015 10:15PM

Doonge:

@Anonymous

Sorry for the late reply, I don't really check here often.

Your diagnosis is right, I didn't bother to update the BlackHorus server because I thought it would not matter if it says it is not compatible with the script, as long as the main feed is compatible.
But I was apparently wrong, as apparently the script doesn't like it when one feed is incompatible and messes with localStorage. It is a bad behavior that I will fix (if a server is offline the script shouldn't care that much, for instance), in the meantime I'm updating the BlackHorus feed.

Indeed, you did not notice this problem earlier, because I properly updated both feeds when I added comico.jp. But I didn't bother when I had to add comico.toast.com.

One cannot have multiples domains in Access-Control-Allow-Origin, but one can uses the wildcard "*" that matches every websites, and one can adapt this header depending on the referer. As I didn't add toast.com as possible referer, the server just returned the default (the first) publisher: Naver ^^

edit: I think the problem is that I changed the blurb of Fluttering Feelings (following the scanlator instruction), but there are currently "forbidden" characters in it (slash "/"). So the script refuses to register the webtoon. I'm editing the blurb back as temporary fix. (extending the allowed characters is easy but will come with other things next update).

Thanks for replying to my post.

Yes, did a quick test just now, and it does work all the time now, not only the first time. So looks like it's fixed!

Will check the rest of your post in greater detail later.

If the need arises, what is the best way to contact you? (Although it should be very rare; this was a special case.)

last edited at Jun 3, 2015 12:11PM

otakuJin:

anonymous:

For the overtoon (overlay) method to read the chapter on Comico in English,
I made a visual guide webpage on how to set it up.

I tried to make it as easy as possible to follow by providing screenshots for every step.
Also, since it is a webpage, I put a link that you can drag and drop to set up the bookmarklet (rather than copying the JavaScript code, creating a new bookmark, then pasting).

Here's the page:
bit.do/ffovertoon

I actually wanted to make this in time for chapter 37 this past Sunday but didn't have the time, unfortunately.

Still a work in progress. Going to update it some more. I also intend on summarizing how Comico works.

Hope it'll prove useful. Feedback is welcome. (... but may be ignored. :3 )

I just want to let you all know that if it doesn't work again (due to cookies), just open your [Chrome] browser incognito. That works for me.

Thanks for confirming the issue, because I was starting to think this was only happening for me. (Despite having reproduced this on different computers in different networks.)

Indeed, Incognito Mode should be the easiest workaround for now for those who experience this issue. I just added the workaround to the page.

I'll paste it here too:

There is a temporary bug right now that some people may experience.
As a workaround to ensure that this will work for sure, open a "private window" in your browser:
Chrome: Press Ctrl Shift N (Command Shift N on a Mac) to open an Incognito Window
Firefox: Press Ctrl Shift P (Command Shift P on a Mac) to open a Private Browsing window
Internet Explorer: Press Ctrl Shift P to open an InPrivate Browsing window
After you're done reading the chapter, just close the private window.
Hopefully, this issue will be resolved soon and this extra step won't be necessary.

 
 
Alextasha:

You can always also try addon version http://bit.ly/1I4BpSQ

I might be wrong, but I think the addon version does the exact same thing as the bookmarklet, as in it runs the exact same Odd Squad script that does the overlays. It's just that the addon automates it for you.

If this is the case, then the same issue will occur. (Works once, then never works again.)

last edited at Jun 2, 2015 4:34AM

For the overtooning (overlay) method to read the chapter on Comico in English,
I made a visual guide webpage on how to set it up.

I tried to make it as easy as possible to follow by providing screenshots for every step.
Also, since it is a webpage, I put a link that you can drag and drop to set up the bookmarklet (rather than copying the JavaScript code, creating a new bookmark, then pasting).

Here's the page:
bit.do/ffovertoon

I actually wanted to make this in time for chapter 37 this past Sunday but didn't have the time, unfortunately.

Still a work in progress. Going to update it some more. I also intend on summarizing how Comico works.

Hope it'll prove useful. Feedback is welcome. (... but may be ignored. :3 )

last edited at Jun 6, 2015 2:37AM

Yomeiro Choice is funny but it's so wrong.

Yomeiro Choice is funny because it's so wrong.

Zombie No-rae
...
Seol-a x Geu-rim (No-rae's older sister)
...
And years later, Seol-a hooks up with little nephew because he LOOKS JUST LIKE NO-RAE. And he's got a dick, to boot.

Motion to add the Foursome, Necro, Incest and Shota tags.

last edited at Jun 1, 2015 6:22PM

Thanks, kyra!

Please check the huge post I made above about the technical issue that I experienced with the overlay method. If needed, please forward to Doonge as he/she might not be checking this forum.

In the meantime, if anyone is having issues with the overlay method with the bookmarklet, use Chrome's Incognito Mode (Ctrl Shift N) or Firefox's Private Browsing (Ctrl Shift P).

last edited at Jun 1, 2015 3:06AM

@ kyra / Doonge

For chapter 36 (last week's chapter), I just re-tried the overtooning (overlay) translations via the bookmarklet.

It worked in one Chrome profile but in a completely new Chrome profile as well as in Firefox, it didn't work.

 
Specifically, the issue that I observed was as follows.

If you are doing the overtooning method for the first time, it works. You click the bookmarklet, and the chapter is translated.
But if you reload the page and try it again, it doesn't work anymore. When you click the bookmarklet, only the orange Overtooning logo appears next to the Comico logo on the top left, but the chapter won't get the overlays.

However, if I clear cookies, then it works once again. But just like before, it only works once then never again.

 
So I took a look at the "OverTooning CONSOLE".

This is when it works:

[overlayLoader.path] pathname: /titles/[0-9]+/chapters/[0-9]+$
[overlayLoader.run] End of pathing.
[overlayLoader.query] Ping feed: http://blackhorus.bumblebits.net (1)
[overlayLoader.path] Queries to be made: 2
[overlayLoader.run] End.
[overlayLoader.cors] http://bumblebits.net/oddsquad/feed/comico.toast.com/85/37.json?1
[overlayLoader.cors] http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0
[overlayLoader.cors] Response returned with non-OK status
[overlayLoader.cors] undefined
[overlayLoader.cors] https://[...]/kr/37/no37p01.png
[...]
[overlayLoader.cors] https://[...]/kr/37/no37p15.png

This is when it doesn't work:

[overlayLoader.path] pathname: /titles/[0-9]+/chapters/[0-9]+$
[overlayLoader.run] End of pathing.
[overlayLoader.query] Ping feed: http://blackhorus.bumblebits.net (1)
[overlayLoader.path] Queries to be made: 1
[overlayLoader.run] End.
[overlayLoader.cors] http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0
[overlayLoader.cors] Response returned with non-OK status
[overlayLoader.cors] undefined

I noticed that the difference between the two is that the one that works has
http://bumblebits.net/oddsquad/feed/comico.toast.com/85/37.json?1
http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0
and the one that doesn't work only has
http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0

http://bumblebits.net/oddsquad/feed/comico.toast.com/85/37.json?1
appears to contain all the URLs for the FF overlays.
(The other one is for other comics.)

But it only loads it the first time, and every subsequent time, it no longer loads, and I assumed that this is why it would fail.

I wasn't sure why it doesn't load it the second time. I suspected it might have to do with what is saved in Local Storage the first time around due to this part in the naver.reader.oss.js code:

    for(var j = 0; j < this.data.feedList.length; j++) {
        if(accessFeed.indexOf(j) == -1 && this.data.feedList[j].lastUpdate + 60 * 24 * 7 < MTime) {
            overlayLoader.addLog('[overlayLoader.query] Ping feed: ' + this.data.feedList[j].url + ' (' + j + ')');
            this.queries.push({feedID: j, udpdate: true});
        }
    }

where this.data comes from:

    this.data = localStorage.getItem('overloaderData');

This would also make sense because when you clear cookies, Local Storage is also cleared.

 
So after a little more investigating, turns out it was definitely due to what was stored in Local Storage.

If I remove "Local storage" for the site "comico.toast.com", it works again.

Alternatively, I could go to edit Local Storage for "comico.toast.com"
Key:
overloaderData

Value:
{"feedList":[{"url":"http://bumblebits.net/oddsquad/feed","name":"Oddsquad","lastUpdate":23885657,"teamUrl":"http://www.oddsquad.org"},{"url":"http://blackhorus.bumblebits.net","name":"BlackHorus Scans","lastUpdate":0}],"webtoonList":[]}

If I change "lastUpdate":23885657 to "lastUpdate":0, then it works again.

 
Also, like I mentioned before, I have one specific Chrome profile where this issue is not occurring, as in, I use the bookmarklet multiple times without any problems. This is probably due to whatever was stored in Local Storage before.

In that Chrome profile, this is what's in Local Storage:

Key:
overloaderData

Value:
{"feedList":[{"url":"http://bumblebits.net/oddsquad/feed","name":"Oddsquad","lastUpdate":23885623,"teamUrl":"http://www.oddsquad.org"},{"url":"http://blackhorus.bumblebits.net","name":"BlackHorus Scans","lastUpdate":0}],"webtoonList":[{"wI":"85","wT":"Fluttering Feelings","wA":"ssamba","wB":"'Seol-a' and 'No-rae', two college girls that stumbled on one another.{endl}The sweet and sour story of two girls who are different in almost every single way.","fL":[0]}]}

 
So did something change in the naver.reader.oss.js code recently? This didn't used to be an issue.

Would you be able to find what's the issue?

Thanks!

 
 
 
 
 
The stuff below is what I initially thought was the problem when I first posted.
Now, I know that it has nothing to do with the issue.
However, it is still an error that you guys may want to look into.

---

In Firefox's Console, when I click the bookmarklet, I see this:

"[overlayLoader.path] pathname: /titles/[0-9]+/chapters/[0-9]+$" naver.reader.oss.js:1990:8
"[overlayLoader.run] End of pathing." naver.reader.oss.js:1990:8
"[overlayLoader.query] Ping feed: http://blackhorus.bumblebits.net (1)" naver.reader.oss.js:1990:8
"[overlayLoader.path] Queries to be made: 1" naver.reader.oss.js:1990:8
"[overlayLoader.run] End." naver.reader.oss.js:1990:8
"[overlayLoader.cors] http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0" naver.reader.oss.js:1990:8
Use of attributes' nodeValue attribute is deprecated. Use value instead. naver.reader.oss.js:2177:0
GET
XHR
http://blackhorus.bumblebits.net/comico.toast.com/85/37.json [HTTP/1.1 200 OK 242ms]
"[overlayLoader.cors] Response returned with non-OK status" naver.reader.oss.js:1990:8
"[overlayLoader.cors] undefined" naver.reader.oss.js:1990:8
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0. (Reason: CORS header 'Access-Control-Allow-Origin' does not match 'http://comic.naver.com').

Note the error at the end (bolded).

If I load
http://blackhorus.bumblebits.net/comico.toast.com/85/37.json?0
and check the HTTP header, indeed, I see this:
Access-Control-Allow-Origin: http://comic.naver.com

For this error to not occur, it would be to have "Access-Control-Allow-Origin" be "http://comico.toast.com" when serving URLs under http://blackhorus.bumblebits.net/comico.toast.com/. As far as I know, it is not possible to have multiple domains in "Access-Control-Allow-Origin".

last edited at Jun 1, 2015 2:28AM

@ halmoni / d.d.d.

Minor typos:

Box: A thouhtful guy with a snug embrace.

No-rae: That's becaue I didn't tell you;

Note that these are extremely minor and do not impact the story in any way, so it's totally up to you guys whether you want to fix it (especially the rough typeset).

last edited at May 31, 2015 10:43PM

CrescentLuna25:

I'm kind of disappointed in this chapter. Not because it has a bad story ( NO WAY! ).... One is because of No-rae's accident maybe -hopefully nothing bad happened to her- The main reason is Hee-jin

Read the name again...