Translation status

652 Strings
99%
Browse Translate
5,356 Words
93%
34,086 Characters
93%

Strings status

Strings Words Characters
652 5,356 34,086
All strings Browse Translate Zen
648 5,036 31,977
Translated strings Browse Translate Zen
4 320 2,109
Unfinished strings Browse Translate Zen
4 320 2,109
Untranslated strings Browse Translate Zen
2 6 33
Strings with any failing checks Browse Translate Zen
2 6 33
Translated strings with any failing checks Browse Translate Zen
3 3 31
Translated strings with dismissed checks Browse Translate Zen
2 6 33
Failing check: Multiple capitals Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Django-mailman3 GPL-3.0-or-later
HyperKitty GPL-3.0-or-later 99% 1 1 8 1 1
Mailman Core GPL-3.0-or-later 36% 265 4,810 31,573 265
Browse all components

Summary

Project website list.org
Instructions for translators

Mailing list for translators: <mailman-developers@python.org
Project maintainers2 User avatar maxkingUser avatar msapiro
Translation license GNU General Public License v3.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://gitlab.com/mailman/postorius.git
Repository branch master
Last remote commit Merge branch 'weblate-gnu-mailman-postorius' into 'master' 7b771de7
User avatar msapiro authored 01/28/2026
Last commit in Weblate Merge branch 'weblate-gnu-mailman-postorius' into 'master' 7b771de7
User avatar msapiro authored 01/28/2026
Weblate repository https://hosted.weblate.org/git/gnu-mailman/postorius/
File mask src/postorius/locale/*/LC_MESSAGES/django.po
Translation file Download src/postorius/locale/sq/LC_MESSAGES/django.po
Last change Oct. 10, 2025, 8:07 p.m.
Last change made by Background commit
Language Albanian
Language code sq
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 6,798,943
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
01/25/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 652 5,356 34,086
Translated 99% 648 94% 5,036 93% 31,977
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 2 1% 6 1% 33
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 4 5% 320 6% 2,109
Last 12 months Previous

Activity in last 12 months

12 changes 11 changes 23 changes 0 changes 0 changes 13 changes 9 changes 2 changes 6 changes 10 changes 0 changes 0 changes 0 changes 0 changes 4 changes 0 changes 2 changes 2 changes 2 changes 0 changes 20 changes 0 changes 0 changes 0 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

5,356
Hosted words
652
Hosted strings
99%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+99%
—
Contributors
—
User avatar weblate:commit

Changes committed
Changes committed 10/10/2025
User avatar Besnik_b

Translation changed
Where are replies to list messages directed? No Munging is strongly recommended for most mailing lists.
This option controls what Mailman does to the Reply-To: header in messages flowing through this mailing list. When set to No Munging, no Reply-To: header is added by Mailman, although if one is present in the original message, it may be stripped depending on First strip Reply-To. Setting this value to Reply to List or either of the Explicit Reply settings causes Mailman to insert a specific Reply-To: header in all messages, either adding to or overriding the header in the original message depending on First Strip Reply-To. Explicit Reply inserts the value of Explicit reply-to_address, Reply goes to list inserts the list posting address. Explicit Reply-to set; no Cc added is useful forannounce-only lists where you want to avoid someone replying to the list address. There are many reasons not to introduce or override the Reply-To: header. One is that some posters depend on their own Reply-To: settings to convey their valid return address. Another is that modifying Reply-To: makes it much more difficult to send private replies. See <a href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To' Munging Considered Harmful</a> for a general discussion of this issue. See <a href="http://marc.merlins.org/netrants/reply-to-useful.html">`Reply-To' Munging Considered Useful</a> for a dissenting opinion. Some mailing lists have restricted posting privileges, with a parallel list devoted to discussions. Examples are `patches' or `checkin' lists, where software changes are posted by a revision control system, but discussion about the changes occurs on a developers mailing list. To support these types of mailing lists, select Explicit Reply and set the Reply-To: address option to point to the parallel list.
Për ku drejtohen përgjigjet ndaj mesazheve të listës? Për shumicën e listave të postimeve këshillohet me forcë “Pa Rishkrim Kryesh”.
Kjo mundësi kontrollon se ç’bën Mailman-i me kryet <em>Reply-To:</em> te mesazhe që rrjedhin nëpër këtë listë postimesh. Kur caktohet si “Pa Rishkrim Kryesh”, s’shtohet ndonjë krye <em>Reply-To:</em> nga Mailman-i, edhe pse, nëse te mesazhi origjinal ka të pranishme një të tillë, ajo nuk hiqet. Caktimi i kësaj vlere si “Përgjigjuni te Lista”, “Përgjigje Eksplicite”, apo “Vetëm Përgjigje” e bën Mailman-in të futë një krye specifike <em>Reply-To:</em> në krejt mesazhet, duke anashkaluar kryet në mesazhin origjinal, në qoftë e nevojshme (“Përgjigje Eksplicite” fut vlerën e <em>reply_to_address</em>). “U caktua krye eksplicite <em>Reply-to</em>; s’u shtua Cc” është e dobishme për lista vetëm për njoftime, kur doni të shmangni dikë nga përgjigja te adresa e listës. Ka plot arsye për të mos futur ose për të mos anashkaluar kryet <em>Reply-To:</em>. Njëra është se disa sisteme postimi varen nga rregullimet e tyre për <em>Reply-To:</em> për të përcjellë adresën e tyre të vlefshme të kthimit.Një tjetër është se ndryshimi i <em>Reply-To:</em> e bën shumë më të vështirë dërgimin e përgjigjeve private. Për një diskutim në përgjithësi të kësaj çështjeje, shihni <a href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To' Munging Considered Harmful</a>. Për opinione që s’pajtohen me këtë, shihni <a href="http://marc.merlins.org/netrants/reply-to-useful.html">`Reply-To' Munging Considered Useful</a>. Disa lista postimesh kanë privilegje të kufizuara postimi, me një listë paralele kushtuar diskutimeve. Shembuj janë lista `patches' ose `checkin', ku ndryshimet e software-it postohen sipas një sistemi versioni kontrollesh, ndërsa diskutimi rreth ndryshimeve ndodh te një listë postimesh për zhvilluesit. Për mbulim të këtyre lloje listash, përzgjidhni “Përgjigje Eksplicite” dhe caktojeni mundësinë për adresën <em>Reply-To:</em> të shpjerë te lista paralele.
10/09/2025
User avatar None

Resource updated
The “src/postorius/locale/sq/LC_MESSAGES/django.po” file was changed. 06/24/2025
User avatar None

String added in the repository
Where are replies to list messages directed? No Munging is strongly recommended for most mailing lists.
This option controls what Mailman does to the Reply-To: header in messages flowing through this mailing list. When set to No Munging, no Reply-To: header is added by Mailman, although if one is present in the original message, it may be stripped depending on First strip Reply-To. Setting this value to Reply to List or either of the Explicit Reply settings causes Mailman to insert a specific Reply-To: header in all messages, either adding to or overriding the header in the original message depending on First Strip Reply-To. Explicit Reply inserts the value of Explicit reply-to_address, Reply goes to list inserts the list posting address. Explicit Reply-to set; no Cc added is useful forannounce-only lists where you want to avoid someone replying to the list address. There are many reasons not to introduce or override the Reply-To: header. One is that some posters depend on their own Reply-To: settings to convey their valid return address. Another is that modifying Reply-To: makes it much more difficult to send private replies. See <a href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To' Munging Considered Harmful</a> for a general discussion of this issue. See <a href="http://marc.merlins.org/netrants/reply-to-useful.html">`Reply-To' Munging Considered Useful</a> for a dissenting opinion. Some mailing lists have restricted posting privileges, with a parallel list devoted to discussions. Examples are `patches' or `checkin' lists, where software changes are posted by a revision control system, but discussion about the changes occurs on a developers mailing list. To support these types of mailing lists, select Explicit Reply and set the Reply-To: address option to point to the parallel list.
Për ku drejtohen përgjigjet ndaj mesazheve të listës? Për shumicën e listave të postimeve këshillohet me forcë “Pa Rishkrim Kryesh”.
Kjo mundësi kontrollon se ç’bën Mailman-i me kryet <em>Reply-To:</em> te mesazhe që rrjedhin nëpër këtë listë postimesh. Kur caktohet si “Pa Rishkrim Kryesh”, s’shtohet ndonjë krye <em>Reply-To:</em> nga Mailman-i, edhe pse, nëse te mesazhi origjinal ka të pranishme një të tillë, ajo nuk hiqet. Caktimi i kësaj vlere si “Përgjigjuni te Lista”, “Përgjigje Eksplicite”, apo “Vetëm Përgjigje” e bën Mailman-in të futë një krye specifike <em>Reply-To:</em> në krejt mesazhet, duke anashkaluar kryet në mesazhin origjinal, në qoftë e nevojshme (“Përgjigje Eksplicite” fut vlerën e <em>reply_to_address</em>). “U caktua krye eksplicite <em>Reply-to</em>; s’u shtua Cc” është e dobishme për lista vetëm për njoftime, kur doni të shmangni dikë nga përgjigja te adresa e listës. Ka plot arsye për të mos futur ose për të mos anashkaluar kryet <em>Reply-To:</em>. Njëra është se disa sisteme postimi varen nga rregullimet e tyre për <em>Reply-To:</em> për të përcjellë adresën e tyre të vlefshme të kthimit.Një tjetër është se ndryshimi i <em>Reply-To:</em> e bën shumë më të vështirë dërgimin e përgjigjeve private. Për një diskutim në përgjithësi të kësaj çështjeje, shihni <a href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To' Munging Considered Harmful</a>. Për opinione që s’pajtohen me këtë, shihni <a href="http://marc.merlins.org/netrants/reply-to-useful.html">`Reply-To' Munging Considered Useful</a>. Disa lista postimesh kanë privilegje të kufizuara postimi, me një listë paralele kushtuar diskutimeve. Shembuj janë lista `patches' ose `checkin', ku ndryshimet e software-it postohen sipas një sistemi versioni kontrollesh, ndërsa diskutimi rreth ndryshimeve ndodh te një listë postimesh për zhvilluesit. Për mbulim të këtyre lloje listash, përzgjidhni “Përgjigje Eksplicite” dhe caktojeni mundësinë për adresën <em>Reply-To:</em> të shpjerë te lista paralele.
06/24/2025
User avatar None

Source string changed
Where are replies to list messages directed? No Munging is strongly recommended for most mailing lists.
This option controls what Mailman does to the Reply-To: header in messages flowing through this mailing list. When set to No Munging, no Reply-To: header is added by Mailman, although if one is present in the original message, it is not strippedmay be stripped depending on First strip Reply-To. Setting this value to either Reply to List, Explicit Reply, or Reply Only or either of the Explicit Reply settings causes Mailman to insert a specific Reply-To: header in all messages, either adding to or overriding the header in the original message if necessary (depending on First Strip Reply-To. Explicit Reply inserts the value of reply_to_Explicit reply-to_address, Reply goes to list inserts the list posting address). Explicit Reply-to set; no Cc added is useful forannounce-only lists where you want to avoid someone replying to the list address. There are many reasons not to introduce or override the Reply-To: header. One is that some posters depend on their own Reply-To: settings to convey their valid return address. Another is that modifying Reply-To: makes it much more difficult to send private replies. See <a href="http://marc.merlins.org/netrants/reply-to-harmful.html">`Reply-To' Munging Considered Harmful</a> for a general discussion of this issue. See <a href="http://marc.merlins.org/netrants/reply-to-useful.html">`Reply-To' Munging Considered Useful</a> for a dissenting opinion. Some mailing lists have restricted posting privileges, with a parallel list devoted to discussions. Examples are `patches' or `checkin' lists, where software changes are posted by a revision control system, but discussion about the changes occurs on a developers mailing list. To support these types of mailing lists, select Explicit Reply and set the Reply-To: address option to point to the parallel list.
06/24/2025
User avatar None

String updated in the repository
Should any existing Reply-To: header found in the original message be stripped? If so, this will be done regardless of whether an explicit Reply-To: header is added by Mailman or not.
A duhet hequr çfarëdo krye Reply-To: ekzistuese e gjetur në mesazhin origjinal? Nëse po, kjo do të kryhet pavarësisht nëse shtohet apo jo shprehimisht një krye Reply-To: nga Mailman-i.
06/24/2025
User avatar None

Changes committed
Changes committed 06/10/2025
User avatar Besnik_b

Translation changed
Should any existing Reply-To: header found in the original message be stripped? If so, this will be done regardless of whether an explicit Reply-To: header is added by Mailman or not.
A duhet hequr çfarëdo krye Reply-To: ekzistuese e gjetur në mesazhin origjinal? Nëse po, kjo do të kryhet pavarësisht nëse shtohet apo jo shprehimisht një krye Reply-To: nga Mailman-i.
06/09/2025
User avatar None

Resource updated
The “src/postorius/locale/sq/LC_MESSAGES/django.po” file was changed. 06/09/2025
User avatar None

String added in the repository
Should any existing Reply-To: header found in the original message be stripped? If so, this will be done regardless of whether an explicit Reply-To: header is added by Mailman or not.
A duhet hequr çfarëdo krye Reply-To: ekzistuese e gjetur në mesazhin origjinal? Nëse po, kjo do të kryhet pavarësisht nëse shtohet apo jo shprehimisht një krye Reply-To: nga Mailman-i.
06/09/2025
Browse all translation changes