Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: start implementing Ravkav GTFS support #772

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

micolous
Copy link
Collaborator

Alternative for #751

/* A map of language codes (two-letter ISO code) to language ID, local to
* this file, used for `Names.other` and `Names.other_short`.
*/
map<string, uint32> languages = 7;
Copy link
Collaborator

@phcoder phcoder Nov 1, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need more than just id. I think it needs to map to a message containing ID but also e.g. which is primary local language. E.g. on English system if the checkbox "show local language" is on and we scan Rav-Kav then Hebrew will be the language to show. Other attributes might include tts hints. Hebrew omits vowels and I can imagine having 2 IDs for Hebrew: first one is used for display purposes (E.g for Haifa: חיפה‎) and second one with vowels (חֵיפָה‎) is retrieved but not shown and instead is stuffed into tts hints. For this we need a second field in language message which species the key for tts hints. Obviously tts hints is for the future but let's the design be expandable for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants