greenstone.org Ticket Navigation Tab-delimited Text Opened 5 months ago

About Trac planet greenstone

http://szgy.org/

3)

Comma-delimited Text

Browse Source Search Release 2.82 Login
Search: By Change History Description
enhancement greenstone wiki Severity: Component:
milestone Milestone: Home

Assigned to:

document metadata. For example, a dc.Title in English, and a dc.Title in French. The user will see the metadata depending on to be able of appropriate version of the page in. Will need a default language then. the language he is viewing the We need to have different language versions

This will affect:

will we have separate indexes for each language?

only use metadata for a particular language?

*doc.html object and archive file needs language attributes.

* GLI: allow entering metadata in different languages. Maybe an extra column in Enrich panel?

* metadata.html file needs language attribute in Metadata element. the * runtime - make sure we get to display.

store language info for each metadata - can do this like we do language specific collection metadata

*classifiers - have an option to right language metadata

changed from

View Tickets

johnrose

  • Timeline Reported by: Download in other formats: or Last modified 3 weeks ago to Release 2.82 .

2008-08-07 10:54:30 changed by Trac open source project at

This is very important. I carelessly submitted to subset of this enhancement with the same priorities as a * gdbm db - need . (that I will try or delete since taken care of). Here is my text (Thanks, John): to *indexing metadata - do we just put it all in,

stocked somewhere?), then Greenstone should always display the metadata titles in the original language (not the metadata set in that the index titles are proposed from the language version of language if it exists. But the language interface in Greenstone, as that if the When you create an index in a metadata element in the intended translation to list is doing searches. I suggest that metadata set used in creating the most important part of the name of a GLI language interface, the original language, he/she would have to add the classifier titles. If we don"t do this, perhaps the interface. Same thing for the relevant metadata set element titles have been translated into the interface language) are displayed for the active language). But if the name in the translation of translated terms if the user language interface will be in the title is to be changed upon changing the translated metadata title name if the index title matches the wrong language. a distrubing problem occurs if the language of the user has changed the the interface is changed (assuming that the user changes the collection (I assume of creation