Homebrew: Language
v1.1.0
🍺language
<description_of_the_homebrew_category_and_use>
An Example:
The _Meta is normally included in a full JSON, for this example it has been removed. See the link for how to develop the _meta.
"language": [
{
"name": "Semaphore",
"source": "json_in_meta",
"entries": [
"Remember to prefix the message with \"GNU\"."
],
"type": "secret"
}
]
Learn More
- In the example; <description_of_results/fields>
Field List (Sources)
If you do not include the required fields (denoted with bold text) the JSON may pass JSONLint but will fail upon stitch.
| Field Name | Data Type | Description | Required |
|---|---|---|---|
| name | String | The Name for the language | True |
| entries | Array of Strings | Other Names | False |
| source | String | json (_meta's json value) | True |
| page | Integer | The Page number it apepars upon | True |
| srd | Boolean | Is this language part of the SRD | False |
| typicalSpeakers | Array of Strings | what groups or creatures use this language | False |
| script | String | name of the alphabet | False |
| type | String | what kind of language is it? "standard"; "exotic"; "secret" |
False |
| additionalSources | Integer | what additional sources it appears within | False |
| fonts | array of String | addresses for the language's associated fonts | False |
🗄️ Reference Files:
- 🛢️ Requirements Specs (Schemata)
- [[ |🧾 Blank Template]]
- 📖 Sample JSON
- 💾 No other Functional Examples exist
- 📚 Repository of Other Examples
- Reference Tag: (how to link to entries within the
"entries":){@language <name_of_Language>|<json_source>|<optional_display_text>}
- Example:
{@language Dambrathan|SCAG}
{@language Dambrathan|SCAG|and optional link text added with another pipe}
Homebrew Support
Known Issues
- Looks like its perfect... (Did we miss anything?)
- NAME OF THE ISSUE
- Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
- Work Around : Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
FAQ
- Nothing's here (Do you have any suggestions?)
Best Practices
- None as yet (Do you have any suggestions?)
Related Features
Did that answer your question(s)?
If not please check the under Support; Troubleshooting or the Known Issues page for further guidance, or go to the Discord community and leave a comment in the issues channel.
If you enjoy the project, please follow this link to see how you can contribute and help make it even better.
