On Mar 6, 2006, at 3:01 AM, Daniel Swarbrick wrote:
> If your "US-English" tags carry the same weight as something like a
> tooltip,
I wasn't talking about hints or comments or tooltips.
First and foremost, the adhoc example I presented was to introduce
the idea of meta data for recordings. That was the tenor of it. What
individual parameters and values are called in that example only
reflects the general objective of discoverability so that the average
Joe can edit it even without having a GUI tool.
What exactly the parameters and values will be called has yet to be
determined, but they should meet the objective that an average person
could edit the file without knowledge about locales.
Quite possibly, the meta data database file might use two parameters,
one for the language and one for the location, for *example* ...
Language = "Romantsch";
CountryOrTerritory = "Japan";
... for recordings made for an IVR system for the Swiss embassy in
Tokyo.
On the system level there may then be another database file which
would contain definitions of languages and countries/territories, for
example ...
Languages = {
...
Romantsch = rm;
Raeto-Romance = rm;
...
};
CountriesAndTerritories = {
...
Japan = JP;
Nihon = JP;
Nippon = JP;
...
};
By looking up the user level and system level dictionaries, the
system would then be able to translate the above into "rm_JP" and use
that as a locale code internally.
Just an *example* of how things could be abstracted and meet both
user level and system level objectives.
regards
benjk
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo!
Security Centre. http://uk.security.yahoo.com
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev
