starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Transifex: Please utilize Glossaries for consistent translations #9133

New Issue
Closed
opened 2025-12-29 20:46:05 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:46:05 +01:00
Owner
Copy Link

Originally created by @stavr666 on GitHub (Jan 23, 2024).

Language

Russian

ISO 639-1 code

ru

Volunteer

Yes

Comments

I was given access to project and find out, that in current state all phrases is translated without clean context-relations (so, translators not knowing, what exactly phrase referring to) AND without any sort of glossary.

It's not my job, but I happen to translate some texts, so definitely know, that there will be too much unrelated results, when translator does not know contest. And much-much more inconsistencies, IF there is not any king of agreement on terminology and naming before translation started. The last part is most important for technical texts, in which use of words often differs from their everyday meaning.

Add editable glossary, please, so same word can have same meaning across all translation.

Originally created by @stavr666 on GitHub (Jan 23, 2024). ### Language Russian ### ISO 639-1 code ru ### Volunteer Yes ### Comments I was given access to project and find out, that in current state all phrases is translated without clean context-relations (so, translators not knowing, what exactly phrase referring to) AND without any sort of glossary. It's not my job, but I happen to translate some texts, so definitely know, that there will be too much unrelated results, when translator does not know contest. And much-much more inconsistencies, IF there is not any king of agreement on terminology and naming before translation started. The last part is most important for technical texts, in which use of words often differs from their everyday meaning. Add editable glossary, please, so same word can have same meaning across all translation.
adam added the type: translation label 2025-12-29 20:46:05 +01:00
adam closed this issue 2025-12-29 20:46:06 +01:00
adam commented 2025-12-29 20:46:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 23, 2024):

Occurrences of each string are noted in the Transifex platform. Where the meaning of a term is unclear, translators should refer to the location(s) of the text within the application for context. Additionally, we pass explicit context along with the original string in cases where a word may have multiple meanings.

Transifex does provide a glossary feature that allows you to define terms if needed, but I'd expect most translators to already be familiar with the majority of terminology used in NetBox.

@jeremystretch commented on GitHub (Jan 23, 2024): Occurrences of each string are noted in the Transifex platform. Where the meaning of a term is unclear, translators should refer to the location(s) of the text within the application for context. Additionally, we pass explicit context along with the original string in cases where a word may have multiple meanings. Transifex does provide a [glossary feature](https://help.transifex.com/en/articles/6229127-understanding-glossaries) that allows you to define terms if needed, but I'd expect most translators to already be familiar with the majority of terminology used in NetBox.
adam commented 2025-12-29 20:46:07 +01:00
Author
Owner
Copy Link

@stavr666 commented on GitHub (Jan 24, 2024):

I'd expect most translators to already be familiar with the majority of terminology used in NetBox.

Doesn't look real when you see something like this:
image

And whole translation that inconsistent, it's not a rare example.

@stavr666 commented on GitHub (Jan 24, 2024): > I'd expect most translators to already be familiar with the majority of terminology used in NetBox. Doesn't look real when you see something like this: ![image](https://github.com/netbox-community/netbox/assets/84839985/affa71d8-500b-4878-b670-922952bf30a1) And whole translation that inconsistent, it's not a rare example.
adam commented 2025-12-29 20:46:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 24, 2024):

The initial translations are machine-generated to save time. Your role as a translator is to review and correct them as needed.

@jeremystretch commented on GitHub (Jan 24, 2024): The initial translations are machine-generated to save time. Your role as a translator is to review and correct them as needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: translation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9133
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?