- 1 Documentation
- 2 Discussion
- 2.1 What is the difference between English and English?
- 2.2 Name vs surname
- 2.3 Cannot add a Lakota name
- 2.4 What is the difference between this property and P1477?
- 2.5 Acute accents to indicate stress
- 2.6 Merge?
- 2.7 Qualifier for name format
- 2.8 Other names for other things
- 2.9 add support for THL as transliteration for Tibetan in property P1559
- 2.10 Language vs script
name of a person in their native language. Could be displayed in addition to the label, if language has a different script
|Type “human (Q5), fictional character (Q95074), human who may be fictional (Q21070568), abstract being (Q15619164), character that may be fictional (Q21070598), animal (Q729)”: element must contain property “instance of (P31)” with classes “human (Q5), fictional character (Q95074), human who may be fictional (Q21070568), abstract being (Q15619164), character that may be fictional (Q21070598), animal (Q729)” or their subclasses (defined using subclass of (P279)). (Help)|
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1559#type Q5, Q95074, Q21070568, Q15619164, Q21070598, Q729, SPARQL, SPARQL (new)
|Qualifiers “transliteration (P2440), Revised Hepburn romanization (P2125), pinyin transliteration (P1721), McCune-Reischauer romanization (P1942), name in kana (P1814), IPA transcription (P898), ISO 9:1995 (P2183), Hungarian-style transcription (P2719), Wylie transliteration (P4187), Revised Romanization (P2001), instance of (P31), has quality (P1552), start time (P580), end time (P582), point in time (P585), sourcing circumstances (P1480), writing system (P282), Möllendorff transliteration (P5139), alternate names (P4970), THL Simplified Phonetic Transcription (P4189), object has role (P3831), of (P642), pronunciation audio (P443), reason for deprecation (P2241), has cause (P828)”: this property should be used only with the listed qualifiers. (Help)|
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1559#Allowed qualifiers, SPARQL, SPARQL (new)
What is the difference between English and English?Edit
The given example is quite strange:
- Barack Obama (Q76), P1559 → (en) "Barack Hussein Obama II"
So in his native language Barack Obama is called "Barack Hussein Obama II", but in English it's "Barack Obama"? And then there is birth name (P1477): "Barack Hussein Obama II (English)". --Kolja21 (talk) 11:23, 30 October 2014 (UTC)
- @Kolja21: I think it should be birth name (P1477): "Barack Obama (English)" (today's most known name, like English label) and birth name (P1477): "Barack Hussein Obama II (English)" (official name or something like this for the moment of born). --putnik 13:03, 17 November 2014 (UTC)
I have added a more useful example for western users: Shinzō Abe (Q132345) has name in native language (P1559): 安倍 晋三 in his native language Japanese (Q5287). This in particular is a nice property when different alphabets are used to display names. —MisterSynergy (talk) 06:43, 14 October 2015 (UTC)
Name vs surnameEdit
- @Infovarius: It should include notable parts of full name. For most cases it's like label on person's native language. For Russian Wikipedia it's the same of "оригинал_имени" ("original name") parameter in infobox. --putnik 13:33, 17 November 2014 (UTC)
- Hmm, too vague. We should have a monolingual property for "personal name in original language" only. --Infovarius (talk) 18:25, 17 November 2014 (UTC)
Cannot add a Lakota nameEdit
For Spotted Tail (Q267752), I'm trying to add name in native language (P1559) = "Siŋté Glešká" in the Lakota language. Lakota is at Lakota (Q33537); it has an ISO 639-3 code of 'lkt'. Yet the system won't accept that language. The error message calls it an illegal value. I've tried using the name, Q value, and ISO code. We should allow any ISO 639-3 code (P220) language. Runner1928 (talk) 03:02, 20 April 2015 (UTC)
- Best is to request addition of the language on Phabricator or on Contact the developers. That's the short term solution. They are working on a long time solution, but don't know how long that will take. Mbch331 (talk) 20:52, 13 October 2015 (UTC)
What is the difference between this property and P1477?Edit
- name in native language (P1559) can be useful to a Wikipedia where the language used by the property has a different script (ruwiki uses for languages other than ru). P1477 is for cases where the current name of a person is different from their (full) name at birth. Both would generally be in the same language.
--- Jura 06:21, 26 February 2016 (UTC)
Acute accents to indicate stressEdit
In some languages stress of words, particularly names, is irregular and thus occasionally indicated by acute accents. Do we consider these acute accents as part of the original name and store them within this property, or would it be better to omit them? At the moment I deal with cyrillic names in Russian language in particular where this is an issue, but the question is basically valid for all languages where optional acute accents are used to indicate stess. Just to make sure: regular diacritics are somewhat different and not part of my question here.
- I think that the question holds its own answer. As far as the accent is optional, it should not be used in normal writing. Maybe a specific property, or qualifier ? --Hsarrazin (talk) 12:58, 7 July 2016 (UTC)
Okay thanks, I will do so in future. Since I’m not able to use IPA and IPA transcription (P898), there will unfortunately not be any information about name spelling in the affected items in near future. Regards, MisterSynergy (talk) 05:54, 8 July 2016 (UTC)
- No, native label (P1705) is for places. --Thibaut120094 (talk) 13:33, 21 July 2017 (UTC)
- @Thibaut120094: So there's no overlap between coverage of these properties? P1705 looks more general to me, so could cover the same uses as this property is currently used for... I've asked for more feedback about this at Wikidata:Project_chat#Native_names. Thanks. Mike Peel (talk) 23:47, 22 July 2017 (UTC)
@Mike Peel: no, names of persons (name in native language (P1559)) are quite different from other names e.g. P1705 and should be kept in separate property. Nicknames are different from P1559 too. d1g (talk) 09:35, 24 July 2017 (UTC)
Qualifier for name formatEdit
Please see Wikidata_talk:WikiProject_Names#Qualifier_for_name_format.
--- Jura 13:40, 15 December 2017 (UTC)
Other names for other thingsEdit
I don't know the restriction to people's names. Many objects, cities, toponyms habe such a kind of name. for example: Canal Dortmund-Ems i Dortmund-Ems-Knanal. Or many villages in the north of Germany, that have an original name in Low German. It is very interesting the way they appeared in the right template, before the restrictions was decreed.--Flamenc (talk) 14:07, 16 April 2018 (UTC)
- There seems to be native label (P1705) for that purpose. I actually came here looking for a "name in original language" for events but these discussions convinced me that we shouldn't have such a property. Deryck Chan (talk) 15:52, 10 August 2018 (UTC)
add support for THL as transliteration for Tibetan in property P1559Edit
The THL Simplified Phonetic Transcription (P4189) should be accepted for property name in native language (P1559) with at least Tibetan language (bo). There is currently a warning.Popolon (talk) 14:12, 21 August 2018 (UTC)
Language vs scriptEdit
I noticed that Liu Cixin (Q607588) has two name in native language (P1559) statements, for simplified / traditional Chinese. But his name can also be written "Liu Cixin". Names aren't in any particular language, are they? We've got the same name written with 3 different scripts. There are probably multiple ways of writing his name in Latin script. Shouldn't this property be labelled "name in native script"? The native script in this case would presumably be simplified Chinese. Ghouston (talk) 04:54, 17 February 2019 (UTC)