On Tue, Apr 24, 2018 at 2:41 AM, Rainer Jung wrote:
> Am 24.04.2018 um 07:20 schrieb Marion et Christophe JAILLET:
>>
>> Le 24/04/2018 à 02:58, William A Rowe Jr a écrit :
>>>
>>> On Thu, Apr 19, 2018 at 12:20 AM, Marion et Christophe JAILLET
>>>
Am 24.04.2018 um 07:20 schrieb Marion et Christophe JAILLET:
Le 24/04/2018 à 02:58, William A Rowe Jr a écrit :
On Thu, Apr 19, 2018 at 12:20 AM, Marion et Christophe JAILLET
wrote:
Le 18/04/2018 à 22:12, William A Rowe Jr a écrit :
On Wed, Apr 18, 2018 at 2:31
Le 24/04/2018 à 02:58, William A Rowe Jr a écrit :
On Thu, Apr 19, 2018 at 12:20 AM, Marion et Christophe JAILLET
wrote:
Le 18/04/2018 à 22:12, William A Rowe Jr a écrit :
On Wed, Apr 18, 2018 at 2:31 PM, Nick Kew wrote:
I suspect the
On Thu, Apr 19, 2018 at 12:20 AM, Marion et Christophe JAILLET
wrote:
> Le 18/04/2018 à 22:12, William A Rowe Jr a écrit :
>>
>> On Wed, Apr 18, 2018 at 2:31 PM, Nick Kew wrote:
I suspect the straightforward way to do this, in 2.6/3.0,
On Thu, Apr 19, 2018 at 10:24 AM, Eric Covener wrote:
> On Thu, Apr 19, 2018 at 9:38 AM, Eric Covener wrote:
>>> If using gettext, there are some tools to check for that.
>>
>> Would be nice to put some feelers out to $bigcos to make sure we
>> choose a
On Thu, Apr 19, 2018 at 9:38 AM, Eric Covener wrote:
>> If using gettext, there are some tools to check for that.
>
> Would be nice to put some feelers out to $bigcos to make sure we
> choose a format they'd accomoddate [if they were otherwise willing to
> donate a one-time
> If using gettext, there are some tools to check for that.
Would be nice to put some feelers out to $bigcos to make sure we
choose a format they'd accomoddate [if they were otherwise willing to
donate a one-time translation]
--
Eric Covener
cove...@gmail.com
Le 18/04/2018 à 22:12, William A Rowe Jr a écrit :
On Wed, Apr 18, 2018 at 2:31 PM, Nick Kew wrote:
I suspect the straightforward way to do this, in 2.6/3.0, will be to add an
i18n table of the error log strings extracted from and indexed by those
APLOGNO() entries. No match?
On Wed, Apr 18, 2018 at 2:31 PM, Nick Kew wrote:
>
>> I suspect the straightforward way to do this, in 2.6/3.0, will be to add an
>> i18n table of the error log strings extracted from and indexed by those
>> APLOGNO() entries. No match? Default English message.
>
> Please, not
> I suspect the straightforward way to do this, in 2.6/3.0, will be to add an
> i18n table of the error log strings extracted from and indexed by those
> APLOGNO() entries. No match? Default English message.
Please, not without an overhaul of APLOGNO to automate it a lot better!
The time to
On Wed, Apr 18, 2018 at 1:53 PM, Marion et Christophe JAILLET
wrote:
> Le 18/04/2018 à 20:00, William A Rowe Jr a écrit :
>>
>> Localizing our error messages alone would go a long ways to being
>> friendly to non-english speaking administrators. If we don't want to
Le 18/04/2018 à 20:00, William A Rowe Jr a écrit :
I'm speaking of personal i18n experience as a Windows developer, and
assigning support for Cyrillic-based languages in nginx that I've presumed
exist (I've never researched the software but am familiar with the origins.)
[...]
In short, we
I'm speaking of personal i18n experience as a Windows developer, and
assigning support for Cyrillic-based languages in nginx that I've presumed
exist (I've never researched the software but am familiar with the origins.)
IIS/Windows long offered robust support to the multibyte character
> On 18 Apr 2018, at 17:55, William A Rowe Jr wrote:
>
> So I'll start with this;
Erm, would you like to cite a source for that claim? I confess it’s not one
I’ve seen.
I don’t follow either nginx marketing nor any fan club they might have.
If what you refer to is the
14 matches
Mail list logo