It is said that they initially used kr like knc. And it seemed like they
decided to make knc their domain.

According to their answers, the microlanguages under kr do not communicate
well with knc.
What they want is the knc domain. Of course, their language responses need
to be reviewed by experts.

Anyway, the important thing now seems to be about the translationwiki.
Can I ask them if this(translationwiki kr) is all in knc? Or should we
discuss whether it should be referred to as kr after expert verification?

Sotiale

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
바이러스가
없습니다.www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2024년 4월 9일 (화) 오후 7:33, Amir E. Aharoni <[email protected]>님이
작성:

> I can enable knc for translation, but I am wondering: Is there still use
> for kr? Will there ever be? Or maybe the kr translations can be moved to
> knc? I tried to reach an expert, but didn't succeed.
>
> --
> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
> http://aharoni.wordpress.com
> ‪“We're living in pieces,
> I want to live in peace.” – T. Moore‬
>
>
> ‫בתאריך יום ג׳, 9 באפר׳ 2024 ב-2:46 מאת ‪MF-Warburg‬‏ <‪
> [email protected]‬‏>:‬
>
>> Please see <
>> https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Kanuri>.
>> There's an active project at Wp/knc. Interface translation however is not
>> enabled for knc, but for kr: <https://codelookup.toolforge.org/knc>, <
>> https://codelookup.toolforge.org/kr>.
>> _______________________________________________
>> Langcom mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>>
> _______________________________________________
> Langcom mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
Langcom mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to