From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] default ebrc international
Date: Fri, 02 Oct 2015 03:42:28 -0400 [thread overview]
Message-ID: <20150902034228.eklhad@comcast.net> (raw)
While thinking about international things...
A new feature is the autogeneration of .ebrc if you don't have one,
but of course it's in English.
We support other languages in our messages, should probably do so here.
Maybe not right away, depends on my mood and other things,
but here is a path to get there.
tools/buildsourcestring.pl
Change the program so it accepts multiple input files, like this
infile1 string1 infile2 string2 infile3 string3 ... outfile
It converts the text of the input files into C strings.
For example source files
ebrc-en.default ebrc-fr.default ebrc-de.default etc
These are translations of the default ebrc.
Run buildsourcestring and they all become strings in ebrc.c.
In messages.c, when the language is determined,
set the default ebrc string to the correct string for the language,
so if you need to write out this default file it will be correct.
And of course change the makefiles and CMakeList.txt
as ebrc translations become available.
Karl Dahlke
reply other threads:[~2015-10-02 7:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150902034228.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/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 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).