well, with the debate raging about plans for the web interface and
the importance of non-English stuff () it seems like a good time to
bring up the idea of translating the sword website into (at minimum)
appropriate languages, imho these would do for starters:
Important imho:
German
Chinese Tra
bring up the idea of translating the sword website into (at minimum)
appropriate languages, imho these would do for starters:
This is a really important point I missed in my list of improvements
that are IMO necessary for the Sword website :)
_If_ there is going to be a change to the website this
This is a good idea. I will say Korean and Spanish should be in the frist tier for
sure. Not sure about Thai and Arabic.
Why Korean should be first tier?
1. According to http://www.glreach.com/globstats/
The ranking of the language used on the net is
English 36.5%
Chinese (combined with Trad
Daniel, that's a very useful and good idea!
For www.bibletime.info we have a online translation tool in place which offers
the possibility to translate and edit the messages of the chosen language
online.
The data is stored in a aSQL database.
In my opinion the online translation tool is very
On Mon, 24 Feb 2003, Daniel Glassey wrote:
> well, with the debate raging about plans for the web interface and
> the importance of non-English stuff () it seems like a good time to
> bring up the idea of translating the sword website into (at minimum)
> appropriate languages, imho these would
In a message dated 2/25/2003 12:07:12 AM Pacific Standard Time, [EMAIL PROTECTED] writes:
I think the list of most important languages is not important. Given the
difficulty we've had even getting people to translate those few strings
for book names and the UIs and the fact that we can't make a
ok guys. I'm really not sure what we're talking about.
If we do a localization of anything, it will not be extra work (on our
end) to allow it support other languages. Please don't feel your
language group will be left out. If you can get a browser to render it,
and we add localization (which
Joachim,
I think what you did with bibletime.info is really great. I'm not sure
how much of the technical framework we'd be willing to use on crosswire,
but the concepts are awesome. I'd really like to get some more detailed
explanations of your implementation and see if we can come up with a
Joachim,
I had a look at the i18n taglib from jakarta and don't like it. I
don't like the idea of replacing all strings in the source files with
some key name. It makes the page very unreadable.
Martin showed me some of your stuff earlier today and it was great.
Here's my plan for a jsp imp
Troy,
I don't really know the matter very well, but I'll say something anyway,
risking mistakes. Joachim, maybe you can comment on this.
The main objection I'd have is that you need to reinvent the wheel completely.
The GNU gettext package offers so many cool features that you would not
implem
Just a quick note,
we don't use gettext on bibletie.info anymore, because it turned out it's ways
too slow for websites where we had to check whether a string is already
included in the catalogue.
I'll write some comments on Troy's eMail soon.
Joachim
> Troy,
>
> I don't really know the matte
One (imho) very important thing is the ability to edit the the
translations offline. This would allow people on limited dialup to
work on it.
I'd suggest that there should be a way to download the 'translation
page' in a format that can be easily edited. A spreadsheet file is
one option though
I could provide some technolgy to dyanmically display different languages and seperate
the text data from the html structure. Localization for HTML is always the headache.
However, that is based on JavaScript and DOM Level 1. Not sure that will help if we
cannot use client side JavaScript.
Ther
In Mozilla, we use ENTITY in DTD for XUL (XML based ui) files. We modify the expat to
read in those DTD file based on a chrome locale.
In C and JavaScript file while we need to display UI in the run time, we use Java's
Property file format.
Look at http://www.mozilla.org/projects/l10n/mlp_tool
In a message dated 2/25/2003 1:52:01 PM Eastern Standard Time, [EMAIL PROTECTED]
writes:
> Just a quick note,
> we don't use gettext on bibletie.info anymore, because it turned out it's ways
> too slow for websites where we had to check whether a
> string is already
> included in the catalogue
In a message dated 2/25/2003 12:06:06 PM Eastern Standard Time, [EMAIL PROTECTED]
writes:
>
> I'd suggest that there should be a way to download the 'translation
> page' in a format that can be easily edited. A spreadsheet file is
> one option though it requires people to have a spreadsheet
>
16 matches
Mail list logo
