[sword-devel] isalnum(3) for i18n

Ben Morgan benpmorgan at gmail.com
Wed Aug 13 16:20:03 MST 2008


I'd really like to see an abbreviations field - while a description is
useful, an abbreviation such as KJV, ESV, etc is invaluable when there is
not much room.
Most bibles have such an abbreviation.
I also agree that we should be targeting most of this at the end users of
each module - developers don't matter nearly as much :)

So I think:
Description should be in the foreign language (encoded as per encoding
directive)
There should be a field Abbreviation for a short version (encoded as per
encoding directive)
And the actual module name (presumably derived from the abbreviation, but
ascii) can be used by developers.

Maybe a field like Description_en would be a good idea. Then if you are
using the english locale, you might see that in the frontend.
That way you could also have a Description_fr for french description,
Description_de for german description, etc.

God Bless,
Ben
-------------------------------------------------------------------------------------------
The Lord is not slow to fulfill his promise as some count slowness,
but is patient toward you, not wishing that any should perish,
but that all should reach repentance.
2 Peter 3:9 (ESV)


On Thu, Aug 14, 2008 at 2:40 AM, Eeli Kaikkonen <
eekaikko at mail.student.oulu.fi> wrote:

> On Wed, 13 Aug 2008, Daniel Blake wrote:
>
> > I may be missing something here, but the "Description" field was
> > included so an actual description of a module could be added.
> > Descriptions are very important for people to choose which modules they
> > want to use/look at.  Many times the name of a module just isn't enough
> > to tell people what the module is about.  Similar to the front and back
> > cover of books for review before purchasing them.
> >
> > Wouldn't it be better to add a field for the localized name and use the
> > description field for it's intended purpose?
>
>
> The situation seems to be unclear. Right now descriptions are and they
> should be short, usually it's a couple of words giving the real name of
> the work and the writer. It should be short enough to fit into module
> lists in user interfaces, though a name of a real book may well be quite
> long.
>
> I would really like to see those descriptions in two languages because
> I'm curious. Even if I can't read some language I may look at a module.
> Especially for general books it would be nice to know what they are
> about. That information may not be necessary, but I speak now as an
> end user who is curious and wants to know unnecessary details. After
> all, that's how many people are.
>
> I understand the point of "if you can't read it, you don't need to know
> about it". But I think it's not valid. People want to know and
> even need to know things which someone else can't anticipate.
>
> BTW, most of the Descriptions seem to be in English. Even most of the
> Bible translations which have their names in the native language have
> the English name of the language in their descriptions.
>
>
>  Yours,
>        Eeli Kaikkonen (Mr.), Oulu, Finland
>        e-mail: eekaikko at mailx.studentx.oulux.fix (with no x)
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.crosswire.org/pipermail/sword-devel/attachments/20080814/d60eee3d/attachment.html 


More information about the sword-devel mailing list