Java properties Qt Linguist .ts Android string resources Apple OS X strings PHP strings JSON files .Net Resource files Others Weblate’s Web API Notification hooks Exports RSS feeds Changes weblate 2 checks Unchanged translation Starting or trailing newline Starting spaces Trailing space Trailing stop Trailing colon Trailing question Trailing exclamation Trailing ellipsis Format strings Missing plurals glossaries On project page, on Glossaries tab, you can find link Manage all glossaries, where you can start new glossaries or edit existing ones. Once glossary is existing, it will also show up on this tab

Java properties Qt Linguist .ts Android string resources Apple OS X strings PHP strings JSON files .Net Resource files CSV files Others Weblate’s Web API Notification hooks Exports RSS feeds Changes checks Unchanged translation Starting or trailing newline Starting spaces Trailing space Trailing stop Trailing colon Trailing question Trailing exclamation Trailing ellipsis Format strings Missing plurals glossaries On project page, on Glossaries tab, you can find link Manage all glossaries, where you can start new glossaries or edit existing ones. Once glossary is existing, it will also show up on this tab

Java properties Qt Linguist .ts Android string resources Apple OS X strings PHP strings JSON files .Net Resource files CSV files Others Weblate’s Web API Notification hooks Exports RSS feeds Changes checks Unchanged translation Starting or trailing newline Starting spaces Trailing space Trailing stop Trailing colon Trailing question Trailing exclamation Trailing ellipsis Maximum Length Format strings glossaries On project page, on Glossaries tab, you can find link Manage all glossaries, where you can start new glossaries or edit existing ones. Once glossary is existing, it will also show up on this tab

Glossaries tab of each project page, you can find a link that reads Manage all glossaries, wherein you can start new glossaries or edit existing ones. Once a glossary exists, it will also show up in this tab. On strings mistakenly untranslated. Starting or trailing newline Source and translation do not both start (or end) with a newline. Newlines usually appear in source strings for good reason, omissions or problems when the translated text is put to use. Starting spaces Source and translation do not both start with the same number of spaces. A space in the beginning of a string is usually used for indentation

Glossaries tab of each project page, you can find a link that reads Manage all glossaries, wherein you can start new glossaries or edit existing ones. Once a glossary exists, it will also show up in this tab. On strings mistakenly untranslated. Starting or trailing newline Source and translation do not both start (or end) with a newline. Newlines usually appear in source strings for good reason, omissions or problems when the translated text is put to use. Starting spaces Source and translation do not both start with the same number of spaces. A space in the beginning of a string is usually used for indentation

a language is added to a component (to do this, select a component, its Translation tab and click Start new translation). Once a glossary exists, it will also show up in this list. Glossaries are shared strings mistakenly untranslated. Starting or trailing newline Source and translation do not both start (or end) with a newline. Newlines usually appear in source strings for good reason, omissions or problems when the translated text is put to use. Starting spaces Source and translation do not both start with the same number of spaces. A space in the beginning of a string is usually used for indentation

a language is added to a component (to do this, select a component, its Translation tab and click Start new translation). Once a glossary exists, it will also show up in this list. Glossaries are shared strings mistakenly untranslated. Starting or trailing newline Source and translation do not both start (or end) with a newline. Newlines usually appear in source strings for good reason, omissions or problems when the translated text is put to use. Starting spaces Source and translation do not both start with the same number of spaces. A space in the beginning of a string is usually used for indentation

a language is added to a component (to do this, select a component, its Translation tab and click Start new translation). Once a glossary exists, it will also show up in this list. Glossaries are shared strings mistakenly untranslated. Starting or trailing newline Source and translation do not both start (or end) with a newline. Newlines usually appear in source strings for good reason, omissions or problems when the translated text is put to use. Starting spaces Source and translation do not both start with the same number of spaces. A space in the beginning of a string is usually used for indentation

a language is added to a component (to do this, select a component, its Translation tab and click Start new translation). Once a glossary exists, it will also show up in this list. Glossaries are shared strings mistakenly untranslated. Starting or trailing newline Source and translation do not both start (or end) with a newline. Newlines usually appear in source strings for good reason, omissions or problems when the translated text is put to use. Starting spaces Source and translation do not both start with the same number of spaces. A space in the beginning of a string is usually used for indentation

a language is added to a component (to do this, select a component, its Translation tab and click Start new translation). Once a glossary exists, it will also show up in this list. Glossaries are shared strings mistakenly untranslated. Starting or trailing newline Source and translation do not both start (or end) with a newline. Newlines usually appear in source strings for good reason, omissions or problems when the translated text is put to use. Starting spaces Source and translation do not both start with the same number of spaces. A space in the beginning of a string is usually used for indentation