rydenius wrote:[stuff about the one-volume registration rule]
so…… what do you propose we do about it? (TBH, it's a carry-over rule from the last guidelines. That's actually the only reason why it's there. xD)
rydenius wrote:Should this section (and #7 and #8 as well) have some kind of note about cases in which the project is stalled or there is no Project Manager. Maybe something along the lines of contacting a Supervisor?
Will be in the editor's guide/walkthrough. I dislike complicating rules to cover every single possible case, since covering the normal cases makes these rules long enough already. I think we should generally remember that this page describes guidelines/conventions of best practice. These aren't necessarily rules that we're banning people for if they break them @____@;; If fact, there are many users who don't even fully the current format guideline (i.e.: Teh Ping, many others…).
rydenius wrote:Yay for Incomplete templates. I'm glad to see a formal protocol for that. Should there be anything formalized about the chapter listing on the overview page? For example: chapter name (1/5) or chapter name (20%). Is that something we want to avoid in general because of the Android app? So far I haven't seen any problems with it breaking the app for the project I'm working on. (Hmm... that's sounds like it might be better located in the Overview guidelines, but chapter updates are noted here under #12, so it might fit there.)
Like denormative said, I see no real reason to have a requirement to alter the main page, especially if the incomplete template is being used.
rydenius wrote:Also are there other conventions that should be added to make pages more friendly to the Android app?
Not my area of expertise. Someone will need to communicate explicit recommendations to me.
Misogi wrote:[All of the minor edit recommendations]
Added. You know, you're free to edit the page yourself, especially if they're really really minor things (like grammar). ;D
Cthaeh wrote:If any of this ends up requiring that the default text at the top of registration pages be updated, it would probably be a good idea to make a single page/template to get transcluded into the top of registration pages. That way any future changes or updates would only need to made once.
From my experience, each project can place slightly different text on top of their registration pages (depends on what they do for project-specific guidelines). So in that sense, I'm not sure a template would be as useful as we think, if a lot of projects end up writing something custom. IDK though.
Cthaeh wrote:Two weeks seems pretty short to me. I don't think it's unreasonable for someone to be out of contact for two weeks. The "apparently Inactive Translator" implies there is a longer period of inactivity than just two weeks (though I don't see a definition for it), so maybe the two weeks to try to contact isn't as unreasonable. I would personally make it something like after two weeks, contact the project manager or wiki supervisor who tries to contact the inactive translator themselves through multiple means, and then 1-2 weeks after no contact again the reservation is annulled (so at least a total of 3-4 weeks of no contact, if not more, plus some amount of general inactivity).
As you pointed out, the "general inactivity" is the key point. Honestly, I wouldn't want to expand a requirement longer than 2 weeks, because I see projects like Hatamaou where lots of people register for a chapter but never upload a thing, and vanish. Their names stay on the registration page and new members don't want to overwrite those registration slots. Hatamaou, by the way, gets a lot of new members.
If I could Supervise Hatamaou, I would put in a requirement that registration slots automatically expire in 1 month if you fail to upload anything (and mark incomplete). But that would be a project-specific type guideline that I think would be better suited for cases like Hatamaou.
Also, the clause of contacting the Project Manager is supposed to play two roles. A): The PM knows of the original translators is actually active or not. B): The PM could try contacting the inactive translator. C): The PM could just say no because he/she knows the (potentially) inactive translator already started some translations, or for some other reason. Furthermore, the PM could opt to ask the interested translator to wait longer than two weeks.
I guess my concern is that there's an active translator who wants to translate (but can't because of logistical restrictions). Compared with an inactive one, I'd rather let the active one translate sooner.
AKAAkira wrote:Inline Illustrations should be placed so that it will be displayed adjacent to the passages written in the page opposite of it in the original novel. To do this, place the relevant piece of code directly before the sentence that starts the page before the picture.
Done.
denormative wrote:Not directly relating to these rules I guess, but with the 'Manual of Style' section, it might be worth having a minimal "this is a suggested way of handling things for Japanese translation 'style' quirks". Things like...
Want to make a Baka-Tsuki Manual of Style? ;D I'll take you up on it if you can start brainstorming items for it. Perhaps split this and add it to AKAAkira's format guideline thread.
Onizuka-gto wrote:Editing: I recommend that any edits per session (i.e. 5 changes, userx5) that exceeds 1000 words will be considered a "Major Edit".
As for monitoring purposes, anything over this number tells me an edit is not minor in any such form as it will have takes a person considerable effort in one sitting session or of an vandalising nature, therefore require my attention to to check the username against the project staff and registration list if it is not familiar. If it is an anonymous, then i will revert it immediately.
We've defined a major edit as anything that would necessitate an editor contacting the translator… so does that mean we should try and shift some definitions?
rydenius wrote:Regarding tense it's probably good to have some general guidelines, and maybe I'm a bit naive on this, but shouldn't the translator do his or her best to maintain the tense found in the original work?
Arguably, you could say all stories in Chinese narrate in present tense. But that's the norm in asian literature. It would be weird to carry it over literally.
i.e.: "Once upon a time, in a land far far away, there is a dog who chases mice. This dog loves being mean to mice, and eats all the mice he can. One day this dog runs outside and sees a mouse. He thinks it's great that he can chase mice every day!"
In Western languages, the normal way of telling a story is in past tense (hence, the classic openings like "On a dark and stormy night" or "Once upon a time"). While it's become increasingly common to narrate novels in present tense nowadays, it's an unusual narrative tense for an English reader.
As a translator, I often say it's important to translate the effect, not the literal. A japanese reader reads a novel seamlessly. With that regard, the translation should read seamlessly. If we translated the tense as present, it can stick out and feel "unusual." But that feeling wasn't present for the original japanese reader.
http://www.baka-tsuki.org/project/index ... kaya_style Something you might find interesting. ;D Lare-tan is amazing, as usual.
Kira082 wrote:For
>Editors are REQUIRED to contact the Project Staff for Major Edits
I suggest to put them on the chapter's discussion page. If it's a general on, then put it on the project discussion page.
We had this discussion before. xD
From what I observe, the most popular way editors communicate with translators is on user talk pages (or some other direct communication means).
With that respect, I'd prefer that these conventions reflect the most popular behaviors on Baka-Tsuki. Of course, if you'd prefer that editors put them on chapter discussion pages, that's something as a translator you can request.