User talk:CRGreathouse/lang tags: Difference between revisions

From Rosetta Code
Content added Content deleted
(<pre> for output, <lang…> for linguistic bits)
(don't use lang for output)
Line 1: Line 1:
==Using lang for output==
I checked on a few of the Java examples marked on this page and it looks like it is taking output snippets as examples without highlighting. I'm sure you figured it out yourself but I wanted to point it out in case you didn't notice yet. I'm not sure how to set up the criteria in the lang tag task so that this doesn't happen. --[[User:Mwn3d|Mwn3d]] 04:46, 28 November 2011 (UTC)
I checked on a few of the Java examples marked on this page and it looks like it is taking output snippets as examples without highlighting. I'm sure you figured it out yourself but I wanted to point it out in case you didn't notice yet. I'm not sure how to set up the criteria in the lang tag task so that this doesn't happen. --[[User:Mwn3d|Mwn3d]] 04:46, 28 November 2011 (UTC)
: is the &lt;lang&gt; tag used for output? that doesn't make sense. i think it should be &lt;pre&gt; or just indent. they all look the same anyways:
: is the &lt;lang&gt; tag used for output? that doesn't make sense. i think it should be &lt;pre&gt; or just indent. they all look the same anyways:
Line 6: Line 7:
:detecting if &lt;lang&gt; is used for output is hardly possible, one would have to analyze the contents.--[[User:EMBee|eMBee]] 07:56, 28 November 2011 (UTC)
:detecting if &lt;lang&gt; is used for output is hardly possible, one would have to analyze the contents.--[[User:EMBee|eMBee]] 07:56, 28 November 2011 (UTC)
:: It shouldn't be used for plain output (use <nowiki><pre></nowiki> for that) but it ''does'' make sense for highlighting an interactive session using the solution. Have a care! (Also note that some things that mention C are actually mis-labelled C# solutions; there are problems with interaction with wiki syntax.) –[[User:Dkf|Donal Fellows]] 14:55, 28 November 2011 (UTC)
:: It shouldn't be used for plain output (use <nowiki><pre></nowiki> for that) but it ''does'' make sense for highlighting an interactive session using the solution. Have a care! (Also note that some things that mention C are actually mis-labelled C# solutions; there are problems with interaction with wiki syntax.) –[[User:Dkf|Donal Fellows]] 14:55, 28 November 2011 (UTC)
::: Right, lang shouldn't be misused for output. On the other hand, it's entirely possible to have code for a different language in a section; for example, I recently wrote a section in which one language made a messy external call. To clarify I broke that section out (after finishing the code in the other language) in a short snippet marked <nowiki><lang bash>...</lang></nowiki>. [[User:CRGreathouse|CRGreathouse]] 18:53, 28 November 2011 (UTC)

Revision as of 18:53, 28 November 2011

Using lang for output

I checked on a few of the Java examples marked on this page and it looks like it is taking output snippets as examples without highlighting. I'm sure you figured it out yourself but I wanted to point it out in case you didn't notice yet. I'm not sure how to set up the criteria in the lang tag task so that this doesn't happen. --Mwn3d 04:46, 28 November 2011 (UTC)

is the <lang> tag used for output? that doesn't make sense. i think it should be <pre> or just indent. they all look the same anyways:
outout with pre
output with indent
<lang>output with lang</lang>
detecting if <lang> is used for output is hardly possible, one would have to analyze the contents.--eMBee 07:56, 28 November 2011 (UTC)
It shouldn't be used for plain output (use <pre> for that) but it does make sense for highlighting an interactive session using the solution. Have a care! (Also note that some things that mention C are actually mis-labelled C# solutions; there are problems with interaction with wiki syntax.) –Donal Fellows 14:55, 28 November 2011 (UTC)
Right, lang shouldn't be misused for output. On the other hand, it's entirely possible to have code for a different language in a section; for example, I recently wrote a section in which one language made a messy external call. To clarify I broke that section out (after finishing the code in the other language) in a short snippet marked <lang bash>...</lang>. CRGreathouse 18:53, 28 November 2011 (UTC)