Change Details

The #language-team plans for this fiscal year include work in the areas described below. # 1. Growing small wikis with translation Millions of speakers of less supported languages have limited access to knowledge. They have access to few articles with little coverage. We want to help small wikis grow by: - Encouraging the use of #contenttranslation to create new articles on desktop. - Support the translation of new sections on mobile and desktop to expand existing articles anytime. ## Key interventions and rough schedule **Q1 (Jul-Aug-Sep):** Learn about needs and explore potential solutions. Attract more people to translate on desktop. **Q2 (Oct-Nov-Dec):** Transfer sections to existing articles on desktop Support basic translation on mobile **Q3 (Jan-Feb-Mar):** Transfer sections to existing articles on mobile Transfer articles on mobile **Q4 (Apr-May-Jun):** Expand the basic capabilities to find and translate types of content. ## Metrics and impact Increase the size of the community of translators and the content created/expanded by them in small wikis: - Increase the percentage of new editors that completed their second translation in a month. - Double the number of weekly translations on selected wikis (to create new content or extend existing one). # 2. Comfortable creation of multilingual content We want content such as project documentation, policies, campaigns, reports, and other types of documentation to be available in all languages, but currently making content multilingual makes it hard to work with it. The Translate extension (#mediawiki-extensions-translate) helps with the translation process, but it also adds complexity that discourages users from creating multilingual content. ## Key interventions and rough schedule **Q1 (Jul-Aug-Sep):** Learn about the needs of other Wikimedia Foundation teams Translation project management workflows **Q2 (Oct-Nov-Dec):** Support communication and coordination with translators Reusable language metadata **Q3 (Jan-Feb-Mar):** Support the parsing changes Improve translation quality (1/2) **Q4 (Apr-May-Jun):** Improve translation quality (2/2) Visual editing support of translatable content (Research & Designs)

The #language-team plans for this fiscal year include work in the areas described below. # 1. Growing small wikis with translation Millions of speakers of less supported languages have limited access to knowledge. They have access to few articles with little coverage. We want to help small wikis grow by: - Encouraging the use of #contenttranslation to create new articles on desktop. - Support the translation of new sections on mobile and desktop to expand existing articles anytime. ## Key interventions and rough schedule **Q1 (Jul-Aug-Sep):** Learn about needs and explore potential solutions: - {T225300} Attract more people to translate on desktop. **Q2 (Oct-Nov-Dec):** Transfer sections to existing articles on desktop Support basic translation on mobile **Q3 (Jan-Feb-Mar):** Transfer sections to existing articles on mobile Transfer articles on mobile **Q4 (Apr-May-Jun):** Expand the basic capabilities to find and translate types of content. ## Metrics and impact Increase the size of the community of translators and the content created/expanded by them in small wikis: - Increase the percentage of new editors that completed their second translation in a month. - Double the number of weekly translations on selected wikis (to create new content or extend existing one). # 2. Comfortable creation of multilingual content We want content such as project documentation, policies, campaigns, reports, and other types of documentation to be available in all languages, but currently making content multilingual makes it hard to work with it. The Translate extension (#mediawiki-extensions-translate) helps with the translation process, but it also adds complexity that discourages users from creating multilingual content. ## Key interventions and rough schedule **Q1 (Jul-Aug-Sep):** Learn about the needs of other Wikimedia Foundation teams Translation project management workflows **Q2 (Oct-Nov-Dec):** Support communication and coordination with translators Reusable language metadata **Q3 (Jan-Feb-Mar):** Support the parsing changes Improve translation quality (1/2) **Q4 (Apr-May-Jun):** Improve translation quality (2/2) Visual editing support of translatable content (Research & Designs)

The #language-team plans for this fiscal year include work in the areas described below. # 1. Growing small wikis with translation Millions of speakers of less supported languages have limited access to knowledge. They have access to few articles with little coverage. We want to help small wikis grow by: - Encouraging the use of #contenttranslation to create new articles on desktop. - Support the translation of new sections on mobile and desktop to expand existing articles anytime. ## Key interventions and rough schedule **Q1 (Jul-Aug-Sep):** Learn about needs and explore potential solutions.: - {T225300} Attract more people to translate on desktop. **Q2 (Oct-Nov-Dec):** Transfer sections to existing articles on desktop Support basic translation on mobile **Q3 (Jan-Feb-Mar):** Transfer sections to existing articles on mobile Transfer articles on mobile **Q4 (Apr-May-Jun):** Expand the basic capabilities to find and translate types of content. ## Metrics and impact Increase the size of the community of translators and the content created/expanded by them in small wikis: - Increase the percentage of new editors that completed their second translation in a month. - Double the number of weekly translations on selected wikis (to create new content or extend existing one). # 2. Comfortable creation of multilingual content We want content such as project documentation, policies, campaigns, reports, and other types of documentation to be available in all languages, but currently making content multilingual makes it hard to work with it. The Translate extension (#mediawiki-extensions-translate) helps with the translation process, but it also adds complexity that discourages users from creating multilingual content. ## Key interventions and rough schedule **Q1 (Jul-Aug-Sep):** Learn about the needs of other Wikimedia Foundation teams Translation project management workflows **Q2 (Oct-Nov-Dec):** Support communication and coordination with translators Reusable language metadata **Q3 (Jan-Feb-Mar):** Support the parsing changes Improve translation quality (1/2) **Q4 (Apr-May-Jun):** Improve translation quality (2/2) Visual editing support of translatable content (Research & Designs)