Re: using whiptail and translated strings from arbitrary scripts

2016-05-04 Thread Osamu Aoki
Hi, On Wed, Apr 27, 2016 at 02:29:19PM +, Bas Wijnen wrote: > Debian translators just translate packaging texts. Everything else is done by > upstream (which can be the same people, but it is not organized by Debian > AFAIK). I am not sure but my impression is that the i18n team seems to tra

Re: using whiptail and translated strings from arbitrary scripts

2016-05-04 Thread Osamu Aoki
Hi, On Wed, Apr 27, 2016 at 02:28:22PM +0200, Daniel Pocock wrote: > > > On 27/04/16 14:00, Antonio Terceiro wrote: > > On Tue, Apr 26, 2016 at 09:32:02PM +0200, Daniel Pocock wrote: > >> > >> It is well documented how developers should create po files for > >> i18n support in their debconf con

Re: using whiptail and translated strings from arbitrary scripts

2016-04-27 Thread Daniel Pocock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 27/04/16 16:29, Bas Wijnen wrote: > On Wed, Apr 27, 2016 at 02:28:22PM +0200, Daniel Pocock wrote: >> If I use this method, can the strings be translated easily by >> the Debian translators just like the strings for >> po-debconf/maintainer scri

Re: using whiptail and translated strings from arbitrary scripts

2016-04-27 Thread Bas Wijnen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Apr 27, 2016 at 02:28:22PM +0200, Daniel Pocock wrote: > If I use this method, can the strings be translated easily by the > Debian translators just like the strings for po-debconf/maintainer > scripts? > > Or is there some additional Debian-s

Re: using whiptail and translated strings from arbitrary scripts

2016-04-27 Thread Daniel Pocock
On 27/04/16 14:00, Antonio Terceiro wrote: > On Tue, Apr 26, 2016 at 09:32:02PM +0200, Daniel Pocock wrote: >> >> >> It is well documented how developers should create po files for >> i18n support in their debconf configuration questions during >> package install[1]. >> >> What about arbitrary

Re: using whiptail and translated strings from arbitrary scripts

2016-04-27 Thread Antonio Terceiro
On Tue, Apr 26, 2016 at 09:32:02PM +0200, Daniel Pocock wrote: > > > It is well documented how developers should create po files for i18n > support in their debconf configuration questions during package install[1]. > > What about arbitrary scripts that are run from the command line and > don't

Re: using whiptail and translated strings from arbitrary scripts

2016-04-27 Thread Daniel Pocock
On 27/04/16 07:55, Paul Wise wrote: > On Wed, Apr 27, 2016 at 3:32 AM, Daniel Pocock wrote: > >> One use case I'm thinking of is the live CD for PGP key management >> discussed already[2]. After booting, instead of showing a login >> prompt on tty1 it will go into a whiptail/dialog interface, l

Re: using whiptail and translated strings from arbitrary scripts

2016-04-26 Thread Eduard Bloch
Hallo, * Daniel Pocock [Tue, Apr 26 2016, 09:32:02PM]: > > > It is well documented how developers should create po files for i18n > support in their debconf configuration questions during package install[1]. > > What about arbitrary scripts that are run from the command line and > don't use debc

Re: using whiptail and translated strings from arbitrary scripts

2016-04-26 Thread Paul Wise
On Wed, Apr 27, 2016 at 3:32 AM, Daniel Pocock wrote: > One use case I'm thinking of is the live CD for PGP key management > discussed already[2]. After booting, instead of showing a login > prompt on tty1 it will go into a whiptail/dialog interface, like the > installer and ask some questions li

using whiptail and translated strings from arbitrary scripts

2016-04-26 Thread Daniel Pocock
It is well documented how developers should create po files for i18n support in their debconf configuration questions during package install[1]. What about arbitrary scripts that are run from the command line and don't use debconf to store the user responses? How should they interact with whipt