User:Pharap/Wiki Improvement Proposals

Improvement Proposals

Inline D'ni Dictionary Template

Reference	IP-001
Type	Template
Status	Unimplemented

Summary

The wiki has an extensive dictionary which at the moment isn't being particularly well leveraged from within templates and articles. I propose to change that by adding some templates that could make use of the dictionary in conjuction with the D'ni rendering capabilities of the wiki to provide rendered D'ni with hover text that provides information from the D'ni dictionary.

Notably, the hover text would be able display the three main ways of writing that word (Dnifont, OTS, and NTS), as well as the IPA pronunciation of the word.

Reasoning

This feature would make it easier to provide more linguistic information with less markup and less effort.

The primary way of implementing this template (see Example below) would allow using the name of the dictionary entry, which is likely easier for those who are not well-versed in Dnifont. However, a secondary implementation supporting Dnifont may be provided.

Having the IPA pronunciation would be particularly useful considering how many pages currently feature rendered Dnifont and OTS-style words but lack any corresponding IPA. The presence of IPA would be incredibly useful for readers who understand the meaning of the IPA symbols, as it would help them to know how to pronounce the various D'ni words and names that crop up throughout the wiki.

Example

A usage like {{D'ni word OTS|Teledahn}} could appear as thus: .

Hence one would only need to remember the name of the dictionary entry, and the template will generate all relevant information as part of the hover text.

Alternatively, a variant like {{D'ni word Dnifont|teleDan}} accepting Dnifont could also be permitted, as well as possibly a form that could accept either argument, such as {{D'ni word|ots=Teledahn}} and {{D'ni dict|dnifont=teleDan}}, perhaps even having {{D'ni word|Teledahn}} be treated as {{D'ni word|ots=Teledahn}}.

Ideally the hover text would be better formatted, more like the [[Has length::30 cm]] property from the Semantic MediaWiki addons: 30 cm0.0622 sp <br />11.801 in <br />0.983 ft <br />0.3 m <br />, but I have yet to investigate how that might be achieved.

Implementation

As a proof of concept, I have implemented all the aforementioned templates:

• A template that accepts a Dictionary page name:
  • {{User:Pharap/Templates/D'ni word OTS|Teledahn}} →
• A template that accepts Dnifont:
  • {{User:Pharap/Templates/D'ni word Dnifont|teleDan}} →

• A template that accepts either:
  • {{User:Pharap/Templates/D'ni word|Teledahn}} →
  • {{User:Pharap/Templates/D'ni word|ots=Teledahn}} →
  • {{User:Pharap/Templates/D'ni word|dnifont=teleDan}} →

Discovering how to implement this solution took me quite a lot of research as at first I didn't know about the existance of the OTS, NTS, and IPA properties, as their existence was somewhat buried in the Dict D'ni module and {{IPA}} template respectively. After figuring those out I managed to discover some modules that support the 'dnifont2ots' and 'dnifont2nts' functions.

It also took me a while to realise that the syntax [[Property::Value]] can be used to declare a value for a property in the same way as {{#set: Property=Value}}, and that consequently the following two lines of the D'ni Dict module are producing two properties:

• output = output..'* [[OTS]]: [[OTS::'..dnifont2ots(args['dnifont'])..']]\n'
• output = output..'* [[NTS]]: [[NTS::'..dnifont2nts(args['dnifont'])..']] '

Specifically:

• If the expression dnifont2ots(args['dnifont']) were to produce teledahn then the output * [[OTS]]: [[OTS::teledahn]] would be inserted into the page.
• If the expression dnifont2nts(args['dnifont']) were to produce teledan then the output * [[NTS]]: [[NTS::teledan]] would be inserted into the page.

In the case of the {{IPA}} template, I simply hadn't peeked at its source. At one point I had separately thought of the possibility of including such a property in the {{IPA}} template, but for a while after I had simply presumed that it wouldn't be there and hadn't thought to check until I ended up looking at the source by chance when editing my User page and noticing the property's presence.

After getting a working prototype, I went back and refined the templates several times, including changes such as adding a link parameter, changing how I was using the 'dnifont2ots' facilities (due to discovering a second module with the same functionality), and splitting the hover text over multiple lines.

Apocrypha Banner

Reference	IP-002
Type	Template
Status	Unimplemented

Summary

At the moment, apocrypha articles using the {{apocrypha}} template are marked with a small badge at the top right of the page which is unobvious and easily overlooked.

I propose that instead of (or in addition to) a small badge, apocrypha articles be marked with a large banner at the top of the page as is done with both Out-of-Cavern artices (e.g. Riven (game)) via the {{OOC}} tag and Unexplored Branches articles (e.g. Chiso Preniv) via the {{Unexplored Branches}} tag.

Reasoning

The reasoning behind this suggestion is to make apocrypha articles more obvious and less likely to be mistaken for 'official' content, particularly in cases where particularly well-made apocrypha with similar quality and/or appearance to official content might easily be mistaken for official content if one has overlooked the badge.

Example

The banner by including the {{apocrypha}} template would appear as thus:

The badge on the top right of the page could appear as it currently does or be omitted.

Implementation

The change could be enacted by the use of an {{ambox}} template.

<indicator name="apocrypha">[[File:Apocrypha.png|30px|link=GoArch:Apocrypha]]</indicator><includeonly>[[Category:Apocrypha]]</includeonly>
{{ambox
| type=notice
| image=[[File:Apocrypha.png|50px]]
| issue = is [[GoArch:Apocrypha|apocrypha]]. It should be considered [[GoArch:Canon policy|non-canon]] and may consist of fan-created content.
| small = {{#if:{{{sect|{{{section|{{{1|}}}}}}}}}|{{#if:{{{small|{{{left|}}}}}}|left}} }}
| sect = {{{sect|{{{section|{{{1|}}}}}}}}}
}}
<noinclude>
'''This template is for indicating that an article is about a non-canon subject. Non-canon subjects include:
* Fan-created content, such as the [[Lara Documents]] or fan-created Ages
* Material from the Dark Horse comics
* Ret-conned content from the Myst novels (such as [[Tadjinar]])</noinclude>

This template currently includes no documentation, though if any were needed it should simply be a matter of adapting the documentation provided for the {{OOC}} or {{Unexplored Branches}} templates.

Hover Text Template

Reference	IP-003
Type	Template
Status	Unimplemented

Summary

I propose introducing a {{hover text}} template like UESP's {{hover}} template, which is itself based on Wikimedia's {{H:title}}.

Reasoning

This new template would be useful for adding contextual information as a basic tooltip, and could be used as a base for building further, more complex templates.

Example

• {{Hover text|This is the hovertext|This is the main text}} → This is the main text
• {{Hover text|This is the hovertext|This is the main text|dotted=no}} → This is the main text

Implementation

The easiest way to impelement this would be with a title attribute on a span element. There may, however, be a better, more sophisticated, or more semantically correct way to implement the template. Fortunately, it can be amended after-the-fact if necessary.

Additionally, the text would be underlined with a dotted line to highlight the fact the user can hover over it, and the cursor could be optionally changed to the help cursor.

By default, the first parameter would be the hover text and the second parameter would be the main text. A dotted parameter would be used to disable the dotted line.

See {{User:Pharap/Templates/Hover text}} for a functional implementation.

Abbreviation Template

Reference	IP-004
Type	Template
Status	Unimplemented

Summary

This would function very much like the aforementioned {{hover}} template, but would instead rely on the <abbr> HTML element.

Reasoning

While the observable functionality is identical to {{hover}}, there would be a distinct semantic difference that may be of use to external tools, or perhaps to screenreaders.

Note, from Mozilla's documentation:

The title attribute has a specific semantic meaning when used with the element; it must contain a full human-readable description or expansion of the abbreviation. This text is often presented by browsers as a tooltip when the mouse cursor is hovered over the element.

Example

• Dictionary Abbreviations:
  • n.
  • adj.
  • prep.
  • pre.
  • suf.

Implementation

The implementation would use the <abbr> HTTP element and its title attribute.

See {{User:Pharap/Templates/Abbreviation}} for a functional implementation.

Sic Template

Reference	IP-005
Type	Template
Status	Unimplemented

Summary

At the moment the {{sic}} template merely produces a box with a link to Wikipedia, roughly appearing as [sic]. The template accepts word fragments, but doesn't do anything useful with them.

I would like to propose an alternative implementation of {{sic}} that would be based on UESP's implementation of {{sic}}. Specifically, it would accept the verbatim text and a corrected form, and provide the corrected form as hover text that appears when the incorrect word is hovered over with the reader's cursor.

(A surplus of examples can be found in the Bloodmoon:Airship Captain's Journal article.)

I would also propose that the revised {{sic}} link to an internal article on the wiki rather than externally linking to Wikipedia, to avoid the generation of the  icon, which clutters the page. The most obvious candidate at the moment would be the Quotations section of the style guide.

Reasoning

Merely highlighting that a word is incorrect is of limited use and provides only half the information necessary to understand the problem, relying on the reader to inuit both what the problem actually is and what the correct text should be.

Providing a correction not only informs the reader of what the text should have said, but helps them to recognise why the incorrect text is incorrect.

Example

Examples:

• {{User:Pharap/Templates/Sic|Whark|Wahrk}} → Whark [sic]
• {{User:Pharap/Templates/Sic|Ghen|Gehn}} → Ghen [sic]
• "{{User:Pharap/Templates/Sic|Muphry|Murphy|link=no}}'s law" → "Muphry's law"

To provide a more concrete example, Gehn's Lab Journal incorrectly says "discreet" instead of "discrete", and at present that looks like discreet [discrete] [sic]. With the proposed change, it would appear as (something more like) discreet [sic].

Implementation

A functional implementation can be viewed at {{User:Pharap/Templates/Sic}}.

IPA Hover Guides

Reference	IP-006
Type	Module
Status	Unimplemented

Summary

Wikipedia has an {{IPAc-en}} template that produces IPA that provides a pronunciation guide when hovering over the individual characters. For example, the Basalt page features examples such as /ˈbæsɔːlt/ where hovering over the 'b' gives "'b' in 'buy'", hovering over the 'æ' gives "'a' in 'bad'", hovering over the 's' gives "'s' in 'sigh'", et cetera.

It would be useful if similar functionality could be reproduced on this wiki.

Reasoning

It would provide a useful starting point for people who aren't familiar with IPA and are trying to understand how to pronounce various names and D'ni words.

Example

A hypothetical {{IPAc-en|t|ɛ|.|l|ɛ|.|d|ɑ|n}} would give /tɛ.lɛ.dɑn/.

Implementation

Despite being used as a template, this would be best implemented as a module.

The exact implementation is currently to be confirmed, but the general idea is simple enough:

• Each numbered parameter will be examined.
• The specific IPA character will be looked up in a table of tooltips.
• If a corresponding piece of tooltip text was found:
  • The character will be inserted into the page surrounded by a span with the title set to whatever the found tooltip was.
  • Otherwise, the character will be inserted without any additional processing.

The whole thing would be wrapped in a span element with its style attribute set to produce a dotted line, and that would be bookended by forward slashes.

Add a quote Parameter to {{cite journal}}

Summary

I propose to add a quote parameter to the {{cite journal}} template so that references may include specific quotes relevant to the claim being supported by the citation.

Reasoning

The intent of such a quotation would be to make it easier to verify claims as readers would not have to (for example) go hunting through entire journals just to find the one sentence that supports the claim made in the article.

Example

The quote parameter could then be used as thus:

<ref name="Tay">{{cite journal|author=Catherine|journal=Personal journal|journal-page=Reference:Catherine, personal journal (Riven)|game=Riven|quote=They have named it "Tay"}}</ref>

Producing an output of:

Catherine, Personal journal. Riven. "They have named it "Tay""

The presence or absence of quote marks and/or the style of the quote marks would be up for discussion.

Should anyone find the nesting of the same style of quotes unsatisfactory, I believe it should be possible to enforce the inner quotes being made a different style.

Implementation

This proposal could be implemented by simply adding {{#if:{{{quote|}}}| "{{{quote}}}"|}} to the existing template, such that it becomes:

{{{author}}}. ''{{{journal-nolink|[[{{{journal-page|Reference:{{{author}}}, {{{journal}}}}}}|{{{journal}}}]]}}}''. {{{game-nolink|[[{{{game-page|{{{game}}}}}}|{{{game}}}]]}}}.{{#if:{{{quote|}}}| "{{{quote}}}"|}}<noinclude>{{documentation}}</noinclude>

The documentation for the template could be ammended with:

"quote":
{
	"label": "Quote",
	"description": "A selected quote from the referenced journal. The chosen quote should be relevant to the article content that makes use of the citation. If omitted, no quote is included in the reference.",
	"example": "They have named it \"Tay\"",
	"type": "string"
}

As well as the addition of "quote" to the end of the paramOrder array.

Note: In regards to enforcing that nested quotes use a different style, I don't believe templates alone are capable of text replacement that sophisticated, though it's possible they support some sort of regex-replacement feature that I'm unaware of at the time of writing. To support such a feature would, I believe, require a Lua module. I haven't researched that as I'm presuming it won't be an issue, but should it be an issue I have sufficient experience with Lua and parsing that I'm confident I could make a good go of it.

Incomplete Proposals

• Further proposals for adding quote parameters to other cite templates, such as {{cite dialog}}.
• Add an access-date parameter to the {{cite forum post}} template.
• Add relevant details to Reference: pages that archive forum posts such that they can be properly cited with a {{cite forum post}}. In particular, the original forum post URL would be useful - the reference page should be considered the archived form if no Wayback Machine page exists.