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

Assuming brackets to indicate hearing-impaired elements should be optional (e.g. round ones can also reflect other intentions) #345

Open
davidgaryesp opened this issue Jan 20, 2025 · 1 comment

Comments

@davidgaryesp
Copy link

In subtitles containing any square or round bracket-pairs (in any position, whether empty or not), Tero appears to assume that they indicate the presence of "Hearing impaired" elements. But these are merely stylistic conventions, hence (AFAICT) assuming them to be firm indicators of such types of element is arguably over-interpretation. They (especially round brackets) can also apply to other intentions. In such instances, the "Hearing impaired" icon (in entries in List mode) is misleading and distracting.

Describe the solution you'd like

  • Add a convention-customization option for round brackets/parentheses to not be interpreted and/or indicated (e.g. as icons in the list) as "Hearing impaired".
  • Preferably do the same for square brackets.

Describe alternatives you've considered
Ignore the "Hearing impaired" icons. But they are "clutter" to "quick scanning by eye".

Additional context
I understand that, "in the wild":

  • It is only square brackets that are de facto stylistic indicators of non-speech sounds - which I imagine correspond to "Hearing impaired" in Tero
  • Round brackets can be / are (in general) used for several types of speech-related purpose - such as short asides/tangents and for corrections/additions to expressed information (e.g. immediately following verbatim incorrect/incomplete speech).
@chenlung
Copy link
Collaborator

Sometimes context is provided in brackets for a translation, so I think I would agree with customisation.

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

No branches or pull requests

2 participants