11.15.1
DCA Participating Authorities in Wales are developing a consistent approach to bilingual LLPG and LSG data entry conventions. This work is being carried out by the Welsh Language Commissioner – see - http://www.comisiynyddygymraeg.cymru/English/infrastructure/Pages/Technology,-Websites-and-Software-Welsh-Language-Considerations-.aspx (accessed January 2016) which is developing protocols for the standardisation of place names. The following guidance addresses two primary issues confronted by those compiling a dual language gazetteer, with Welsh being the second language:
- The technical issues of using two alphabets in a software system; and
- The SNN conventions which are required to facilitate this.
11.15.2
The guidance below outlines the SNN conventions which must be in place to ensure consistency of translation between the two languages in all instances:
- For future developments SNN / LLPG should only allow building numbering schemes and letter suffixes must not be used. Using numbers therefore allows for a UNED 1, UNED 2 (or UNIT 1, UNIT 2 etc.) monolingual PAO / SAO and for a bilingual rendering as UNED 1 / UNIT 1 without any problem of a divergent numbering / lettering system. In particular, this rule facilitates consistent data sorting within any application.
- Legacy Welsh language addresses should be recorded correctly with a 2 character suffix if that is the official address. If the Welsh language flag is set, two characters may be entered into the PAO and SAO suffix Fields.
- Although having the superset ‘Welsh + English’ alphabet available as a software sorting device incorporated within business applications is necessary for data application users, it should not be used as the basis for allocating building lettering / numbering systems themselves. That causes confusion especially for someone looking for buildings on the ground who does not know that all the letters from two alphabets are incorporated.
- If there are good reasons why a numerical system cannot be used, then the sequence should be in one language only that allows for example UNED A, UNED B, UNED C, UNED CH, etc. (not UNIT A….UNIT CH). If this remains without a translation of the ‘uned’ element in the ENG side of the gazetteer entry then it reinforces that a non-English language system is used and thus there should be no confusion.
- Similarly if only an English text is used then the sequence would run UNIT A, UNIT B, UNIT C, UNIT D in both the ENG and the CYM entries thus ensuring that no-one should be looking for the missing ‘UNIT CH’.
11.15.3
If an address is provided within an LLPG which is identified as being a bilingual gazetteer it must be provided in both languages. A bilingual gazetteer is identified in the LLPG Metadata Record using the code “BIL” in the language Field.
11.15.4
For example, a public building such as a library must be recorded in the LLPG as a BLPU and must have two Approved Preferred LPIs (LOGICAL_STATUS=1), one with the language flag set to “ENG” (English) and the other to “CYM” (Welsh) with the Addressable Object either translated into or captured in the appropriate language. In some instances there is no difference between these values, for example property numbers, as no literal translation is either applicable or appropriate.
11.15.5
Any number of further Alternative or Historical LPIs can be held and flagged under the appropriate language. For example the Welsh speakers in the community may have a local descriptive name for the library but for each LPI created in one language a mirror version must be created in the other language, thus, there is a 1:1 relationship between each ENG and CYM LPI.
11.15.6
Each Street Record must be identified according to which language is in use. This information must be recorded against each Street Record. All new Streets can be specifically named officially in English only or officially in Welsh only or officially in both.
11.15.7
In the first case, English only, both the Welsh and English flagged Street Records must contain the same “English” name, in the second case, Welsh only, both must contain the “Welsh” name and in the third case, English and Welsh, the English and Welsh translations must be held against the appropriate flags.
11.15.8
In all cases the Welsh flagged Street Records must hold locality, where applicable, town and Local Highway Authority information in their Welsh forms and the English flagged Street Records must hold the English forms. Mixed language locality, town and Local Highway Authority constructs are not allowed.
11.15.9
There is not always a complete translation of all address elements, therefore it follows that not all locations have a direct alternative language translation and some property names or place names are the same in either language. If this is the case the Authority Address Custodian must ensure that both language versions of the LPI Records are recorded consistently.
11.15.10
Each LPI Record must be identified according to which language is in use. This language information must be recorded against each LPI.