Confirmed users
950
edits
Websites/Snippets/Rewrite: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 25: | Line 25: | ||
* Run XML validation and escaping on all snippets to avoid issues with invalid XML breaking about:home. | * Run XML validation and escaping on all snippets to avoid issues with invalid XML breaking about:home. | ||
* Provide a good way for non-admins to see what snippets are currently active. | * Provide a good way for non-admins to see what snippets are currently active. | ||
= L10n App = | |||
One of the major components of the rewrite will be a user-facing localization app. Users will be able to log in and suggest translations, and certain users will have permission to log in to a special admin interface that lets them see suggested translations and choose which one is best, or add their own instead. | |||
== Users == | |||
* '''Admin''' - Creates snippets via the admin interface. | |||
* '''Approved Localizer''' - Controls which string is chosen as the accepted translation. | |||
* '''Community Localizer''' - Can suggest possible translations for a string. | |||
* '''QA''' - Can double-check and make/suggest corrections to an accepted translation (only a few large locales have this). | |||
== Stories == | |||
* As an '''Admin''', I can: | |||
** See how many locales have completed translating a snippet. | |||
** Mark a snippet as not available for localization. | |||
* As an '''Approved Localizer''', I can: | |||
** See a list of strings to translate and can filter it by locale and whether it has an accepted translation. | |||
** See a list of suggestions for an individual string and can choose one as the accepted translation, or fill in my own string. | |||
** Preview what a snippet would look like with a certain string. | |||
** Save an approved translation for use in multiple locales (single translation for all es-* locales, for example). | |||
* As a '''Community Localizer''', I can: | |||
** See a list of strings to translate and can filter it by locale and whether it has an accepted translation. | |||
** Suggest a translation for a string and see what my previous suggestion was. | |||
** Preview what a snippet would look like with a certain string. | |||
** Receive notifications when new strings are available for translation. | |||
** Access some sort've data about snippets via JSON. | |||
** View the translation interface in another language besides English. | |||
* As a '''QA''', I can: | |||
** Review the accepted translation for a string and make a correction (suggest a correction?) | |||
** Preview what a snippet would look like with a certain string. | |||
== Open Questions == | |||
* Do L10n QAs need anything more than a read-only view of accepted translations? Could we have them use the public interface for localizers and just offer useful filters? | |||
* When should a string be put out for translation? | |||
** Suggestion: If the snippet is enabled, the strings are available for translation unless it is past the published_end date. | |||
*** Most snippets that don't have a published_end date are long-term snippets that don't need an end date, thus there shouldn't be many strings that are up for translations but not used. | |||
* Do admins need the ability to select priority locales? | |||
** How would localizers be notified that certain snippets are a high-priority? | |||
** Suggestion: Leave this for a later iteration. | |||
* Is the need for a JSON API just for seeing what strings are available for translation, or do we want more, like a way to pull the translations out of the system via the API? | |||