User talk:Braiam - Revision history

KLSymph: /* Rakudai Kishi */ forgot to leave my name

2015-06-26T22:01:58Z

Rakudai Kishi: forgot to leave my name

← Older revision		Revision as of 22:01, 26 June 2015
Line 63:		Line 63:
	You asked: ''Why reverting the noinclude tag changes? It makes reading the "Full Text" volumes version awkward compared to other projects presentations, since it doesn't have the references at the end of the page (where most readers expect them to be). I don't understand why you revert a non-destructive edit.''		You asked: ''Why reverting the noinclude tag changes? It makes reading the "Full Text" volumes version awkward compared to other projects presentations, since it doesn't have the references at the end of the page (where most readers expect them to be). I don't understand why you revert a non-destructive edit.''

	I do not endorse placing references at the end of the volume, because for me the references represent page footnotes (though due to how the wiki works, this is equivalent to chapter end-notes), and I write the references accordingly: with the expectation that they are attached to particular chapters. Moving all of them to the end of the volume and numbering them consecutively the way that the noinclude tag does removes that context and therefore they become less informative at a glance. Since I did not write the references to be read as a glossary, they are sub-optimal when formatted that way. While it is true that full-text views on Baka-Tsuki generally put the references at the end of volumes, that is a common usage which I view as not the best for the Rakudai Kishi project, and since Baka-Tsuki allows projects to enforce their own individual formatting standards, I exercise that prerogative in this case. Hope that clears it up.		I do not endorse placing references at the end of the volume, because for me the references represent page footnotes (though due to how the wiki works, this is equivalent to chapter end-notes), and I write the references accordingly: with the expectation that they are attached to particular chapters. Moving all of them to the end of the volume and numbering them consecutively the way that the noinclude tag does removes that context and therefore they become less informative at a glance. Since I did not write the references to be read as a glossary, they are sub-optimal when formatted that way. While it is true that full-text views on Baka-Tsuki generally put the references at the end of volumes, that is a common usage which I view as not the best for the Rakudai Kishi project, and since Baka-Tsuki allows projects to enforce their own individual formatting standards, I exercise that prerogative in this case. Hope that clears it up. -- [[User:KLSymph\|KLSymph]] ([[User talk:KLSymph\|talk]]) 22:01, 26 June 2015 (UTC)

KLSymph: Rakudai Kishi response

2015-06-26T22:00:41Z

Rakudai Kishi response

← Older revision		Revision as of 22:00, 26 June 2015
Line 58:		Line 58:

	::::Yep, B-T notified me of the edit already. Thanks a bunch for your work! -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 15:59, 1 July 2013 (CDT)		::::Yep, B-T notified me of the edit already. Thanks a bunch for your work! -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 15:59, 1 July 2013 (CDT)

			== Rakudai Kishi ==

			You asked: ''Why reverting the noinclude tag changes? It makes reading the "Full Text" volumes version awkward compared to other projects presentations, since it doesn't have the references at the end of the page (where most readers expect them to be). I don't understand why you revert a non-destructive edit.''

			I do not endorse placing references at the end of the volume, because for me the references represent page footnotes (though due to how the wiki works, this is equivalent to chapter end-notes), and I write the references accordingly: with the expectation that they are attached to particular chapters. Moving all of them to the end of the volume and numbering them consecutively the way that the noinclude tag does removes that context and therefore they become less informative at a glance. Since I did not write the references to be read as a glossary, they are sub-optimal when formatted that way. While it is true that full-text views on Baka-Tsuki generally put the references at the end of volumes, that is a common usage which I view as not the best for the Rakudai Kishi project, and since Baka-Tsuki allows projects to enforce their own individual formatting standards, I exercise that prerogative in this case. Hope that clears it up.

Shift: /* OreImo v12c02 */

2013-07-01T20:59:14Z

OreImo v12c02

← Older revision		Revision as of 20:59, 1 July 2013
Line 38:		Line 38:

	::: I know from where you come as I had wrote/figure out code in Python, Javascript, HTML, and played around fixing (was more like hammering my way through) PHP where I didn't know what the heck was happening. (I still have a piece of over 2000 lines of JS that I still don't know how it works		::: I know from where you come as I had wrote/figure out code in Python, Javascript, HTML, and played around fixing (was more like hammering my way through) PHP where I didn't know what the heck was happening. (I still have a piece of over 2000 lines of JS that I still don't know how it works

			::::Haha, yeah. Programming can be like that. But no worries, judging by the "<ruby><rb>launch</rb><rp>(</rp><rt>public beta</rt><rp>)</rp></ruby>, emergency bugfix, repeat" cycle common with this past generation's games, there are corporate giants who don't understand thousands if not millions of their own lines of code.

	::Fun fact: The lack of trailing single-quote pairs is apparently by design, meaning they aren't necessary for lines that are entirely of a single style. Even the [//en.wikipedia.org/wiki/Help:Wiki_markup#Format wikipedia wiki-markup help] page mentions that the formatting marks only work on a single line. My guess is that it's to prevent exactly the issue one comes across when forgetting to close tags in HTML. Rarely does one honestly need to italicize multiple paragraphs of text at a time, in English, anyway. LNs at least seem to utilize much, much shorter "paragraphs", so sometimes multi-line formatting is needed for comparatively "large" blocks of internal monologue (more than a single thought).		::Fun fact: The lack of trailing single-quote pairs is apparently by design, meaning they aren't necessary for lines that are entirely of a single style. Even the [//en.wikipedia.org/wiki/Help:Wiki_markup#Format wikipedia wiki-markup help] page mentions that the formatting marks only work on a single line. My guess is that it's to prevent exactly the issue one comes across when forgetting to close tags in HTML. Rarely does one honestly need to italicize multiple paragraphs of text at a time, in English, anyway. LNs at least seem to utilize much, much shorter "paragraphs", so sometimes multi-line formatting is needed for comparatively "large" blocks of internal monologue (more than a single thought).
Line 54:		Line 56:

	:::Just submitting when you posted your response. --[[User:Braiam\|Braiam]] ([[User talk:Braiam#top\|talk]]) 15:48, 1 July 2013 (CDT)		:::Just submitting when you posted your response. --[[User:Braiam\|Braiam]] ([[User talk:Braiam#top\|talk]]) 15:48, 1 July 2013 (CDT)

			::::Yep, B-T notified me of the edit already. Thanks a bunch for your work! -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 15:59, 1 July 2013 (CDT)

Braiam: /* OreImo v12c02 */

2013-07-01T20:48:38Z

OreImo v12c02

← Older revision		Revision as of 20:48, 1 July 2013
Line 36:		Line 36:

	::I generally prefer wiki-markup to html-markup on the wiki, as well—except perhaps in cases where ''multi-line'' markup is necessitated (#4 on your list), if only because of the fact that it's much harder to miss an un-closed HTML tag than it is to forget to italicize a line at the end. Space concerns I won't address, except to say that, from a programmer's perspective, in this modern age clarity is often of greater (albeit subjective) value than brevity. As I said, I don't really disagree with the choice of wiki-markup over HTML markup, so there's really nothing to "argue" there.		::I generally prefer wiki-markup to html-markup on the wiki, as well—except perhaps in cases where ''multi-line'' markup is necessitated (#4 on your list), if only because of the fact that it's much harder to miss an un-closed HTML tag than it is to forget to italicize a line at the end. Space concerns I won't address, except to say that, from a programmer's perspective, in this modern age clarity is often of greater (albeit subjective) value than brevity. As I said, I don't really disagree with the choice of wiki-markup over HTML markup, so there's really nothing to "argue" there.

			::: I know from where you come as I had wrote/figure out code in Python, Javascript, HTML, and played around fixing (was more like hammering my way through) PHP where I didn't know what the heck was happening. (I still have a piece of over 2000 lines of JS that I still don't know how it works

	::Fun fact: The lack of trailing single-quote pairs is apparently by design, meaning they aren't necessary for lines that are entirely of a single style. Even the [//en.wikipedia.org/wiki/Help:Wiki_markup#Format wikipedia wiki-markup help] page mentions that the formatting marks only work on a single line. My guess is that it's to prevent exactly the issue one comes across when forgetting to close tags in HTML. Rarely does one honestly need to italicize multiple paragraphs of text at a time, in English, anyway. LNs at least seem to utilize much, much shorter "paragraphs", so sometimes multi-line formatting is needed for comparatively "large" blocks of internal monologue (more than a single thought).		::Fun fact: The lack of trailing single-quote pairs is apparently by design, meaning they aren't necessary for lines that are entirely of a single style. Even the [//en.wikipedia.org/wiki/Help:Wiki_markup#Format wikipedia wiki-markup help] page mentions that the formatting marks only work on a single line. My guess is that it's to prevent exactly the issue one comes across when forgetting to close tags in HTML. Rarely does one honestly need to italicize multiple paragraphs of text at a time, in English, anyway. LNs at least seem to utilize much, much shorter "paragraphs", so sometimes multi-line formatting is needed for comparatively "large" blocks of internal monologue (more than a single thought).

			:::Yeah, I was reading those looking how the trailing quotes worked about as once I tried to <nowiki>''Paragraph 1 / br / br / Paragraph 2''</nowiki> and didn't work (figures).

	::The thought/flashback thing (e.g., your "Sentence" ref.) is actually most likely due to the source text: occasionally the author uses 『』 style Japanese "double-quotes" (so to speak) to delineate flashback quotes or set-off otherwise significant lines. ''Actual'' thoughts aren't always so clearly marked off, and I suspect some of them are actually discretionary designations based on how the words are presented in the original text. E.g. something like "Ah, I get it already, shut up!" would seem more likely to be a thought than narration, and thus in the "TL" (EN -> EN, does it get any easier!) it might be presented as ''Ah, I get it already, shut up!''		::The thought/flashback thing (e.g., your "Sentence" ref.) is actually most likely due to the source text: occasionally the author uses 『』 style Japanese "double-quotes" (so to speak) to delineate flashback quotes or set-off otherwise significant lines. ''Actual'' thoughts aren't always so clearly marked off, and I suspect some of them are actually discretionary designations based on how the words are presented in the original text. E.g. something like "Ah, I get it already, shut up!" would seem more likely to be a thought than narration, and thus in the "TL" (EN -> EN, does it get any easier!) it might be presented as ''Ah, I get it already, shut up!''

	::The vast majority of narration is done from the past-tense first person perspective of Kyousuke, anyway, which can make it even more difficult to tell where Kyousuke is "recalling" something as a narrator and where he is "commenting" on it as a participant. My interpretation, anyway. I'm not the TL so I can only guess how it affects the TLs, past and present. I just reference the text occasionally to maintain consistency during edits, and that's the impression I've gotten thus far.		::The vast majority of narration is done from the past-tense first person perspective of Kyousuke, anyway, which can make it even more difficult to tell where Kyousuke is "recalling" something as a narrator and where he is "commenting" on it as a participant. My interpretation, anyway. I'm not the TL so I can only guess how it affects the TLs, past and present. I just reference the text occasionally to maintain consistency during edits, and that's the impression I've gotten thus far.

			:::For me is just annoying having to check the format (the last thing I do when writing a text anyways) and I try to interpret the point of view while reading in any case, so at least for me the formatting isn't important.

	::Anyway, I completely understand the potential for confusion—I've accidentally removed a few italic markups myself before realizing in the preview that the formatting was changed and the quotes didn't appear in the actual rendered page. I'm taking your response as go ahead to re-introduce those particular italics to the text, then? -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 15:27, 1 July 2013 (CDT)		::Anyway, I completely understand the potential for confusion—I've accidentally removed a few italic markups myself before realizing in the preview that the formatting was changed and the quotes didn't appear in the actual rendered page. I'm taking your response as go ahead to re-introduce those particular italics to the text, then? -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 15:27, 1 July 2013 (CDT)

	::Re:Re: Yeah, I actually watch any page I've edited for at least a few days to make sure there isn't any fallout or follow up, as applicable. It's just -so- much easier to follow a conversation that's on a single page. XD -[[User:Shift\|shift]] ([[User talk:Shift\|talk]])		::Re:Re: Yeah, I actually watch any page I've edited for at least a few days to make sure there isn't any fallout or follow up, as applicable. It's just -so- much easier to follow a conversation that's on a single page. XD -[[User:Shift\|shift]] ([[User talk:Shift\|talk]])

			:::Just submitting when you posted your response. --[[User:Braiam\|Braiam]] ([[User talk:Braiam#top\|talk]]) 15:48, 1 July 2013 (CDT)

Shift: /* OreImo v12c02 */

2013-07-01T20:29:19Z

OreImo v12c02

← Older revision		Revision as of 20:29, 1 July 2013
Line 45:		Line 45:

	::Anyway, I completely understand the potential for confusion—I've accidentally removed a few italic markups myself before realizing in the preview that the formatting was changed and the quotes didn't appear in the actual rendered page. I'm taking your response as go ahead to re-introduce those particular italics to the text, then? -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 15:27, 1 July 2013 (CDT)		::Anyway, I completely understand the potential for confusion—I've accidentally removed a few italic markups myself before realizing in the preview that the formatting was changed and the quotes didn't appear in the actual rendered page. I'm taking your response as go ahead to re-introduce those particular italics to the text, then? -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 15:27, 1 July 2013 (CDT)

			::Re:Re: Yeah, I actually watch any page I've edited for at least a few days to make sure there isn't any fallout or follow up, as applicable. It's just -so- much easier to follow a conversation that's on a single page. XD -[[User:Shift\|shift]] ([[User talk:Shift\|talk]])

Shift: /* OreImo v12c02 */

2013-07-01T20:27:08Z

OreImo v12c02

← Older revision		Revision as of 20:27, 1 July 2013
Line 34:		Line 34:
	# It uses less bandwidth/disk space since it only uses 32 bits of data.		# It uses less bandwidth/disk space since it only uses 32 bits of data.
	:Well, I said 3... but who cares about what I say. I will normalize the use of italics for two single-quote marks where I see fit in any case.		:Well, I said 3... but who cares about what I say. I will normalize the use of italics for two single-quote marks where I see fit in any case.

			::I generally prefer wiki-markup to html-markup on the wiki, as well—except perhaps in cases where ''multi-line'' markup is necessitated (#4 on your list), if only because of the fact that it's much harder to miss an un-closed HTML tag than it is to forget to italicize a line at the end. Space concerns I won't address, except to say that, from a programmer's perspective, in this modern age clarity is often of greater (albeit subjective) value than brevity. As I said, I don't really disagree with the choice of wiki-markup over HTML markup, so there's really nothing to "argue" there.

			::Fun fact: The lack of trailing single-quote pairs is apparently by design, meaning they aren't necessary for lines that are entirely of a single style. Even the [//en.wikipedia.org/wiki/Help:Wiki_markup#Format wikipedia wiki-markup help] page mentions that the formatting marks only work on a single line. My guess is that it's to prevent exactly the issue one comes across when forgetting to close tags in HTML. Rarely does one honestly need to italicize multiple paragraphs of text at a time, in English, anyway. LNs at least seem to utilize much, much shorter "paragraphs", so sometimes multi-line formatting is needed for comparatively "large" blocks of internal monologue (more than a single thought).


			::The thought/flashback thing (e.g., your "Sentence" ref.) is actually most likely due to the source text: occasionally the author uses 『』 style Japanese "double-quotes" (so to speak) to delineate flashback quotes or set-off otherwise significant lines. ''Actual'' thoughts aren't always so clearly marked off, and I suspect some of them are actually discretionary designations based on how the words are presented in the original text. E.g. something like "Ah, I get it already, shut up!" would seem more likely to be a thought than narration, and thus in the "TL" (EN -> EN, does it get any easier!) it might be presented as ''Ah, I get it already, shut up!''

			::The vast majority of narration is done from the past-tense first person perspective of Kyousuke, anyway, which can make it even more difficult to tell where Kyousuke is "recalling" something as a narrator and where he is "commenting" on it as a participant. My interpretation, anyway. I'm not the TL so I can only guess how it affects the TLs, past and present. I just reference the text occasionally to maintain consistency during edits, and that's the impression I've gotten thus far.

			::Anyway, I completely understand the potential for confusion—I've accidentally removed a few italic markups myself before realizing in the preview that the formatting was changed and the quotes didn't appear in the actual rendered page. I'm taking your response as go ahead to re-introduce those particular italics to the text, then? -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 15:27, 1 July 2013 (CDT)

Braiam: /* OreImo v12c02 */

2013-07-01T19:54:19Z

OreImo v12c02

← Older revision		Revision as of 19:54, 1 July 2013
Line 33:		Line 33:
	# The only advantage that has the HTML is for large chunk of text where single quotes is a hassle to use.		# The only advantage that has the HTML is for large chunk of text where single quotes is a hassle to use.
	# It uses less bandwidth/disk space since it only uses 32 bits of data.		# It uses less bandwidth/disk space since it only uses 32 bits of data.
	Well, I said 3... but who cares about what I say. I will normalize the use of italics for two single-quote marks where I see fit in any case.		:Well, I said 3... but who cares about what I say. I will normalize the use of italics for two single-quote marks where I see fit in any case.

Braiam: /* OreImo v12c02 */

2013-07-01T19:53:46Z

OreImo v12c02

← Older revision		Revision as of 19:53, 1 July 2013
Line 26:		Line 26:

	Cheers, -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 14:10, 1 July 2013 (CDT)		Cheers, -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 14:10, 1 July 2013 (CDT)

			:Yeah, for my point of view, they were more trailing quotes than attempts of using italics, as you can see only two single-quotes at the start of the line, instead both start and end, so I took them as mistake since they didn't appear to fit as murmur from Kyosuke and in same chapter line 4 (actually 12-something but I'm not going to count) translator used 'Sentence' for internal troughs/flashback, and that didn't looks like when I read the text and since formatting of internal troughs don't have defined rule in the guidelines I just went and deleted em. About the use of HTML syntax for the wiki, I'm rather against it for 3 reasons:
			# This is a wiki, not a HTML page, hence if it has a proper syntax, why reinvent the wheel?
			# I have 3 keys less to press when using single-quotes marks (not counting that for <> I have to use Shift too),
			# The source page looks cleaner that way.
			# The only advantage that has the HTML is for large chunk of text where single quotes is a hassle to use.
			# It uses less bandwidth/disk space since it only uses 32 bits of data.
			Well, I said 3... but who cares about what I say. I will normalize the use of italics for two single-quote marks where I see fit in any case.

Shift: /* OreImo v12c02 */ new section

2013-07-01T19:10:35Z

OreImo v12c02: new section

← Older revision		Revision as of 19:10, 1 July 2013
Line 14:		Line 14:

	As for the Spanish stuff, without those links, they have no home for now. And probably never will, given the pace (or lack thereof) at which it is being (not) worked on. I could do the Spanish translation myself, but (1) it would come out slightly odd to a native speaker (which I am not), and (2) it would slow down my progress on the Japanese to English translation. --[[User:Rpapo\|Rpapo]] ([[User talk:Rpapo\|talk]]) 05:05, 11 April 2013 (CDT)		As for the Spanish stuff, without those links, they have no home for now. And probably never will, given the pace (or lack thereof) at which it is being (not) worked on. I could do the Spanish translation myself, but (1) it would come out slightly odd to a native speaker (which I am not), and (2) it would slow down my progress on the Japanese to English translation. --[[User:Rpapo\|Rpapo]] ([[User talk:Rpapo\|talk]]) 05:05, 11 April 2013 (CDT)

			== OreImo v12c02 ==

			Doumo, doumo, konnichiwa...

			Your fixes to [[Ore_no_Imōto_ga_Konna_ni_Kawaii_Wake_ga_Nai:Volume_12_Chapter_2\|OreImo v12c02]] w/ regard to the misc. accidental wiki-markup missed before, et cetera, are much appreciated! However, I was wondering whether the [[Talk:Ore_no_Imōto_ga_Konna_ni_Kawaii_Wake_ga_Nai:Volume_12_Chapter_2\|removal of certain italics]] was intentional?

			I realize they can look a lot like unbalanced double quotes in the edit-view if they're done with doubled-up single-quotes (<nowiki>''</nowiki>''italics''<nowiki>''</nowiki>) rather than HTML (<i>''italics!''</i>), so I thought I'd see if that was the case. The last thing I want to start is a fight, so I figured it'd be best to check rather than assuming one way or the other and reverting those particular changes.

			That aside, thanks for staying vigilant with edits! Every positive contribution helps make the TLs that much better for the readers!

			Cheers, -[[User:Shift\|shift]] ([[User talk:Shift\|talk]]) 14:10, 1 July 2013 (CDT)

Rpapo: /* Golden Time main page */ new section

2013-04-11T10:05:47Z

Golden Time main page: new section

← Older revision		Revision as of 10:05, 11 April 2013
Line 8:		Line 8:

	I'm doing the V8C1+2.--[[User:Kadi\|Kadi]] ([[User talk:Kadi\|talk]]) 17:40, 14 September 2012 (CDT)		I'm doing the V8C1+2.--[[User:Kadi\|Kadi]] ([[User talk:Kadi\|talk]]) 17:40, 14 September 2012 (CDT)

			== Golden Time main page ==

			Please refrain from changing the volume header lines for "Golden Time". Those must stay the way they are, as the links between the chapters use them. Whenever you click on "Main Page" from a chapter page, it takes you back to the section header for the volume of the moment. When you move the "Full Text" stuff onto that line, it breaks the links.

			As for the Spanish stuff, without those links, they have no home for now. And probably never will, given the pace (or lack thereof) at which it is being (not) worked on. I could do the Spanish translation myself, but (1) it would come out slightly odd to a native speaker (which I am not), and (2) it would slow down my progress on the Japanese to English translation. --[[User:Rpapo\|Rpapo]] ([[User talk:Rpapo\|talk]]) 05:05, 11 April 2013 (CDT)