Table of Contents
Languages Meta
This article describes OOU notes on how different or alternative languages are used and described at the meta layer - that is, during composition and rendering.
Worldbuilding
For notes on the use of different languages as elements of Suocéverse worldbuilding, see the following pages (
require privileged access):
Rendering
In the primary release sites such as PC and AO3 that support semantic markup, some markup is used to denote two classes of dialogue where needed:
- (A) The dialogue takes place in a language separate from publication (eg.: Spanish in an English publication)
- (B) The language of the dialogue lies past the Human-Pokémon language barrier (eg.: most human languages in Pokécentric stories)
Where the platform allows, (A) is marked with the lang attribute and its specific value for the container of the dialogue. This allows futureproofing for eg.: audiobook conversions. Where the platform allows for container classing instead, both (A) and (B) are marked with a container and the value of the “lang” attribute reused for the classname. This allows for the reader to normalize the visual style by eg.: importing the VeniaSilente work skin into Stylus.
This is all about the semantics of the text and does not involve narration itself (where alternatives such as “[Character] said in Portuguese” can be used).
In the primary sites and others that support it, “live” translation for dialogue sections is provided via Ruby (annotation) / Furigana. For sites that don't provide such support, a campaign is ongoing to request semantic support. Non-semantic translation addendums can also be provided in other platforms with the same general model used for all VeniaSilente addendums: either an inline-level tag that can imitate Okurigana , such as superscript / subscript, or a block-level tag that can imitate an aside and can be inserted freely right at the end of a paragraph or section.
Tastes Anew is an example of implementation of the Furigana support. Dangerous Upgrade is an example of implementation of block-level asides (for notes, not language).
Site Support
This table shows the interlanguage support of publication platforms as of Apr 2023, and the strategy used in rendering human or Pokémon interlanguages for them:
| Platform | Ruby? | Aside? | Strategy / Alternatives |
|---|---|---|---|
| PokéCommunity | Y | Partial | Ruby is used normally starting 2023. PC CSS (eg.: [css-span]) directly styles language containers. Pending revision for the engine's migration to Xenforo. |
| AO3 | Y | Y | Ruby is used normally. ISO639-2 markup for <span> elements styles language containers.The VeniaSilente work skin provides classes for inline annotations. |
| Thousand Roads | N | Partial | Site help suggests it supports <dl>, sup/sub but renderer doesn't.Block-level asides (paragraph with right-alignment) are used for annotation. |
| Fanficslandia | N | Partial | Site help suggests it supports protected classes but renderer doesn't. Inline-level asides (highlightable spoiler sections) are used for annotation. |
| Canalave Library | N | N | Block-level asides (paragraph with right-alignment) are used for annotation. |
| Other generalistic BBCode forums | N | N | Block-level asides are used for annotation. |
| Generalistic Markdown renderers | N | Partial | Block-level asides (<html> escape sections) are used for annotation. |
| FF.net | N | N | lol. lmao, even. |
User Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International