Template talk:ko-l
Param Request
[edit]Could an admin please modify this template so that the requirement for a {{{1}}} (the transcription of the word) is bypassed? The following code would do the job:
<includeonly>{{#ifeq:{{{link|}}}|no|{{term||{{{1|}}}|sc=Kore}}|{{Kore|{{wlink|{{{1|}}}}}}} }} {{#if:{{{2|}}}| (''{{{2|}}}''{{#if:{{{3|}}}|, “{{{3|}}}”}}{{#if:{{{4|}}}|, {{#ifeq:{{{link|}}}|no|{{term||{{{4|}}}|sc=Kore}}|{{Kore|{{wlink|{{{4|}}}}}}}}}}}{{#if:{{{note|{{{5|}}}}}}|, {{{note|{{{5|}}}}}} }})|{{#if:{{{3|}}}| (“{{{3|}}}”)}}}}</includeonly>
Thanks. Wyang (talk) 05:16, 26 February 2013 (UTC)
- By "bypassed", do you mean just that it's ignored if left out? -- Eiríkr Útlendi │ Tala við mig 05:28, 26 February 2013 (UTC)
- Yes. Included if exists, ignored if doesn't exist. Wyang (talk) 05:33, 26 February 2013 (UTC)
- Okay. Now that I look at it, though, I'm a bit baffled what it should look like. The basic format:
{{ko-inline|한국어|hangugeo|[[Korean]]|韓國語}}
- So if arg 1 is excluded, the call would look like:
{{ko-inline||hangugeo|[[Korean]]|韓國語}}
- However, given the following sample of a full call:
- ... I find myself scratching my head about what this should look like without that first argument -- all you'd have would be the bits in the parentheses, which doesn't seem to be right somehow.
- If you could knock up some dummy HTML or wikicode that just shows the formatting for what you're thinking of, or perhaps a sample page showing the same, I'd be happy to implement it. -- Eiríkr Útlendi │ Tala við mig 06:02, 26 February 2013 (UTC)
- Sorry... {{{2}}} is what I meant: the transcription. Wyang (talk) 07:06, 26 February 2013 (UTC)
- Ta, easy enough then. :) But wouldn't you want a transcription as a general rule, for sake of entry completeness? EN WT does target English readers, after all, who may not know how to read Hangul. -- Eiríkr Útlendi │ Tala við mig 07:21, 26 February 2013 (UTC)
- Sorry... {{{2}}} is what I meant: the transcription. Wyang (talk) 07:06, 26 February 2013 (UTC)
- Omission of transcription only occurs in etymologies of Korean words.. The readers can get the transcription if they click on the Hangeul links. I don't want to have to input so much when auto-generating Korean entries. I think definition is probably more important than pronunciation in etymology, but the current code won't allow the definition to be displayed without a transcription, hence the change. Wyang (talk) 07:29, 26 February 2013 (UTC)
- In process. It's a bit more convoluted than I first thought, so I'll have to finish it later (it's late here and I must crash). G'night, -- Eiríkr Útlendi │ Tala við mig 08:12, 26 February 2013 (UTC)
Edit request
[edit]Could an admin please add automatic romanisation to this template? The code should be replaced by
<includeonly><!-- -->{{#ifeq:{{{link|}}}|no<!-- -->|<!-- -->{{term/t|ko||{{{1|}}}|tr=-}}<!-- -->|<!-- -->{{term/t|ko|{{{1|}}}|tr=-}}<!-- -->}}<!-- --> <!-- --> (''{{#if:{{{2|}}}|{{{2}}}|{{xlit|ko|{{{1|}}}}}}}''<!-- -->{{#if:{{{3|}}}<!-- -->|<!-- -->, “{{{3|}}}”<!-- -->}}<!-- -->{{#if:{{{4|}}}<!-- -->|<!-- -->, <!-- -->{{#ifeq:{{{link|}}}|no<!-- -->|<!-- -->{{term/t|ko||{{{4}}}|tr=-}}<!-- -->|<!-- -->{{term/t|ko|{{{4}}}|tr=-}}<!-- -->}}<!-- -->}}<!-- -->{{#if:{{{note|{{{5|}}}}}}<!-- -->|<!-- -->, <!-- -->{{{note|{{{5|}}}}}}<!-- -->}}<!-- -->)<!-- --></includeonly><!-- --><noinclude>{{documentation}}</noinclude>
Thanks. Wyang (talk) 14:29, 12 April 2014 (UTC)
Stand-alone consonant support request
[edit]{{ko-l|ㅂ니다}}
yields ㅂ니다 (mnida) rather than the desired 'ㅂ니다 (mnida)'. Can anyone fix this? —Ieay4a (talk) 13:59, 13 August 2015 (UTC)
Transliteration override
[edit]@Wyang Hi Frank. Could you add a transliteration override, as with 원룸 (wonnum), please? E.g. ...|tr=wonnum or similar? @Suzukaze-c In diff please note the irregular pronunciation and translit of 원룸 (wonnum). That's why {{l}}
was used. --Anatoli T. (обсудить/вклад) 06:22, 8 October 2016 (UTC)
- 원룸 (wonnum) or 원룸 (wonnum, “studio”) or 원룸 (wonnum, “studio”) or 원룸 (wonnum, “studio”). :) Wyang (talk) 06:29, 8 October 2016 (UTC)
- Thanks. I knew about other methods. Very often, it's just the transliteration that's required. Thanks for fixing!--Anatoli T. (обсудить/вклад) 06:59, 8 October 2016 (UTC)
Note parameter
[edit]@Suzukaze-c, Erutuon, Dine2016: Hi. Are you able to restore |note=
as it was used in entries such as 규율 (gyuyul) or 규률 (gyuryul)? They use "North Korea" and "South Korea" labels. --Anatoli T. (обсудить/вклад) 01:09, 15 January 2021 (UTC)
- Done —Suzukaze-c (talk) 10:37, 8 March 2021 (UTC)
Hyphen override
[edit](Notifying TAKASUGI Shinji, Atitarev, HappyMidnight, Tibidibi, Quadmix77, Kaepoong, AG202, The Editor's Apprentice, Saranamd): @YeBoy371 Not sure where else to put this, but I've implemented the override --
as a way to force a hyphen to display at a certain point in the middle of a term, for instances where that's needed. For example, 마르크스-레닌주의 (mareukeuseu-reninjuui) can be linked with {{m|ko|마르크스--레닌주의}}
. Theknightwho (talk) 02:08, 30 July 2024 (UTC)
- @Theknightwho: Thanks.
- It also works here with regular template 오스트리아-헝가리 (Oseuteuria-heonggari), although, I can't capitalise the second part.
- I raised it at Wiktionary:Grease_pit/2023/April#Override_for_Korean_hyphen_is_required., first mentioned at Module_talk:ko-translit#Is_suppressing_hyphens_a_good_idea_in_100%_of_cases?
{{ko-proper noun|head=^오스트리아--^헝가리}}
produces an error, though:- Lua error in Module:ko-headword at line 147: Could not produce transliteration. There may be non-hangeul characters in the entry title. Anatoli T. (обсудить/вклад) 23:00, 1 August 2024 (UTC)
- And adding
{{para|hangeul=^오스트리아--^헝가리}}
doesn't override but adds (hangeul 오스트리아헝가리) to the headword. Anatoli T. (обсудить/вклад) 23:04, 1 August 2024 (UTC)- Fixed it with
{{ko-pos|proper|head=오스트리아--헝가리}}
Anatoli T. (обсудить/вклад) 23:08, 1 August 2024 (UTC)- @Atitarev Yes, I've noticed that there's an issue with
^
after-
, but I checked and it wasn't caused by this change. I had a look into it briefly, but it seemed quite complicated to fix, but I'll work on it soon. Theknightwho (talk) 23:09, 1 August 2024 (UTC)
- @Atitarev Yes, I've noticed that there's an issue with
- Fixed it with
- And adding