-
-
Notifications
You must be signed in to change notification settings - Fork 957
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
add glossary #3
Comments
nijel
added a commit
that referenced
this issue
Mar 20, 2012
nijel
added a commit
that referenced
this issue
Mar 20, 2012
The basic infrastructure is there, what is missing is way to edit the dictionary and possibly automatic adding of most frequent words. |
Structure should be /dictionary/project/language/, allowing only languages which have translation in given project. |
nijel
added a commit
that referenced
this issue
Mar 30, 2012
nijel
added a commit
that referenced
this issue
Mar 30, 2012
nijel
added a commit
that referenced
this issue
Mar 30, 2012
nijel
added a commit
that referenced
this issue
Mar 30, 2012
Implemented in git. |
ghost
assigned nijel
Jul 12, 2012
nijel
pushed a commit
that referenced
this issue
Jun 7, 2018
…-part, Git (#3) * "Translation-Team", is detailed, dedicated reviewers, local-part, Git * corrected to "Username or email"
Closed
WofWca
referenced
this issue
in WofWca/weblate
May 2, 2022
NE-546: build docker image from local python code
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Each project should have assigned glossary of frequently used terms.
The text was updated successfully, but these errors were encountered: