Translations for fnbr.co
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
test Compare object values too Jan 8, 2019
CNAME Create CNAME Jan 8, 2019
README.md Updated languages.json Jan 9, 2019
cy.json Fixed issue 4 in reference with #55 (#62) Jan 13, 2019
da.json Update da.json (#67) Jan 15, 2019
de.json Update translations (de.json) (#73) Jan 19, 2019
en.json Fix typo Jan 26, 2019
es.json Revert part of #75 Jan 26, 2019
fi.json Update fi.json (#78) Feb 8, 2019
fr.json
hu.json
it.json Update it.json (#60) Jan 13, 2019
languages.json name change (#81) Feb 21, 2019
nl.json Changed some lines in nl.json (29-01-19) (#77) Jan 30, 2019
no.json Fix not all nav items being lowercase (multiple languages) (#58) Jan 12, 2019
pt-BR.json Fix dateFormat for hu and pt-BR Jan 10, 2019
ro.json
sk.json Update sk.json (#65) Jan 23, 2019
sv.json Fix my mistake in translations Jan 13, 2019
tr.json dateFormat Fix (#76) Jan 30, 2019
vi.json

README.md

fnbr.co translations

UI Translations for fnbr.co. As of now it is not planned to translate all Fortnite cosmetics due to volume.

How can I contribute?

Create a pull request with your changes, language files are named [two-letter code].json, you can find a list of two letter language codes here.
For example en.json for English, es.json for Spanish, pt.json for Portuguese and so on.

The en.json will always be updated with the latest text to translate, so use that as a base and just translate what you can of your language!
If a string does not exist in the file it will default to English.

There are a few things to remember:

  • Don't use Google Translate or other online translation tools, as these lack context and can come up with some very strange results.
  • Text inside square brackets (that's [ and ]) such as [language] needs to remain in English (unless it is followed by ( and ) making it a link - see below), as it is normally replaced when the page is loaded with dyanmic data such as the date.
  • Links are done similar to markdown, [text here](https://example.com) the closing square bracket and first round bracket need to stay together.
  • At the top of the file where the name attribute is, this should be the name of the language in that language, so that it is easily recognisable for speakers.
  • Underneath that, also put name-en, which is the name of the language in English. This is optional.
  • thForDate means if st, nd, rd and th should be put after the date. For example in English it is used like this: January 8th 2019.

In your pull request tell us your Discord name and discriminator and we will give you a Translator role on our Discord, make your fnbr.co account have no adverts and credit you as a thank you.

Links and formatting

Links are in a similar format to Markdown, it can also have 'modifiers' by using | to separate them.
If the text should be a link, the url must be the first modifier in use. If the text is not a link the modifiers can be in any order.

Modifier Description Options
URL A HTTP/HTTPS link
newtab Makes the link open in a new tab true
class Adds CSS classes Any CSS class
tooltip Adds the title and alt attributes Text to show on hover
bold Makes the text bold true

For example:

  • [new tab link](https://fnbr.co|newtab=true) uses the newtab modifier for the link.
  • [bold text](bold=true) uses just the bold modifier and is not a link.
  • [bold new tab link](https://fnbr.co|newtab=true|bold=true) uses both the bold and newtab modifiers for the link