Xenharmonic Wiki talk:Conventions
List formatting
Can we talk about Xenharmonic Wiki:Conventions#Lists? Why is it discouraged to use standard Wikitext lists?? Can we have a vote or something? —Keenan Pepper (talk) 18:57, 30 September 2018 (UTC)
- FREEZE used the truly standard list model. We should all trust FREEZE. PiotrGrochowski (talk) 19:00, 30 September 2018 (UTC)
- I think FREEZE is simply wrong about this. It's just bullshit and has nothing to do with the wiki idea. (I hope you were just kidding, Piotr) --Xenwolf (talk) 19:06, 30 September 2018 (UTC)
- Nope. The standard list model really is the most reliable. Ever heard of Internet Explorer 6? PiotrGrochowski (talk) 19:21, 30 September 2018 (UTC)
- I think FREEZE is simply wrong about this. It's just bullshit and has nothing to do with the wiki idea. (I hope you were just kidding, Piotr) --Xenwolf (talk) 19:06, 30 September 2018 (UTC)
- Absolutely yes (to Keenan): I love the "inoffical lists" and hate the
<ul><li></li></ul>stuff. Why make it so complicated??? Wiki means fast. I don't see anythong faster than placing*at the beginning of the listed items. I'm not aware that this was being discussed somewhere. --Xenwolf (talk) 19:03, 30 September 2018 (UTC)- The "FREEZE" thing was just me and Tyler playing with this until we got it to work. We never intended for these conventions to become standardized, it was just the easiest way to parse. Mike Battaglia (talk) 19:36, 30 September 2018 (UTC)
Informal poll
In favor of Wikitext (*) lists (4): User:Keenan Pepper, User:Xenwolf, User:Mike_Battaglia, User:Joemcmahon
In favor of HTML-style (<ul><li>...) lists (1): User:PiotrGrochowski
Should we imitate FREEZE artefacts?
In my opinion this would be contra-productive. Every wiki syntax aims to be as simple as possible and obvious also in the wiki text. You get the idea of markup's purpose easily. Ans it's easy to adapt for people new to the wiki ho to achieve a goal. It's normally not necessary to know HTML tags for editing wiki content. That's why lists should be created the wiki way (using * and #).
--Xenwolf (talk) 19:22, 30 September 2018 (UTC)
- I will always make lists with the proper, canonical syntax. What languages do various users know? is my page, therefore it is very clean, using the standard list model. PiotrGrochowski (talk) 19:25, 30 September 2018 (UTC)
- No, we should not imitate "FREEZE artefacts." FREEZE artefacts are just things that I screwed up. We should make it right. Mike Battaglia (talk) 20:20, 30 September 2018 (UTC)
- As a wiki author (as in, I've _written_ one of these), thepoint of wiki syntax at all is to permit you to write pages quickly without having to actually write syntactically-valid HTML. If there was no utility to adding wiki markup, it wouldn't have been added at all, and we'd just be opening edit boxes to paste in HTML. Which we would all have to always get right. Which we mostly would not, and would then spend time dorking with instead of writing about tunings. Wiki list markup, which is implemented in this wiki, is there to allow you to concentrate on providing content. Insisting on working against the tool, i.e., the wiki, by forcing HTML markup is counterproductive because it doesn't need to be done, and doing it is slower to write, and harder to update. And updating is the point of using a wiki at all. FREEZE is not a standard. It was a programming shortcut; insisting that it's a reason to hardcode HTML smacks of "I want to do this so I'm finding a reason" not "there is no other way to do this so I've adopted this workaround". There is no need for a workaround. Use the tools. Unless the markup cannot be done with wiki markup, it should not be there. Joemcmahon (talk)
- As I said, I'm not using some old fashioned, rusty
wikispacessyntax. PiotrGrochowski (talk) 05:28, 1 October 2018 (UTC)- This is definitely not "some old-fashioned wikispaces syntax". It's used by lots of simplified markup languages also used by Markdown. On the contrary, most wiki engines use it, please have a look at wikimatrix.org. Maybe it's time to give in now, isn't it?
Best --Xenwolf (talk) 10:37, 1 October 2018 (UTC)
- This is definitely not "some old-fashioned wikispaces syntax". It's used by lots of simplified markup languages also used by Markdown. On the contrary, most wiki engines use it, please have a look at wikimatrix.org. Maybe it's time to give in now, isn't it?
- As I said, I'm not using some old fashioned, rusty
- As a wiki author (as in, I've _written_ one of these), thepoint of wiki syntax at all is to permit you to write pages quickly without having to actually write syntactically-valid HTML. If there was no utility to adding wiki markup, it wouldn't have been added at all, and we'd just be opening edit boxes to paste in HTML. Which we would all have to always get right. Which we mostly would not, and would then spend time dorking with instead of writing about tunings. Wiki list markup, which is implemented in this wiki, is there to allow you to concentrate on providing content. Insisting on working against the tool, i.e., the wiki, by forcing HTML markup is counterproductive because it doesn't need to be done, and doing it is slower to write, and harder to update. And updating is the point of using a wiki at all. FREEZE is not a standard. It was a programming shortcut; insisting that it's a reason to hardcode HTML smacks of "I want to do this so I'm finding a reason" not "there is no other way to do this so I've adopted this workaround". There is no need for a workaround. Use the tools. Unless the markup cannot be done with wiki markup, it should not be there. Joemcmahon (talk)
- No, we should not imitate "FREEZE artefacts." FREEZE artefacts are just things that I screwed up. We should make it right. Mike Battaglia (talk) 20:20, 30 September 2018 (UTC)
What is the "Xenharmonic Wiki" Namespace for?
When do we use this instead of making a regular page? Mike Battaglia (talk) 19:41, 30 September 2018 (UTC)