All of lore.kernel.org
 help / color / mirror / Atom feed
From: susan jasinski <susantjasinski@gmail.com>
To: openbmc@lists.ozlabs.org
Subject: GUI translation bundles
Date: Fri, 15 Feb 2019 14:17:06 -0600	[thread overview]
Message-ID: <CANT4Nr+Gpd7roWyPT5vpeskL9bvKBbsKKma_6WhPpenWdwACwg@mail.gmail.com> (raw)

I’d like some feedback about how to breakdown translation bundles for the GUI.

My initial thought is to create a bundle per panel since companies
have the option to pick and choose which upstream panels they want to
use. Would this be an overwhelming amount of bundles? Does this idea
scale well as we grow the number of panels? Does this scale well as
new panels are added after existing panels have already been
translated?

In addition, there could a “global” bundle for navigation and header,
Should this include words/phrases that are common across many panels
such as “save” and “cancel”?

Also, should GUI notifications/messages be in their own bundle or put
into their respective panel’s bundle?

Can you think of other factors that should guide this decision?

Thank you, Susan Jasinski

             reply	other threads:[~2019-02-15 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 20:17 susan jasinski [this message]
2019-02-18  9:19 ` GUI translation bundles Alexander Amelkin
2019-02-19 19:02   ` Derick
2019-02-21 17:49   ` susan jasinski

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=CANT4Nr+Gpd7roWyPT5vpeskL9bvKBbsKKma_6WhPpenWdwACwg@mail.gmail.com \
    --to=susantjasinski@gmail.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.