Editing User talk:Jcdietz03

From Learning Languages Through Video Games
Jump to navigationJump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 2: Line 2:
 
First off, thanks for your efforts. :) They have certainly not gone unnoticed.
 
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.
+
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  
  
 
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.
 
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.

Please note that all contributions to LLTVG are considered to be released under the wiki's copyright terms (see LLTVG:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that, unless you are providing the text from a video game, you wrote this yourself, or copied it from a public domain or similar free resource.

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

(You don't have JavaScript enabled. If you did, you'd be able to see the handy-dandy fixers we have for reformatting text.)

The below button runs the selected formatting fixers for you.

To run the fixer, first select the text in the edit box that you wish to reformat, then click the button. The handaku/dakuten fixer should be fine to run on an entire page, but for the rest, be careful that only Japanese text is selected.

The fixer does not work in IE (as of IE 8), but it should work in other popular browsers. However, it works better in Chrome than in Firefox, because Firefox scrolls back to the top after running the fixer, and Chrome doesn't. Hence, if you're running the fixer on many small bits of text, you might prefer to use Chrome.