|
From: Brian W. B. <br...@tu...> - 2001-11-30 14:45:05
|
> Ah, about the language system: yes, it may generally
> cause a performance slowdown... this
> could be considered by some people a right price to pay
> to have runtime per-user localization.
Obviously, the current language system could use some
improvement. I do, however, very much like a package-time
translation system. A few thoughts:
o A web-based, password protected, centralized language DB. A
translator could log in and see/translate the most recent
untranslated strings. This would also keep translators from
duplicating effort.
o System would continue to generate *.pp files for
package-time translation.
o Ship a "raw" version of phpWebSite. Running your own
translation is not hard...
o I have never understood the need for runtime translation (if
someone wants to explain, please do). What good is the ability
to display, say the text "Main Menu" in many different
languages when all of your content is locked-in to the
language in which it was written?
o Having our output be a simple string (i.e. there is no
"language engine" handling this output) allows for rather
simple customization. For example, if I really did not like
the term "Main Menu" it is easy for me to change this to read
"Navigation". While it is true that I would need to do this
each time I upgrade, it is a trival thing to do.
I welcome any and all thoughts on this. I would like to see
our methods for maintaining the language files improved, but I
remain unconviced as to the benefit of a runtime translation
system. To those who feel differently, please convince me!
phpWebSite is a team effort and I welcome debate and
discourse.
Kind Regards,
Brian Brown
phpWebSite Project Manager
--
Brian W. Brown
Director, Electronic Student Services
Student Development
Room 269, John Thomas Hall
Appalachian State University
Boone, NC 28608
vox: 828-262-7124
fax: 828-262-2585
L I N U X
.~.
/V\
// \\
/( )\
^^-^^
Love the Penguin
|