Minor error/s

Posted in

#426 by yorhel
2020-06-16 at 13:41
Space after the resolution? I see I don't handle that either...
#427 by shining17
2020-06-16 at 13:42
There's no space before and after the res...
#428 by beliar
2020-06-16 at 20:56
This edit form link for some reason returns a warning "Original title does not seem to contain any non-latin characters", despite the original title being in Korean.
#429 by yorhel
2020-06-17 at 08:25
@428: New feature, needs some tuning. :) Hangul is recognized now.

I've also relaxed the resolution field a bit, it now ignores spaces and recognizes * and unicode ×.
#430 by rampaa
2020-06-17 at 18:18
Does the issue I've mentioned at t2520.415 only happen on my end?
Just to clarify:
This is how I see my own message: link
This is how my message should be displayed ideally: link
This is how I see the original title of the aforementioned game: link
This is how the aforementioned game's original title should be displayed ideally: linkLast modified on 2020-06-17 at 18:22
#431 by yorhel
2020-06-17 at 18:41
Does the issue I've mentioned at t2520.415 only happen on my end?
Not entirely, but it manifests itself differently on my systems. Firefox on Arch Linux renders it correctly in all contexts, Firefox on my Gentoo system renders it correctly except in tags marked with the lang="ja" attribute, which somehow ends up looking like link
#432 by rampaa
2020-06-17 at 18:59
That is weird. The screenshots I've provided was from Firefox on my Windows system. I get the exact same results with Opera. However when I try it with either Chrome or Edge, I get the same result as you do with your Firefox on Gentoo system, ie. it does not display the ♡ character at all.

Something to note, every character other than ♡ is being displayed with Meiryo on my end (as they should be, thanks to lang="ja" thingy) for the original language section, but ♡ alone is being displayed with Tahoma. See link and link.

When I force VNDB to use Meiryo, the character is being displayed correctly.

EDIT: Forgot to mention, the character *is* being displayed correctly below the main title(?) section with all browsers mentioned. See: linkLast modified on 2020-06-17 at 21:40
#433 by beliar
2020-06-22 at 17:24
If you turn a full release entry into a patch and it had the Engine field filled in, the Engine remains with the patch but cannot be edited or removed from the edit form without turning it back to a full release first.
Example: r65216.
#434 by yorhel
2020-06-22 at 17:29
Fixed.
#435 by harleyquin
2020-06-28 at 02:41
I'm trying to add link to the external link section in link, but I keep getting an invalid URL. I've tried restricting the entry to the RJ entry alone and various combinations of the full link (without https etc.) but nothing works.

Is it because the game is not yet available?
#436 by yorhel
2020-06-28 at 05:55
Yes, /announce/ links can't be added at the moment.
#437 by literallolicon
2020-06-28 at 14:15
idk if this question is raised in the right board, but is づ and ず both romanized as "zu" in vndb? I'm used to the romanization of づ as "dzu" to differentiate between the two.
#438 by naiohoras
2020-06-28 at 14:54
yes. you can see the example for them in "Hitozuma", which is written instead of "Hitodzuma"
#439 by literallolicon
2020-06-28 at 16:42
I can see, but why not make the distinction? It's not really that hard, and it keeps the accuracy of Japanese romanization.
#440 by harleyquin
2020-06-28 at 17:05
I can see, but why not make the distinction? It's not really that hard, and it keeps the accuracy of Japanese romanization.

One thing I remembered from class is words using づ are uncommon compared to ず. Not to mention there is little difference in the vocal pronunciation. Since this database relies on the kana conversion table in the anidb romanization list, that's the way it is. You'll have convince the administrators here to follow your proposal to get your way.
#441 by gvbn
2020-06-28 at 17:56
In standard Japanese there's no difference in pronunciation between ず and づ link

VNDB uses Hepburn romanization, which prioritizes pronunciation over one-to-one transcription and consistency (e.g. particles は/へ/を become wa/e/o instead of ha/he/wo, and kana group たちつてと becomes ta-chi-tsu-te-to instead of ta-ti-tu-te-to) so both ず and づ become "zu" under Hepburn rules.
#442 by rampaa
2020-06-29 at 01:06
VNDB has been weird lately. I am not sure what are the necessary steps to replicate the problem. So I will list a few things that have happened:

Sometimes, when I click to "Recent changes", the changes listed are not the most recent ones at all. I need to press F5 to actually see the most recent ones. Same goes for nearly everything else, be it character history or forum discussions.

Most recentely, I saw, let's say, user X's name on "Last post" section. And to read his comment, I clicked on the thread and went to the last page, only to see his comment is not there. Again, when I pressed F5 to forcibly refresh the page, I was able to see the comment.Last modified on 2020-06-29 at 01:07
#443 by harleyquin
2020-06-29 at 02:10
Delete cookies and log in to the website again.
#444 by yorhel
2020-06-29 at 10:15
VNDB has been weird lately.
Hey, don't blame VNDB for decisions made by your browser. VNDB doesn't set a caching policy on its pages, so whether or not pages get cached is up to your browser settings.

I honestly haven't a clue what caching policies are in common use nowadays...
#445 by rampaa
2020-06-29 at 10:35
I didn't update my browser or changed any caching-related setting so I rulled out it being Firefox's fault, because the problem was not there till approximately a week ago.

Anyway, I guess I was off the mark about it being VNDB's fault, sorry. :/
#446 by wakaranai
2020-06-29 at 15:18
> I rulled out it being Firefox's fault

i wouldn't be so sure. i was so tired of their dev's shenanigans with breaking changes and other bs, i've dropped firefox 2 years ago after using it for 15+ years and i should have done it sooner tbh.
#447 by naiohoras
2020-06-29 at 17:41
link is empty...
#448 by yorhel
2020-06-29 at 18:32
Firefox sucks, but the alternatives aren't much better. Much worse, most of them. At least FF can be tweaked quite a lot. Still mad that they broke vimperator, though.

link is empty...
And it's been empty for at least 12 years...
#449 by shining17
2020-06-29 at 18:45
Is there any better browser than Firefox though? Chrome, Opera, Safari, Edge are all shit.
#450 by naiohoras
2020-06-29 at 18:59
And it's been empty for at least 12 years...
well, that's a record since I never visited that page at all since I got here for the first time in 2014. why do you leave it empty anyway?