From: Patrick Williams <patrick@stwcx.xyz>
To: James Feist <james.feist@linux.intel.com>
Cc: Matt Spinler <mspinler@linux.ibm.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Message registries continuation
Date: Tue, 16 Jun 2020 15:50:22 -0500 [thread overview]
Message-ID: <20200616205022.GD4618@heinlein> (raw)
In-Reply-To: <85015a54-0de6-42e2-bd56-732c7f0a420d@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Tue, Jun 16, 2020 at 01:39:18PM -0700, James Feist wrote:
> On 6/16/2020 12:47 PM, Matt Spinler wrote:
> > Also, it may be overkill to need to read in the same registry for every
> > language, as there could
> > be dozens and realistically they will never all be used on a single
> > system, but if the desire is only
> > to load them at startup before the current language is known I don't
> > really see a way around it.
>
> I think this would require a default language and a bmcweb reload if the
> language changed? Its probably ok to change languages after startup, as
> long as the default language is loaded immediately to lower the chances
> of run-time issues. As changing languages is probably a very infrequent
> operation.
Couldn't two users of the same machine request / require different
languages? I know that any machine used by the Australian developers on
this project I'd need to change the settings on so that I get the proper
spelling of color.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-16 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 19:47 Message registries continuation Matt Spinler
2020-06-16 20:39 ` James Feist
2020-06-16 20:50 ` Patrick Williams [this message]
2020-06-16 20:58 ` James Feist
2020-06-16 21:30 ` Matt Spinler
2020-06-16 21:57 ` James Feist
2020-06-18 15:23 ` Brad Bishop
2020-06-22 20:46 ` Matt Spinler
2020-06-22 21:16 ` James Feist
2020-06-23 18:02 ` Matt Spinler
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200616205022.GD4618@heinlein \
--to=patrick@stwcx.xyz \
--cc=james.feist@linux.intel.com \
--cc=mspinler@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.