I just hope this explanation helps Mindwipe understand why everything seems to go backwards. :P


Actually, doesn't it seem more like that closing tag is supposed to be there, but that the OPENING tag and the "NAME said:" line is missing?

Example ( mentally replace {s w/ [s, or be confused ):
{quote}Vanndril said:
{quote}Mindwipe said:
So, let me rage, goddammit.
{/quote}
Yes, I said I wouldn't tell you to stop raging, and I haven't. You can rage all you want, just do it more calmly, or you'll sour the mood even more than the update itself has. :P
{/quote}

That should display as:

Oh yeah, you're right. I would like nested quoting but I also understand why it would be disabled though (people quoting quotes of quotes of quotes until this becomes a mailing list).

I see it, too, of course. But certainly there must be a way to disable nested quoting without letting it break stuff when people manually do it. :P I'm going to report this as a bug.

This would explain why I've had trouble quoting people who quoted people recently.

Not really a bug, but a reason why the markup on notes sucks: line breaks still don't work. If you hit Enter between lines, it will just be ignored. You can only separate lines with a blank space, which looks shitty even on small bits of text: post #5700.

Yeah...and now that it was mentioned, I think this has always been the case. I remember struggling with this once or twice. So this is just an old bug that we never caught.


*shrug* Looks fine to me.

Well, what about the pics where it's not just a list of words, but several sentences separated by breaks?

I really don't understand why he can't find a good program for this. What does the Gelbooru software use? Even our bare-bones software back on Hypnobooru could handle text formatting, line breaks, and translator's notes.

I...don't even know what you mean. I mean, wouldn't you just type the translation and leave it as that, rather than mimic the format it's DRAWN in? Unless I'm mistaken as to what you mean, this seems to be an OCD issue. :P

Or, you know, you could do the same thing you do for images that have text that goes from top to bottom, right to left, and just make multiple note boxes.


That's a good question, but I'm assuming he has his reasons. You should ask him if you're concerned, though. Who knows, maybe he'll give you a satisfying answer, or you'll convince him to look again.

Not when doing so makes it into a big blob of text. Sometimes, it's easier to read when the lines are separated by breaks.



This isn't always the best solution, depending on the spacing of the text.



I don't remember what the thing's called, or I'd do some searching of my own. Though I'm surprised you didn't ask him that question back when he was still looking.

He programmed what, to me, is a complicated piece of work. This software is not simple. I just assumed he had his reasons and that that reason was likely an incompatibility to something this software uses.

I did, at least, figure out how the tags are arranged in the comments, mouseovers, and URLs. They're in the order they were added, which is a terrible way to arrange them, but now we know it's not random.

This may go without saying (not sure) but it's not just broken quotes that screw up the format of the entire page. I just quoted someone and accidentally left the closing spoiler tag without the opening one, and it broke everything below my post. So, it seems like any broken formatting will cause it.

And this kids, is why you don't <<stackoverflow.com/a/1732454/124119|parse markup with regular expressions>>.

I checked this with my crappy Android 2.0 phone (LG Ally) that I still have and frequently use for some reason, and I sadly confirm that I can't see the thumbnails either on this phone... I tried everything from clearing the cookies and the whole data a few times and it still hasn't worked, but that was only for the default browser I have... can anyone confirm this on other android brosers?

@Pendulum - That's a bit concerning. Granted, isn't Android 2.0...oh, I dunno, 5 versions ago? Isn't 7.0 on its way out, soon? I wouldn't know - phones are not my thing - but that's what Google leads me to believe.

If so, does anyone have an Android with a more up to date version that they could test this on, for us? I'm skeptical of the old version of the OS being the possible cause, with the new versions still working. But if it really is a bug, I'd love to report it. You know, so it can get fixed.