Jump to content

sanahtlig

Backer
  • Posts

    3426
  • Joined

  • Last visited

  • Days Won

    33

Everything posted by sanahtlig

  1. Depends on the specific context and if the original topic itself had merit. The OP could certainly be ejected from his own topic if he didn't follow the rules, and the discussion could continue without him. For example, MangaGamer's forums had a rule against promoting piracy, and I discovered that MangaGamer was funding a well-known eroge piracy site. That would be grounds for ejecting them from their position of "authority", similar to the OP of a topic.
  2. Uh, instead of posting the machine translated output, could you post the actual Japanese from the hooked thread? Maybe a screenshot?
  3. Sounds like a prophecy from the scriptures. And then the locusts descended, and naught but desolate children's cartoons remained in their wake.
  4. Micromanaging users like this doesn't seem like a viable or scalable solution. It's too much of a burden on the moderators.
  5. If my proposal is impossible, perhaps moderators could consider suspending the offending users / instigators before locking threads? I really don't like seeing threads being locked. Punish the culprits, not the bystanders.
  6. I used the word "troll" in the title, but this is actually an intermediate measure aimed as much at regular users who have occasional difficulties engaging in civilized discussion.
  7. This is not a response to any particular incident, but rather an approach to handling and preventing future incidents. Technical hurdles may be involved. I still think it's worth looking into. Current approach: Suspend/ban the user(s), lock the thread, hide/delete posts Why this is not ideal: It chills discussion and obstructs the exploration of alternative viewpoints. It becomes difficult to discuss potentially controversial topics, which are often the most interesting and worthwhile discussions to have. Proposed approach: Ban the offending individual(s) from posting in that specific thread Why this is better: It punishes those who deserve it and does not affect everyone else (unlike thread locking). It removes the offending individual(s) derailing the thread and allows the discussion to continue (as opposed to locking the thread). It's a more permanent solution than hiding/deleting posts, which can allow the fight to continue. The punishment is lighter than a total suspension so it can be used more liberally. For these reasons, I think this would be a useful tool in the moderator toolbox.
  8. Sekai Project doesn't fear that customers won't buy their product (although that's a possibility). They fear their partners. They fear GIGA. Remember, this was a license negotiation that took 3 years, and Japanese companies tend to be very conscious of public perception...
  9. Sekai Project is genuinely concerned that fan backlash could scuttle this release. How do I know this? Sources.
  10. I delivered a brief speech on Twitter under the #BaldrGate hashtag. I present it here in a more readable format. I think Sekai Project doesn't acknowledge that censorship is a moral issue to many. They view it as a means to an end. (1) They cut their deals. They abide by the wishes of their partners. They try to respond to customer demand. (2) They don't understand the concerns of anti-censorship advocates. To SP, they're just a small but vocal minority. (3) It could be that SP only understands power. (4) If so, SP should reflect if it wants interactions with English fans to be a series of naked power struggles. (5) This is bigger than a single game. A single company. (6) It's about whether content alteration becomes the norm for English releases. (7)
  11. I complained about that too!
  12. Some people had to wait days to have their account activated. One person had to wait a month. I complained about this and they might have responded to my complaint in the live stream, but I'm not going to watch a 90-minute video just because they can't be bothered to reply directly. Also, a 90-minute video ramble is absolutely the worst way to convey information to those who simply want answers to their questions.
  13. Try installing the game with region format (time) set to Japanese. Also, don't use App Locale. Set your locale (non-unicode programs) to Japanese.
  14. A private chat, posted with the permission of the copyright holder.
  15. Tyr is tragically misunderstood. He just wants to have pseudo-philosophical discussions without being persecuted for his beliefs.
  16. If your audience is merely those who already know about your subject and its significance, then you're probably underselling your message. That's what I learned from my internship in science.
  17. Eroge helped me understanding humans, especially women. -- Tyr[osyn], 7/16/2016 Discuss.
  18. Organization of ideas crosses language boundaries. Not being a native speaker will not impede you. For my solution to a similar problem, take a look at my Windows 10 Visual Novel Compatibility Guide. Notice how I explicitly outline an existing problem and then my approach to solve it. This is a standard writing approach that should be useful in any sort of technical writing. I also make a habit of summarizing the article at the start so readers know what to expect and can see at a glance whether it'll be relevant to them before reading further. In science, the significance of any proposal outweighs all other factors. That's what inspired my current approach to technical writing. The quality of your content won't matter if you can't convince readers it is relevant to them.
  19. I think your lack of understanding stems from not understanding the creative process, as @tymmur said. Put effort into creating something novel. Then watch someone repost it somewhere else, changing a few things here and there--just enough to make it seem different--without even mentioning you. Then you'll understand. Basically, if you're cutting corners by using someone else's work as a template, you're cheating. Creators don't tolerate that.
  20. Imagine if someone took one of my blog articles, changed a few words here and there, and published it as his own and sold it for a profit. That's basically tracing in a nutshell. It's plagiarism. It's taking someone else's work and claiming it as your own without proper acknowledgement of the original. Both writing and drawing are creative processes, not mechanical replication. Every word and every line is supposed to be your's. Simply mimicking others at a low level is not permitted, although similarities at a high level (arguments, tropes) are fine.
  21. It could be helpful to explicitly describe your target audience near the beginning and the significance your article will have for them (and by extension, the community at large). Given that you've targeted this to the "Fan translation" forums, I think you have a very specific audience in mind. This was not at all clear when you posted it on Reddit.
  22. This. Disambiguating and adding precision is absolutely necessary when translating Japanese to English. I didn't tend to note issues like this in my coverage of the Seinarukana TL, but Decay is absolutely right that the new script in that scene reads much more fluidly. I don't know whether to praise the translator or the editor, but they did a fantastic job polishing it up. The earlier script sample demonstrates why I [used to] find reading moege in English such a chore. The dialogue is just so stilted and awkward.
  23. I'm still wondering where the 18+ patch is. As for the translation, if you want to see someone obsessing over actual TL mistakes in an otherwise professional release, take a look at my coverage of TL mistakes in Seinarukana. These are the sorts of issues you should be paying attention to, not silly and inconsequential deviations from fan norms. I discuss what may be systematic problems in the way VNs are translated that people don't usually talk about: sometimes serious issues like "I love you!" becoming "You love her!", which would normally seem unfathomable.
  24. Yeah, I'll probably cover such basics in my review. Or maybe in a separate gameplay guide. As long as it doesn't take too long. Compiling the translation error post took way too much time.
×
×
  • Create New...