Skip to content

Issues from translation feedback #1802

@Kebap

Description

@Kebap

Brief summary of issue / Description of requested feature:

While translating, some ideas / feedback were given about the current state of English texts in Mudlet. We need to discuss and solve them in code. Not sure about correct procedure. For reference, I will mention all here.

Reasons for adding feature:

Discussions can happen in crowdin. They should be between translators. If developers need be involved, discussion can move to github. This is where developers reside. As code needs to be adressed, we can link here easier.

Expected result of feature

Issues from translators will be resolved in a timely manner. Any discussions between developers only can happen transparently here.

ideas for how to solve / implement:

Following will be a long numbered list of current issues and discussions which need developers' feedback.

Listing the following items & state:

  • 1. ! %2 invited to %3
  • 2. ! %1 sets mode %2 %3 %4
  • 3. * %1 %2
  • 4. Room Id
  • 5. Click on a line to select or deselect that room number (with the given name if the rooms are named) to add or remove the room from the selection. ...
  • 6. Room ID: %1 (Selected) Position on Map: (%2,%3,%4)
  • 7. Room ID: %1 (%5 Selected) Position on Map: (%2,%3,%4)
  • 8. render time: %1S mO: (%2,%3,%4)
  • 9. Set room area ID
  • 10. Enter the symbol to use for this/these room(s):
  • 11. Enter new roomweight (= travel time) for all selected rooms, mimimum (and default) is 1 and the only current value used is:
  • 12. <0>
  • 13. Multiple tooltips on triggers' filters
  • 14. <html>
  • 15. Need for Plurals-only mudlet_en_US.ts/.qm file.
  • 16. Link to Gitter

Metadata

Metadata

Assignees

No one assigned

    Labels

    i18n & l10ninternationalization and localization

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions