Jump to content

Talk:Ripuarian language

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Ripuarian Wikipedia

[edit]

Rhinelanders try to build up a Ripuarian Wikipedia. If you can speak or understand ripuarian, please help! The discussion can be found here. Dbach 13:00, 25 Jun 2005 (UTC)

A Ripuarian Wiki has been founded externally, plz don't use the page mentioned above any more. Dbach 14:45, 22 August 2005 (UTC)[reply]

Please support the Ripuarian/Kölsch Wikipedia on Metawiki. --Purodha Blissenbach 04:46, 22 September 2005 (UTC)[reply]

Kölsch = ksh

[edit]

Hoi, according to http://www.ethnologue.com/show_language.asp?code=ksh the code ksh is reserved exclusively for Kölsch. I do not think it great to call something with a code that it is not. GerardM 09:55, 9 April 2006 (UTC)[reply]

work needs to be done

[edit]

anybody got any useful links or info, like maybe language stats, infobox.

Number of speekers?Qrc2006 19:01, 5 August 2006 (UTC)[reply]

Wikipedia of Ripuarian languages

[edit]

It has been suggested to merge this article with the article on the Wikipedia of Ripuarian languages.

This is complete nonsense. A language group and a Wikipedia are two so different things, far apart from each other, that you cannot have one useful article. Trying to make one would end up with 2 sections: (a) the language group (b) the Wikipedia and its history. How strange is that?

There is a policy to have an article on each Wikipedia (see List of Wikipedias) and there is another policy to have an article on each language or language group. Lets stick with that. — Preceding unsigned comment added by Rentenirer (talkcontribs) 11:58, 18 August 2011 (UTC)[reply]

native name

[edit]

Moved from the article as uncourced and contradicting:

  • "| nativename = Ripoarisch"
  • "natively Ripoarėsch"
  • "{{improve|reason="nativename - Ripoarisch" & "natively Ripoarėsch" -- that's contradicting. which is correct? do both forms exist?|date=February 2018}}"

google books doesn't have any reliable source for any of the two names, and it would be surprising, if the native speakers would prefer names for their specific subdialect like Kölsch, Bönnsch ([1]), Öcher Platt, ... -80.133.98.23 (talk) 01:22, 21 May 2018 (UTC)[reply]

language naming inconsistencies

[edit]

I am not here to advocate for anything except consistency.

There are language naming inconsistencies between this article, categories, templates and MediaWiki:

  • Wikipedia has the article Ripuarian language (with redirects from Ripoarisch, Ripuarian (language), Ripuarian dialect, Ripuarian dialect group, Ripuarian dialects, Ripuarian Franconian, Ripuarian languages, Ripuarisch, Ripuiarian Franconian, Ripurian, Ripurian language). There has been no discussion regarding the article name. The article describes Ripuarian as "a German dialect group", not as a separate single language.
  • the en.wiki article identifies an ISO 639-3 language code in the infobox: ksh – this is disputed; see Talk:Ripuarian language § Kölsch = ksh
  • MediaWiki language support returns the name 'Colognian'
    • {{#language:ksh|en}} → Colognian
  • MediaWiki uses the name 'Ripuarian' to refer to ksh.wiki (see List of Wikipedias)
  • templates:
    • {{ksh icon}}(in Kölsch) (deprecated; to be replaced with {{in lang|ksh}} – see TfD)
      categorizes to Category:Articles with Colognian-language external links – calls {{Link language|ksh|cat-lang=Colognian}}
    • {{link language|ksh}}(in Kölsch)
      categorizes to Category:Articles with Ripuarian-language external links
    • {{in lang|ksh}}(in Kölsch) (replaces {{ksh icon}})
      categorizes to Category:Articles with Ripuarian-language sources (ksh)
    • {{lang|ksh|text}}text (has a tool tip that reads: 'Ripuarian language text')
      categorizes to Category:Articles containing Ripuarian-language text
    • {{lang-ksh|text}}Kölsch: text
      categorizes to Category:Articles containing Ripuarian-language text
    • the cs1|2 template suite using |language=ksh, |language=Colognian, |language=Kölsch, or |language=Ripuarian:
      • {{cite book |title=Title |language=ksh}}Title (in Kölsch).
        categorized in Category:CS1 foreign language sources (ISO 639-2)
      • {{cite book |title=Title |language=Colognian}}Title (in Colognian).
        categorized in Category:CS1 foreign language sources (ISO 639-2)
      • {{cite book |title=Title |language=Kölsch}}Title (in Kölsch).
        categorized in Category:CS1 maint: unrecognized language
      • {{cite book |title=Title |language=Ripuarian}}Title (in Ripuarian).
        categorized in Category:CS1 maint: unrecognized language

Of the above, we can do nothing about MediaWiki. For the others, we can standardize on one of 'Colognian' or 'Kölsch', and / or 'Ripuarian' and modify the templates, categories, and article as necessary.

  • {{ksh icon}}, {{link language}}, {{in lang}}, {{lang}}, and {{lang-ksh}} all rely on Module:Lang which overrides the IANA / ISO 639 code-to-name definition (Kölsch) in Module:Language/data/wp languages (Ripuarian) – the provenance of that module is unknown
    • if 'Colognian' is the preferred language name, Module:lang/data is modified to override IANA / ISO 639 / Module:Language/data/wp languages code-to-name definitions
    • if 'Kölsch' is the preferred language name, the override in Module:Language/data/wp languages is disabled
    • if 'Ripuarian' is the preferred language name, no action is required
    • if it is desirable to preserve ksh for either of 'Colognian' or 'Kölsch' and desirable to have a code specific to 'Ripuarian', in Module:lang/data, create a private IETF language tag, perhaps mis-x-ripuar, to specifically identify 'Ripurian' in the various Module:Lang-based templates ('Colognian' or 'Kölsch' handled as described above)
    • regardless of preferred name, {{ksh icon}}, though deprecated, is modified to remove |cat-lang=Colognian as redundant or wrong
    • categorization may change to match the preferred language name(s)
  • the cs1|2 template suite relies on the MediaWiki language name table. However, cs1|2 is capable of overriding MediaWiki code-to-name definitions
    • if 'Colognian' is the preferred language name, no action is required
    • if 'Kölsch' is the preferred language name, Module:Citation/CS1/Configuration is modified to override the MediaWiki code-to-name definition
    • if 'Ripuarian' is the preferred language name, Module:Citation/CS1/Configuration is modified to override the MediaWiki code-to-name definition
    • if either of 'Colognian' or 'Kölsch' (handled as above) along with 'Ripuarian' are the preferred language names, Module:Citation/CS1/Configuration is modified to support the private code-to-name definition described above

Consistency matters. Article name should match category names should match template renderings. So the question is:

  • which language name(s): 'Colognian', 'Kölsch', and / or 'Ripuarian'?

Trappist the monk (talk) 17:13, 5 October 2019 (UTC)[reply]

A month on, and there having been no comment, these decisions:

ksh – reserved for Kölsch per IANA and ISO 639-3
mis-x-colog – created for Colognian
mis-x-ripuar – created for Ripuarian

Trappist the monk (talk) 15:26, 3 November 2019 (UTC)[reply]

1. Colognian is merely the literal English translation of Kölsch. Both are the adjectives that refer to the City of Cologne, or Köln. 2. Kölsch is one of the varieties of Ripuarian, a language which is spoken in Cologne as well as a wider area around that city, and it can be considered the prestige variety of that language. (For comparison, Cantonese can be considered the prestige variety of Yue Chinese.) 3.  The ISO 639-3 code ksh is clearly derived from the word Kölsch, which the standard gives as the autonym of the language designated by that code. The English primary name of the ksh language is, however, Ripuarian. Love —LiliCharlie (talk) 20:38, 3 November 2019 (UTC)[reply]
Forgive me, but what conclusion do you wish readers to draw from what you have written?
Trappist the monk (talk) 23:15, 3 November 2019 (UTC)[reply]
One conclusion is that, despite its derivation and label, ksh is the correct ISO 639-3 code for Ripuarian including Colognian (=Kölsch), as is yue for Yue Chinese including Cantonese. (Per "Denotation" links on iso639-3.sil.org/code/ksh, particularly www.ethnologue.com/language/ksh.) Colognian proper could be assigned a private-use subcode of ksh, e.g. ksh-stdrd ("Standard Ripuarian"), ksh-kolsh or ksh-colog (though ksh-colon might be the better choice, as the spelling Colonian instead of Colognian is attested). Another conclusion is that it is not in line with ISO 639-3 to use the code mis ("Uncoded languages") or an extension of that code for Ripuarian or one of its varieties. Love —LiliCharlie (talk) 00:03, 4 November 2019 (UTC)[reply]
Had the ISO 639-3 custodians wanted to associate ksh with Ripuarian or had they determined that Ripuarian should have its own code, they would not have associated ksh with Kölsch. Because the ISO 639-3 custodians have not elected to 'code' Ripuarian, for our use here, Ripuarian is an uncoded language so the private IETF tag mis-x-ripuar is appropriate. If you disagree with the custodian's decisions, you should take the issue up with them.
I can be persuaded that Kölsch and Colognian are more-or-less synonymous so instead of mis-x-colog for Colognian, we might use ksh-x-cologcolog because the en.wiki article is Colognian dialect (with the 'g').
Trappist the monk (talk) 13:58, 4 November 2019 (UTC)[reply]

About Low Dietsch redirecting here

[edit]

I just noticed that Low Dietsch has been turned into a redirect towards this article. I doubt whether this is the best solution. The two language varieties are apparently very similar, but I think they still shouldn't be treated as if no difference exists between them at all. See as well d:Q151156, where separate articles about Low Dietsch exist both on Wikipedia-fr and Wikipedia-nl.

Another issue in this context: for the last two days, two IPs (I suppose they're actually the same) have removed several internal links to Low Dietsch (example). De Wikischim (talk) 22:49, 22 July 2023 (UTC)[reply]