David Gamey wrote:
> Folks,
>
> I just confirmed something that I wish I understood a few days back. It's
> late and I'll write it up in the next couple of days and if people agree I'll
> fix the pages again.
>
> Basically the formatting and language/task recognition aren't coupled in the
> RC Wiki. This means we can have a heading, like Icon/Unicon with subheadings
> for the differences. It gets rid of the reference/redirect, duplication,
> and keeps the two languages together. It also means that the tasks
> complete/incomplete pages will reflect what's been don for Unicon and Icon
> separately. This shouldn't be a problem because if you follow a link to XYZ
> task unimplemented in Unicon and there is Icon code for it you'll see it very
> clearly.
So people know, I was just chided for using
=={{header|Icon and Unicon}}==
as a header. It causes problems with the linking. The proper form
to use is:
==Icon and Unicon==
and then the subheadings:
==={{header|Icon}}===
and
==={{header|Unicon}}===
-Steve
--
Steve Wampler {[email protected]}
The gods that smiled upon your birth are laughing now. -- fortune cookie
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
