User talk:Jcdietz03

Some critique

First off, thanks for your efforts. :) They have certainly not gone unnoticed.

I have a bit of advice, though. For one thing, I think you're overusing the br tag. I don't like the br tag at all and think it should very rarely be used. Usually you should either keep things on one line (which is generally the case for game text; use a space or not depending on which seems more appropriate) or put a linebreak between them. I think it was Blutorange who came up with the compromise of using bullet points for when we have multiple annotations after a translation block; I'm thinking about officially adopting that convention, which would reduce the number of instances where br would be necessary.

The other issue is I think sometimes your translation blocks are too large. I think translation blocks should generally correspond to one "screen" of game text, and only include more when the division would hurt comprehensibility. (When game text isn't clearly divided into screens with complete sentences, or the screens are too long, I typically use one sentence per block -- sometimes two if one of them is really short, or a stock phrase such as おめでとうございます.) The rationale is that smaller blocks make it easier to correlate the Japanese text with the translated text.

But in any case, 頑張って and keep up the good work! - furrykef (Talk at me) 04:33, 20 April 2011 (UTC)

Please check out LLTVG:Sandbox for an idea for parallel-text. There is probably a better way to implement this, as I am not a programmer. If you need more info on parallel-text, please check the other wiki (though it is admittedly a bit sparse). You can check out some ja-en parallel text books here to see what they look like. I dislike looking up/down to see parallel text and prefer left/right. It is simply my preference. I am not sure about conventions used in parallel-text works, so I cannot say which convention is more commonly used. I just finished reading

Understanding Basic Japanese Grammar which uses parallel text almost exclusively as the method of instruction. Parallel text in this book uses the left-right convention.

You commented that my translated text blocks are too large. This is not in the guideline. Also, I disagree with this as a proposed guideline. When one character is talking at length, it's appropriate to have a huge block of text. I don't think it's appropriate for conversations as it is difficult to tell who is talking. If your knowledge of Japanese is sufficient, you just want to read the text and the wiki markup gets in the way of that. If your knowledge of Japanese is not sufficient, you want to refer to the translation. I think left-right parallel-text (instead of up-down) will make this type of reference easier for readers but harder for editors.

You commented that I excessively use the br tag. Guilty as charged. However, this is not in the guideline. The guideline I use when editing is that one screen of dialogue (up to three lines) per one line in the wiki. I use the current guideline as well (use br tag if a sentence ended without punctuation). The other guideline I use is that if the writer couldn't quite fit what they were trying to say into three lines, I include the extra in the previous line. Jcdietz03 21:15, 20 April 2011 (UTC)

Hi, I reposted this here so we can keep the conversation in one place. Don't worry, I'll definitely see any additions here.

Parallel texts is one possibility and it would indeed justify longer passages in translation blocks. I'll have to give it some thought.

I'm surprised that the manual of style doesn't mention the "one block per screen" rule. I could have sworn that it did, but sure enough, it doesn't. I must confess I'm not convinced it's a bad rule, though maybe we can do away with it if we adopt parallel texts...

I disagree that using short blocks would make it hard to keep track of who is talking. The 'speaker' paramater to ja-en should be used whenever that might be unclear. - furrykef (Talk at me) 23:28, 20 April 2011 (UTC)