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)

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)

Informal poll

In favor of Wikitext (*) lists (2): User:Keenan Pepper, User:Xenwolf

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'm going to agree with User:Xenwolf here. 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. The FREEZE stuff was introduced because the person who wrote the conversion chose to just inline rendered lists instead of parsing and converting the markup. 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.user:joemcmahon