Skip to content

Conversation

mokagio
Copy link
Contributor

@mokagio mokagio commented Mar 11, 2021

Trimming too long keywords client side is the wrong solution to the problem of having keywords that are too long.

Because keywords change sporadically, it's much better to edit the localization source on the GlotPress end.

And even better long term fix would be to add a character limit to GlotPress. I don't know how to do that know but I'll get in touch with folks that might help with that.

See discussion at #1201 (comment)

I'd like to leave this as a draft until the matter is addressed at the root. See pxLjZ-6mD. Just in case I need to trim them again when it comes time for the next submission 🙉

Test

No test required.

Review

Only one developer required to review these changes, but anyone can perform the review.

Release

These changes do not require release notes.

Trimming too long keywords client side is the wrong solution to the
problem of having keywords that are too long.

Because keywords change sporadically, it's much better to edit the
localization source on the GlotPress end.

And even better long term fix would be to add a character limit to
GlotPress. I don't know how to do that know but I'll get in touch with
folks that might help with that.

See discussion at
#1201 (comment)
@mokagio mokagio added this to the 4.34 milestone Mar 11, 2021
@mokagio mokagio added the tooling Related to anything that supports the building & maintaining of the project. label Mar 11, 2021
@mokagio mokagio modified the milestones: 4.34, Future Mar 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling Related to anything that supports the building & maintaining of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant