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

Design Principle: Developer Control vs. Localizer Control #61

Closed
stasm opened this issue Mar 2, 2020 · 2 comments
Closed

Design Principle: Developer Control vs. Localizer Control #61

stasm opened this issue Mar 2, 2020 · 2 comments
Labels
design Design principles, decisions resolve-candidate This issue appears to have been answered or resolved, and may be closed soon.

Comments

@stasm
Copy link
Collaborator

stasm commented Mar 2, 2020

A dedicated issue for discussing one of the design dimensions proposed in #50.

Developer Control vs. Localizer Control

How much logic do we want localizers to handle? The more control they have, the more expressive translations they can build, at the cost of increased complexity.

Related Issues: #21

@stasm stasm mentioned this issue Mar 2, 2020
@Fleker
Copy link

Fleker commented Mar 2, 2020

I would think that the best approach is giving the localizers the discretion to make the best decisions. While it may end up being additional complexity, it would result in higher-quality translations.

@mihnita mihnita added the design Design principles, decisions label Sep 24, 2020
@aphillips aphillips added the resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. label Aug 19, 2023
@aphillips
Copy link
Member

Appears to be done in goals?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Design principles, decisions resolve-candidate This issue appears to have been answered or resolved, and may be closed soon.
Projects
None yet
Development

No branches or pull requests

4 participants