Eeli Kaikkonen wrote:
BTW, what do linguists do when they want to discuss about a language
which doesn't have a name translated into the language of discussion,
especially if the foreign language uses different script? Or do
scholarly articles use only the native names? I guess linguists want to
Karl Kleinpaste wrote:
I find myself mystified as to why this is any real issue or why any
particular choice here is labeled "wrong." You want to localize to the
user? Fine, go ahead. For Xiphos, we choose "all native, all the time,
when we can." We've had not one complaint and a couple thank
On 11/12/2009 12:08 PM, Sebastien Koechlin wrote:
On Wed, Nov 11, 2009 at 03:50:12PM -0500, DM Smith wrote:
We have a few modules that have entities in them. These are of the fashion
(a character entity),U (a numeric decimal entity) andÅ
(a numeric hex entity).
These cause various problem
On Wed, Nov 11, 2009 at 03:50:12PM -0500, DM Smith wrote:
> We have a few modules that have entities in them. These are of the fashion
> (a character entity), U (a numeric decimal entity) and Å
> (a numeric hex entity).
>
> These cause various problems:
This is because osis2mod does not use an
David Haslam writes:
> I don't suppose we have a procedure in place to do this for any
> front-end, let alone all of them.
> And do we even keep a record of who translated what for those
> localizations which have already been made?
Xiphos has a very simple procedure for handling UI localization
I find myself mystified as to why this is any real issue or why any
particular choice here is labeled "wrong." You want to localize to the
user? Fine, go ahead. For Xiphos, we choose "all native, all the time,
when we can." We've had not one complaint and a couple thank-yous.
I'd like to belie
Another aspect of this topic is what happens when new features are added to a
front-end?
Often this will increase the number of UI items that need to be localized.
As none of the front-end developers are omni-competent in all languages,
this in turn requires that the new UI items must be sent out
There is of course another option:
If we make the language list downloadable and subject to the module manager
then it could be updated, arbitrarily and at will.
We could keep it short and small but totally unconnected to sword releases.
Peter
--
GRATIS für alle GMX-Mitglieder: Die maxdome
On Nov 11, 2009, at 11:05 PM, Chris Little wrote:
> Other things to consider:
>
> 1) If a module in a new language is released, should that module be tagged as
> beta or tagged as requiring the next release of Sword until the next release
> of Sword comes?
>
> E.g., let's suppose Sword 1.6.1
On Thu, 12 Nov 2009, Peter von Kaehne wrote:
> I am not sure were can call either approach really "wrong" - they are
> different and have different advantages.
>
> The main problem with Xiphos approach is as Chris rightly states with
> languages which are so dead and extinct that no one would even
Eeli Kaikkonen wrote:
> Xiphos shows "Hebrew" in hebrew alphabets etc. My opinion is very
> strong here: it's wrong. All names should be in English for English
> speakers, in French for French speakers etc. The above mentioned
> examples should of course be in the same language the user
> understa
11 matches
Mail list logo
