@aruseus493 First, congratulations. You won the Most Misleading Topic Title of the Week Award thanks to "dark" and "leveling" in context of edgy RPG-style novel.

As for actual concerns, it's not likely to be caused by clipping (I doubt JNC would ever adjust colors unless assets they got were in a very wrong range or something). Here's a less bad screenshot from an app (with some extra scaling because of device's resolution and extra JPEG artifacts thanks to imgur)
alt text
Histogram here almost gradually falls near zero while clipping usually causes a peak with nothing after it (like here on 255, but that's kinda intentional). The first peak is are pixels with value of 10 and those are shadowed part of image. To make something disappear in that background you'd need to clip everything below 10 which would make lots of other lines disappear as well.

The loss of detail is caused by some combination of downscaling, JPEG compression, possibly denoising, and your screen being unable to show dark colors well.

@paulnamida

Arifureta is the third best-selling J-NC title I think. The WN already had a fan-base in the West when J-NC licensed it.

Someone is making it if you are interest.

https://forums.j-novel.club/topic/542/invaders-of-the-rokujouma-chapter-list-by-part

Sounds good, although of course this wouldn't be as much of a deal if you could automatically resume reading without so much hassle. This is a serious and longstanding problem so JNC really needs to make it a priority. I'd rather have a week without any new releases if it meant they actually made the app save and resume properly and allow you to easily get back to what you were just reading without losing your place or having to wait for splines to be repaginated yet again.

@Terrence

I need Shiki in my life.

@TooFiveFive

@Sam-Pinansky said in In Another World With My Smartphone Volume 4 Discussion:

@_08 the translator turned it in late, and the editor is off at anime expo. So it will be put up... soon? I hope? I don't want to pressure the editor while they are at ax.

Hence me moving the release date for part 2 to "undetermined". But part 3 will come out on time.

In any case maybe today, maybe tomorrow but I doubt much more than that.

Sam P.

@Michael-Pearson yeah, that's a good point! Sounds like a good test project for my new coder.

@Sam-Pinansky said in Sort library:

@Michael-Pearson Not a typo!

Don't you know that singular for many series is a serie?

(it is in my naming scheme anyway ;) ).

And my new engineer just started learning react! Having him add in sorting to the library sounds like a good learning project.

It might be best to add filter at the same time as sort. Then people can easily skip books they aren't interested in or have already read.

I reported it for Android (as quoted above). Interesting to know the bug affects iOS too. I hope it can be fixed soon.

This is also very important to me - as often I am places where I don't have Internet connection but want to be able to read. I don't want to buy epubs - I like the subscription model.

@Eclipzee I've seen the eBook releases listed on the release schedule page before so some are already there. It would be good to have them all listed though. :slight_smile:

@TooFiveFive Well it's got a 4.5 star rating from 4 people...

The books fine, Kobo just hasn't updated the page total for some reason.

Hmm, will try it, then!

I'm using Auro H2O, and since all kobo device are practically on the same firmeware cores, footnote should be no problem. I've had Kindle before and the epub->AZW3 should have no problem as well. Finally, footnote did not trigger any warning with Calibre's epub editor's "Check for bugs" feature, so I'm sure it's safe to assume that most, if not all, e-readers have no problem with it.

Sounds fine to me.

@TooFiveFive Agree, And I also want a following list too, it will be hard to keep track of the library when jnovel expand the title.

This has been ongoing for me since a little before the above linked threads.

To add the workaround methods that work for me:

If I go to the part I want to read, then click next part, the "back" button of my browser will typically bring me to zero percent on the part I want to read.

This workaround method doesn't save any clicks over the above quoted method necessarily, but it is a little faster if you find yourself clicking the part you want to read before remembering the method of clicking on the previous part (and have a next part button).

@Sam-Pinansky :smiley: :smiley: :smiley: :smiley: :smiley: