Add a technical "jargon" po translation file for IRC jargon we don't want to translate literally. #852

New Issue

2026-10-05T04:48:38+02:00

adam commented

2026-10-05 04:48:38 +02:00

Some technical IRC jargon makes no sense, or is too confusing, to translate.

Consider the folowing example:

en:

        <source>{1} {2} voiced {3} on {4}</source>
        <source>{1} {2} devoiced {3} on {4}</source>

nl:

        <target state="translated">{1} {2} geeft stem aan {3} op {4}</target>
        <target state="translated">{1} {2} neemt stem van {3} op {4}</target>

This feels closer to translating to "Has removed the vocal cords from {3}", or something to do with voting rights.

Similar ones are e.g. "wildcard", "op", ..

The main thing is that if ZNC considers something a "stem", and your local, non translated IRC client considers it a voice, you will have trouble laying the connection and it will be flat out confusing.

Some technical IRC jargon makes no sense, or is too confusing, to translate. Consider the folowing example: en: ``` <source>{1} {2} voiced {3} on {4}</source> <source>{1} {2} devoiced {3} on {4}</source> ``` nl: ``` <target state="translated">{1} {2} geeft stem aan {3} op {4}</target> <target state="translated">{1} {2} neemt stem van {3} op {4}</target> ``` This feels closer to translating to `"Has removed the vocal cords from {3}"`, or something to do with voting rights. Similar ones are e.g. "wildcard", "op", .. The main thing is that if ZNC considers something a "stem", and your local, non translated IRC client considers it a voice, you will have trouble laying the connection and it will be flat out confusing.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#852