Menu

#79 LANG support - translate standard values in ASSO|RELA

2.x
closed
Interface (97)
5
2006-02-13
2003-09-27
Nils Meier
No

standard phrases in RELA should be translated by the UI
to the user's language, e.g.:

godfather
godmother
informant
informant at birth
informant at death
other
registry officer at birth
registry officer at death
registry officer at marriage
witness
witness at birth
witness at death
witness at marriage
...

Discussion

  • Nils Meier

    Nils Meier - 2004-03-08
    • summary: translate standard values in ASSO|RELA --> LANG support - translate standard values in ASSO|RELA
     
  • Nils Meier

    Nils Meier - 2004-03-08

    Logged In: YES
    user_id=118458

    also of course the language should be reflected in the header
    as per Gedcom spec

    > HEADER: =
    >
    > n HEAD {1:1}
    > +1 SOUR <APPROVED_SYSTEM_ID> {1:1}
    > +2 VERS <VERSION_NUMBER> {0:1}
    > +2 NAME <NAME_OF_PRODUCT> {0:1}
    > +2 CORP <NAME_OF_BUSINESS> {0:1}
    > +3 <<ADDRESS_STRUCTURE>> {0:1}
    > +2 DATA <NAME_OF_SOURCE_DATA> {0:1}
    > +3 DATE <PUBLICATION_DATE> {0:1}
    > +3 COPR <COPYRIGHT_SOURCE_DATA> {0:1}
    > +1 DEST <RECEIVING_SYSTEM_NAME> {0:1*}
    > +1 DATE <TRANSMISSION_DATE> {0:1}
    > +2 TIME <TIME_VALUE> {0:1}
    > +1 SUBM @XREF:SUBM@ {1:1}
    > +1 SUBN @XREF:SUBN@ {0:1}
    > +1 FILE <FILE_NAME> {0:1}
    > +1 COPR <COPYRIGHT_GEDCOM_FILE> {0:1}
    > +1 GEDC {1:1}
    > +2 VERS <VERSION_NUMBER> {1:1}
    > +2 FORM <GEDCOM_FORM> {1:1}
    > +1 CHAR <CHARACTER_SET> {1:1}
    > +2 VERS <VERSION_NUMBER> {0:1}
    > +1 LANG <LANGUAGE_OF_TEXT> {0:1} <-----------
    Here
    > +1 PLAC {0:1}
    > +2 FORM <PLACE_HIERARCHY> {1:1}
    > +1 NOTE <GEDCOM_CONTENT_DESCRIPTION> {0:1}
    > +2 [CONT|CONC] <GEDCOM_CONTENT_DESCRIPTION>
    {0:M}
    >
    > LANGUAGE_OF_TEXT: = {Size=1:15}
    > [ <LANGUAGE_ID> ]
    > The human language in which the data in the transmission
    is normally
    > read or
    > written. It is used primarily by programs to select language-
    specific
    >
    > sorting sequences and phonetic name matching algorithms.
    >
    > LANGUAGE_ID: = {Size=1:15}
    > A table of valid latin language identification codes.
    > [Afrikaans | Albanian | Anglo-Saxon | Catalan |
    Catalan_Spn | Czech |
    > Danish
    > | Dutch | English | Esperanto | Estonian | Faroese |
    Finnish | French
    > |
    > German | Hawaiian | Hungarian | Icelandic | Indonesian |
    Italian |
    > Latvian
    > | Lithuanian | Navaho | Norwegian | Polish | Portuguese |
    Romanian |
    > Serbo_Croa | Slovak | Slovene | Spanish | Swedish |
    Turkish | Wendic
    > ]
    >
    > Other languages not supported until UNICODE
    > [Amharic | Arabic | Armenian | Assamese | Belorusian |
    Bengali | Braj
    > |
    > Bulgarian | Burmese | Cantonese | Church-Slavic | Dogri |
    Georgian |
    > Greek
    > | Gujarati | Hebrew | Hindi | Japanese | Kannada | Khmer |
    Konkani |
    > Korean
    > | Lahnda | Lao | Macedonian | Maithili | Malayalam |
    Mandrin |
    > Manipuri |
    > Marathi | Mewari | Nepali | Oriya | Pahari | Pali | Panjabi |
    Persian
    > |
    > Prakrit | Pusto | Rajasthani | Russian | Sanskrit | Serb |
    Tagalog |
    > Tamil
    > | Telugu | Thai | Tibetan | Ukrainian | Urdu | Vietnamese |
    Yiddish ]
    >

     
  • Nils Meier

    Nils Meier - 2006-02-13
    • status: open --> closed
     
  • Nils Meier

    Nils Meier - 2006-02-13

    Logged In: YES
    user_id=118458

    this is not planned - there are no 'standard values' really
    - only suggestions by Gedcom.

    It's basically freetext that I'm not going to try to
    interpret and translate -> closed

     

Log in to post a comment.