Dec 1st: If your account has been hit in the most recent ban wave of compromised accounts please reach out to us at management[at]e621.net and we'll help you get your account back.
If you've already contacted us give us a moment to get to you, though if it takes longer than a day for us to get back to you do feel free to reach out again!
Dec 2nd: If you got got and suddenly aren't able to see any of our exquisite selection of sausage and taco posts double check that Safe Mode is disabled in your account settings (Account -> Settings -> Safe mode [right above the blacklist text box]).
Oct 24th: Did you know that as of this news update, 30.8k posts have been uploaded by 5.2k verified artists? Read our Artist Verification page to learn how to get faster approvals and a verified checkmark on your posts.
We still have a Discord server, come talk to us!
Want to advertise on e621? Click here!
Are you an artist uploading your own art to e621? Get verified now!
wous
PrivilegedIt feels like the translation in the child post is one of those careful machine translations.
Nicklo6649
Former StaffBecause it’s somewhat close to what it actually meant, unlike googles and many others?
wous
PrivilegedPretty much. It's like whoever did it couldn't actually read it, but went out of the way to make sure the translation made some sense.
彼女 at the beginning of the first set of boxes marks the words as being third person right off. If a human reader was really prone to that kind of mistake, they would never have been able to finish the rest of the page. Also, the リ in Sauria became ン turning it into saun'a. Simply misreading it that way is odd enough for a human mistake, but forcing it work where someone would normally think twice about what they were reading smacks of just making the best of what the machine gave them.
Login to respond »