Hi Stephen, Understood, thank you.
While reading the Core template code I noticed that adding $language to the URL will require two small changes there as well: TemplateManager.get() will need to return None instead of '' on a 404 so the fallback chain is not cut short, and TemplateLoader.get() will need a language retry loop at each context level. I am planning to include these Core changes in scope alongside the Postorius UI work. Thanks, Sambodhi On Tue, Mar 24, 2026 at 4:58 PM Stephen J. Turnbull <[email protected]> wrote: > > Sambodhi Roy via Mailman-Developers writes: > > > Here are a few questions I have: > > Please try to answer your questions yourself. You should still ask if > you are not sure, but it's useful to know how you think. > > > 1. Should the preferred language -> English fallback happen inside > > Postorius, or should core handle it? > > Anything that core can do should not be implemented in another > component. We do not want to privilege Postorius or HyperKitty over > third-party implementations of the management UI or archiver. > > > 2. Existing templates have an empty language field. > > By "existing" do you mean those distributed with Mailman? What does > the customization page in Postorius do? > > > Should empty mean English/default, or language-agnostic? This > > affects how we handle the unique constraint when new > > language-specific records are added alongside old ones. > > I suspect that current practice on most non-English sites is just to > edit the distributed templates (if present) to use the site's default > language. So probably that needs to be "language agnostic" in > practice. > > > 3. A registered URL silently overrides any filesystem template the > > moment it is saved. Should the editor warn the admin when this > > is about to happen? > > I don't think we should change this. > > > 4. Should the new dedicated footer editor remove footers from the > > generic template dropdown to avoid confusion, or keep both > > working in parallel? > > I don't understand what you mean. My understanding was that the > existing editor in Postorius would grow a language tag field, it would > probably be a two letter ISO 639 language code, possibly combined with > an ISO 3166 region code (eg, I'm pretty sure we have both pt (pt_PT) > and pt_BR, for example). This tag would be stored with the template > wherever it was stored. > > Steve > > > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source https://www.siriusopensource.com/ > Software systems consulting in Europe, North America, and Japan _______________________________________________ Mailman-Developers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
