Considerations for adding multiple language support (as per the discussions started in issue #8)
The NetrunnerDB API served different languages with the "_locale=xx" parameter.
Additional untranslated "[x]_code" fields were supplied alongside the translated fields (e.g. "faction":"Kriminelle","faction_code":"criminal"), allowing applications to process the data without knowing the translations. These fields were supplied for type, subtype, faction, set and side.
As there is no current official source of translated data the translations will probably need to be community driven.
Whilst Multi Language support is not a priority it may be worth incorporating the additional fields (or coming up with an alternative) into the API structure early so any Apps in development can be written with respect for future language support.
Considerations for adding multiple language support (as per the discussions started in issue #8)
The NetrunnerDB API served different languages with the "_locale=xx" parameter.
Additional untranslated "[x]_code" fields were supplied alongside the translated fields (e.g. "faction":"Kriminelle","faction_code":"criminal"), allowing applications to process the data without knowing the translations. These fields were supplied for type, subtype, faction, set and side.
As there is no current official source of translated data the translations will probably need to be community driven.
Whilst Multi Language support is not a priority it may be worth incorporating the additional fields (or coming up with an alternative) into the API structure early so any Apps in development can be written with respect for future language support.