From: Kevin Ryde <user42@zip.com.au>
To: ludo@chbouib.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: More i18n
Date: Thu, 25 Jan 2007 07:58:12 +1100 [thread overview]
Message-ID: <87tzygta57.fsf@zip.com.au> (raw)
In-Reply-To: <87mz49patg.fsf@chbouib.org> (Ludovic Courtès's message of "Wed, 24 Jan 2007 00:44:59 +0100")
ludo@chbouib.org (Ludovic Courtès) writes:
>
> Agreed, but that's only the name of the Info node. Changing it here
> would make the line too long for Info.
Call the node just "Internationalization" and then call the sub nodes
something else, that should fit fine. There's a good chance people
coming to such matters for the first time won't even know what "i18n"
stands for.
>%global-locale
> I wondered too. My conclusion is that there's nothing to be afraid of:
> after all, it's a special object and we have full control over it
> (pretty much like the EOF object, for instance[*]).
If someone sets the locale with setlocale from C, does it still work,
or does %global-locale get out of sync. Gtk likes to do that for
instance.
> I think the above Scheme constructs are easier to work
> with (to maintain, to add `localeconv' support, etc.) than a C
> equivalent.
I think you'll find it's easier in C, especially if you have to worry
about different combinations of fallbacks in different funcs.
> (Besides, I don't think it's very high priority, especially since it
> doesn't have any impact on the API itself.)
If you can bring it to a high state of polish then you can put it all
in 1.8.
> What does it buy us to apply `string-append' at the end rather than
> `string-append' at each step?
string-append at each step means O(n^2) worth of copying (in the
string length). That afflicted output string ports until recently.
Of course whether anyone should be using a big number there is
debatable, but at least we can ensure performance doesn't prevent one
from doing so.
> I prefer to explicitly specify the encoding of non-ASCII files.
But is it non-ascii?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-01-24 20:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 15:04 More i18n Ludovic Courtès
2006-12-11 19:42 ` Neil Jerram
2006-12-12 9:09 ` Ludovic Courtès
2006-12-12 19:48 ` Kevin Ryde
2006-12-31 16:23 ` Neil Jerram
2006-12-31 16:22 ` Neil Jerram
2006-12-13 0:11 ` Kevin Ryde
2006-12-31 16:54 ` Neil Jerram
2006-12-11 23:26 ` Kevin Ryde
2006-12-12 9:36 ` Ludovic Courtès
2006-12-12 19:43 ` Kevin Ryde
2006-12-12 19:19 ` Kevin Ryde
2006-12-31 16:15 ` Neil Jerram
2007-01-01 22:32 ` Kevin Ryde
2007-01-16 21:46 ` Ludovic Courtès
2007-01-16 22:08 ` Ludovic Courtès
2007-01-23 0:49 ` Kevin Ryde
2007-01-23 0:46 ` Kevin Ryde
2007-01-23 23:44 ` Ludovic Courtès
2007-01-24 20:58 ` Kevin Ryde [this message]
2007-01-31 21:13 ` Ludovic Courtès
2007-01-31 22:06 ` Kevin Ryde
2007-01-25 1:05 ` Kevin Ryde
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tzygta57.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
--cc=ludo@chbouib.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).