14,178
edits
mNo edit summary |
Greenpickle (talk | contribs) No edit summary |
||
Line 157: | Line 157: | ||
I think we should write, eg. VoR, EC, SC, FC for cave/area names in the table on this page, to avoid some of the messiness we have now, and have a key for it. <span style="font-family:times;">'''''[[User:Greenpickle|<span style="color:#080;">G</span>]][[User talk:Greenpickle|<span style="color:#050;">P</span>]]'''''</span> 05:50, 27 February 2012 (EST) | I think we should write, eg. VoR, EC, SC, FC for cave/area names in the table on this page, to avoid some of the messiness we have now, and have a key for it. <span style="font-family:times;">'''''[[User:Greenpickle|<span style="color:#080;">G</span>]][[User talk:Greenpickle|<span style="color:#050;">P</span>]]'''''</span> 05:50, 27 February 2012 (EST) | ||
:Agreed. Never looked at it closely, it really is quite a mess. Should we add a key, or make every acronym link to the correct article? '''{''[[User:Espyo|Espyo]]''<sup>[[User talk:Espyo|T]]</sup>}''' 06:55, 27 February 2012 (EST) | :Agreed. Never looked at it closely, it really is quite a mess. Should we add a key, or make every acronym link to the correct article? '''{''[[User:Espyo|Espyo]]''<sup>[[User talk:Espyo|T]]</sup>}''' 06:55, 27 February 2012 (EST) | ||
::That many links would be make the edit text huge. Just use a key. If people are in agreement and just taking the initials will give us distinct abbreviations, I can probably do this programmatically fairly quickly, so don't bother doing any of it manually. <span style="font-family:times;">'''''[[User:Greenpickle|<span style="color:#080;">G</span>]][[User talk:Greenpickle|<span style="color:#050;">P</span>]]'''''</span> 10:50, 27 February 2012 (EST) |
edits