PathfinderWiki talk:Naming conventions

From PathfinderWiki
Archives:

Note true naming exception for spoilers

Green check.svg

Changes Accepted
This section contains a discussion about changes to this policy that have been accepted.

Per User:Yoda8myhead on PathfinderWiki talk:Canon policy, add an exception to the true names policy explaining spoiler avoidance.

  • Use true names. Article names should reflect the native or true name of the subject. For example, use [[Scanderig]], not [[Forgefiend]]. If a common or colloquial name for the subject exists, create a redirect to the main article: [[Forgefiend]][[Scanderig]], using the previous example.
    • Exception: Default to the most commonly used in-world name for articles whose alternative titles could constitute a spoiler. This gives people who don't know the secret a warning that something they might be playing or reading could be spoiled by continuing to read the article.

-Oznogon (talk) 01:28, 19 December 2018 (UTC)

Would love to have any additional consensus on this proposal, especially from HTD since the related examples are their edits. -Oznogon (talk) 18:04, 20 January 2019 (UTC)
Agreed from me.--Fleanetha (talk) 23:16, 20 January 2019 (UTC)
I'll also support this change. --Brandingopportunity (talk) 01:02, 21 January 2019 (UTC)
Likewise, makes sense to me, so agreed, particularly the exception. --Kniedzwi (talk) 02:22, 21 January 2019 (UTC)
Noting here the request at Peacock Spirit / Xanderghul requiring a change if this policy is accepted plus the Move request at Glorio Arkona that would need deleting. Any others? --Fleanetha (talk) 12:27, 21 January 2019 (UTC)

True name convention for creatures

In light of the release of the 2E Bestiary, two creature articles got renamed from their true/native name to their common name (aboleth/alghollthu master and neh-thalggu/brain collector), in contrast to the Use true names convention. Does this guideline apply to creatures anymore? - HTD (talk) 11:15, 25 October 2019 (UTC)

They're now consistent with the articles you created and {{Alghollthu navbox}} entries you added, boss. -Oznogon (talk) 18:08, 25 October 2019 (UTC)

Accommodate name changes from 1E

Green check.svg

Changes Accepted
This section contains a discussion about changes to this policy that have been accepted.

In the "Specific Considerations" list, add:


  • Name changes between editions. Articles should generally use the most recent canon name for a subject, which might result in a different name for subjects whose names changed between Pathfinder First Edition and Pathfinder Second Edition. This is particularly relevant for creatures whose names have been updated or retconned in Second Edition, as well as locations, organizations, and characters who have changed names or identities in Pathfinder Lost Omens setting timeline advancements. Articles should:
    • Always incorporate the First Edition name in the lede, with a canon explanation for the change if possible.
    • Always note the alternative name in the name field of any relevant infoboxes, if both names are considered canon. List the Second Edition name first, separate the names with a <br> line break, and if a name is used only in First Edition content, flag it with the {{1E name}} template to link it to this policy for context: | name = Naiad queen<br>Nymph{{1E name}}
    • Optionally provide context for edition-specific naming in the article's "References" section.

Please see Talk:Naiad queen#Finishing the job for an example of why this policy is necessary to maintain consistent references and context for articles on subjects that span editions. -Oznogon (talk) 23:44, 30 October 2019 (UTC)

No disagreement in over a year and this has anyway become de facto policy. Therefore, I am accepting this policy change formally and will update as needed. Thanks Oznogon for raising this and crafting the words for the update. -Fleanetha (talk) 10:29, 12 December 2020 (UTC)