User talk:Ekirahardian/Before 6 July 2024

Welcome!

Hello, welcome to Wiktionary, and thank you for your contributions so far.

If you are unfamiliar with wiki editing, take a look at Help:How to edit a page. It is a concise list of technical guidelines to the wiki format we use here: how to, for example, make text boldfaced or create hyperlinks. Feel free to practice in the sandbox. If you would like a slower introduction we have a short tutorial.

These links may help you familiarize yourself with Wiktionary:

• Entry layout (EL) is a detailed policy documenting how Wiktionary pages should be formatted. All entries should conform to this standard. The easiest way to start off is to copy the contents of an existing page for a similar word, and then adapt it to fit the entry you are creating.
• Our Criteria for inclusion (CFI) define exactly which words can be added to Wiktionary, though it may be a bit technical and longwinded. The most important part is that Wiktionary only accepts words that have been in somewhat widespread use over the course of at least a year, and citations that demonstrate usage can be asked for when there is doubt.
• If you already have some experience with editing our sister project Wikipedia, then you may find our guide for Wikipedia users useful.
• The FAQ aims to answer most of your remaining questions, and there are several help pages that you can browse for more information.
• A glossary of our technical jargon, and some hints for dealing with the more common communication issues.
• If you have anything to ask about or suggest, we have several discussion rooms such as the Tea room, Beer parlour and Grease pit.

I hope you enjoy editing here and being a Wiktionarian. If you have any questions, bring them to the Wiktionary:Information desk. If you do so, please sign your posts with four tildes: ~~~~ which automatically produces your username and the current date and time.

Again, welcome to Wiktionary! KevinUp (talk) 18:09, 19 January 2019 (UTC)

kyūjitai

Hello,

Japanese kyūjitai is not considered the main form, it's shinjitai. Kyūjitai should be simple soft redirects, without "see also", etymology sections, etc. That way the contents are not duplicated and are kept consistent. --Anatoli T. ^{(обсудить}/^вклад) 13:54, 2 January 2019 (UTC)

Also, be sure to only create kyūjitai terms that are attestable in historical literature. Some terms before 1947 may have non-standard orthography. A good place to look at the orthography of kyūjitai terms would be the Constitution of Japan (w:ja:s:日本國憲法) and the Meiji Constitution (w:ja:s:大日本帝國憲法). KevinUp (talk) 18:09, 19 January 2019 (UTC)

Korean and Vietnamese compounds

Thank you very much for adding Korean and Vietnamese compounds, as well as Sino-Xenic descendants. If you have the time, there are about 1000 entries here which has the old {{vi-hantu}} template that needs to be updated to {{vi-noun|sc=Hani}}, {{vi-verb|sc=Hani}}, etc. Thank you very much, and have a good weekend. KevinUp (talk) 18:09, 19 January 2019 (UTC)

Update: Conversion of {{vi-hantu}} template to {{vi-noun|sc=Hani}} etc. has been  Done. KevinUp (talk) 06:50, 20 January 2019 (UTC)

I think you might be interested in this: Category:Sino-Vietnamese words with uncreated Han etymology. Note that some entries such as Bạch Mã Hoàng Tử are sum of parts that don't need Han character entries. Thank you for your contributions so far! KevinUp (talk) 13:30, 7 February 2019 (UTC)

Wasei-kango

Descendants of Wasei-kango (和製漢語) are to be listed in the Japanese section, not the Chinese section. See 目的#Japanese and 積極#Japanese for example. KevinUp (talk) 20:02, 27 January 2019 (UTC)

Hi. You might want to check the following (when you have the time, of course). Some of these were added by other editors.

Descendants in Chinese section (should be in Japanese section)

• 人民
• 自然
• 單位
• 科學
• 系統
• 社會
• 主義
• 政治
• 代表
• 文化
• 政策
• 博士
• 勞動
• 共和
• 文明
• 保險
• 俱樂部
• 世界語

Also, take a look at 目的語／目的语 (mùdìyǔ). Even though it has Japanese and Korean forms, those terms are not Sino-Xenic descendants, because the Japanese/Korean meanings were derived independently from Chinese, due to 目的#Japanese itself being a wasei-kango. KevinUp (talk) 13:30, 7 February 2019 (UTC)

Community Insights Survey

Share your experience in this survey

Hi Ekirahardian/Before 6 July 2024,

The Wikimedia Foundation is asking for your feedback in a survey about your experience with Wiktionary and Wikimedia. The purpose of this survey is to learn how well the Foundation is supporting your work on wiki and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. Email us if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely,

RMaung (WMF) 14:34, 9 September 2019 (UTC)

Readings from the Nôm foundation or Trần (2004)

Hello. I would like to point out that Hán-Việt readings obtained from the Nôm foundation are likely to be incorrect, because some of the readings (particularly characters not used in pre-colonial Vietnamese texts) are based on modern Mandarin which has four tones, rather than Late Middle Chinese, which had up to eight tones.

I would also like to point out that readings from Trần (2004) (Giúp đọc Nôm và Hán Việt) may also be unreliable for the same reason. So if you come across a character in the Nôm foundation that only has readings from gdhn, try looking for the same character in other sources, such as:

1. Nguyễn (2014) [1]
2. Nguyễn et al. (2009) [2]
3. Bonet (1899) [3]
4. Génibrel (1898) [4]
5. Taberd (1838) [5]

Readings from these dictionaries are much more reliable because they are not based on modern Mandarin. In future, I will propose for entries based on gdhn to be removed unless they can be sourced in other dictionaries that are not based on Mandarin. KevinUp (talk) 02:20, 10 September 2019 (UTC)

Chu Nom

Hey- with the Chinese languages, all the words that have a particular character are included in a "Compounds" box on the page of that character. Should 㗂 have a list of all the Vietnamese words including the character 㗂? Just a thought. --Geographyinitiative (talk) 00:25, 20 September 2020 (UTC)

To be honest i don't have an opinion on that, but isn't the list on the page tiếng enough? Ekirahardian (talk) 09:45, 20 September 2020 (UTC)

河馬

I reverted your pronunciations because they look like they are inferred based on the pronunciation of each character. — justin(r)leung _{{ (t...) | c=› }} 00:53, 29 January 2021 (UTC)

Template:ko-noun

Hello, thank you for your contributions! When you add Sino-Korean words like 번화, please use {{ko-noun|hanja=繁華}} to generate complete header lines. Thanks in advance!--Tibidibi (talk) 15:11, 6 March 2021 (UTC)

Images of the Five Scripts for Sanskrit

When will images for the Bhaiksuki, Grantha, Modi, Nandinagari and Siddham writing systems be added to Module:Unicode data? --Apisite (talk) 04:38, 9 January 2022 (UTC)

Hello, thank you for the message, I'll do it but it might take a while since I'm still doing things manually (Type the character one by one in LibreOffice Impress, one character per page -> Save it to PDF -> Convert it to SVG -> Edit it with Inkscape to remove the white background one by one.) and I don't frequently access Wiktionary.

Sincerely Ekirahardian (talk) 09:32, 13 January 2022 (UTC)

You're welcome, don't forget the Ahom script. --Apisite (talk) 07:24, 14 January 2022 (UTC)

Regarding Ahom script, some new characters were released in Unicode 14.0.0 and are still not covered by Noto. I'll postpone the glyphs extraction until Noto release the new version of Noto Sans Ahom that cover the new characters. Ekirahardian (talk) 13:42, 14 January 2022 (UTC)

Accadian cuneiform

Hi. I added 800 svg files to Module:Unicode data/images/012. However, I just went by the file names on Commons. On the module talk page, I list those U characters that had more than one possible file. You can see where I trimmed the extras in my last edit, (rm. duplicates). If you think I made poor choices for any of those, please feel free to adjust. Thanks. kwami (talk) 22:07, 6 March 2022 (UTC)

BTW, you can do a mass extraction of all the characters in a font to SVG files using the freeware FontForge. There shouldn't be any need for further adjustment (e.g. no white background). I think you can choose either their Unicode values or character names as the names of the SVGs. You can also mass upload them to commons, though I'm not sure how to do that. kwami (talk) 22:10, 6 March 2022 (UTC)

Thank you so much for the suggestion! I actually doing it manually on purpose, so I can define the border length and make it so every glyph will have a proportional size compared to each other. I also already found a quicker way to extract the characters using JavaScript plus paged.js instead of LibreOffice Impress, that's why it's now possible to extract about six thousand Tangut characters from Noto fonts. Ekirahardian (talk) 14:09, 7 March 2022 (UTC)

Good. I was afraid you might be doing a lot of extra work for no purpose. kwami (talk) 00:58, 8 March 2022 (UTC)

Javanese

Added to Module:Unicode data/images/00A on Wikt-id, so no need to upload. kwami (talk) 21:13, 15 April 2022 (UTC)

hello

what is your opinion on life 216.57.213.194 20:55, 12 March 2023 (UTC)

Switching out {{desc}} for {{desctree}}

I noticed you've been switching out {{desc}} for {{desctree}} in descendants sections. There are quite a few instances there this is undesired, like entries with many descendants, or borrowings, especially those into other language families. It's then that we use {{see desc}}, but you'll also want to pay attentions to the common practices in each language. -- Sokkjō 01:33, 27 August 2023 (UTC)

It's also wrong when there are no descendants at the target entry. Desctree reads in the whole page and analyzes the wikitext in order to extract the descendants from the correct language section. This is a colossal waste of system resources when there aren't any descendants to be found.

The module used to just throw a module error in such cases, but I got tired of finding entries in CAT:E because someone removed the descendants from one of the entries somewhere else on the tree. The person removing the descendants had no way of knowing that they were causing a module error in some other entry. I had someone modify the module so it displays an error message that's only visible when you're previewing the entry, and places the entry in a maintenance category for someone like me to fix.

The current setup has its own problems, because people who don't preview the entry when they add {{desctree}} don't have any obvious indication that anything is wrong, aside from a category that one would have to know to look for. Chuck Entz (talk) 00:12, 20 February 2024 (UTC)

Asturian

Please do not create poorly made entries, there is a pronunciation and reference template. Stríðsdrengur (talk) 22:39, 18 March 2024 (UTC)

Hi, can you elaborate more about it? Where can i see the templates? Ekirahardian (talk) 22:41, 18 March 2024 (UTC)

[[Category:Asturian reference templates]], [[Category:Asturian pronunciation templates]]. Stríðsdrengur (talk) 22:43, 18 March 2024 (UTC)

And apparently you're editing a language you don't know, so be more careful. Have a good night. Stríðsdrengur (talk) 22:44, 18 March 2024 (UTC)

• Don't worry about those messages. User:Stríðsdrengur has been going around telling everyone not to edit... Phacromallus (talk) 23:31, 18 March 2024 (UTC)

  I didn't tell them not to edit, just to be more careful, which you don't do either... Stríðsdrengur (talk) 23:33, 18 March 2024 (UTC)