supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Bjornsdottirs, \"Ellenor\"" <>
Subject: Re: Support i18n
Date: Wed, 21 Dec 2022 13:25:46 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

it would be achingly pointless.

most interfaces of relevance to l10n & i18n are machinable, and so a script could tokenize them and provide that info.

I would be curious about S6 and current plans as they relate to interface stability for the purpose of localized wrapping scripts, though.

On 21 December 2022 13:22:33 UTC, wrote:
>Hello. Are you planning to add i18n support to runit?

Ellenor (et al) Bjornsdottir (she)
third-rate MTA dev ;)

      reply	other threads:[~2022-12-21 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-12-21 13:22 ` tomazs
2022-12-21 13:25   ` Bjornsdottirs, "Ellenor" [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).