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

Improve Translator documentation around NodeNorm/NameRes/Babel #148

Open
3 of 5 tasks
gaurav opened this issue Jun 6, 2023 · 0 comments · May be fixed by #292
Open
3 of 5 tasks

Improve Translator documentation around NodeNorm/NameRes/Babel #148

gaurav opened this issue Jun 6, 2023 · 0 comments · May be fixed by #292

Comments

@gaurav
Copy link
Collaborator

gaurav commented Jun 6, 2023

In terms of potentially handing over Babel/NodeNorm/NameRes to another team, here is everything we need to document:

In addition, an FAQ with some basic Translator-facing information will be useful, like:

  • I found two identifiers that refer to the same concept. What should I do?
  • I can't find an identifier for a concept I'm want to represent in Translator. What should I do?
  • I want to add a new source of identifiers to Translator. What should I do?
  • I found an incorrect name in NodeNorm/NameRes. Where should I report it?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant