User talk:DerRudymeister
Add topicWelkom
[edit]Welcome
[edit]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 on Wiktionary's page formatting; all entries must conform to it. The easiest way to start off is to copy the contents of an existing same-language entry, and then adapt it to fit the entry you are creating.
- Check out Language considerations to find out more about how to edit for a particular language.
- Our Criteria for Inclusion (CFI) defines exactly which words can be added to Wiktionary; 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.
- If you have any questions, bring them to Wiktionary:Information desk or ask me on my talk page.
- Whenever commenting on any discussion page, please sign your posts with four tildes (
~~~~
) which automatically produces your username and timestamp. - You are encouraged to add a BabelBox to your userpage to indicate your self-assessed knowledge of languages.
Enjoy your stay at Wiktionary! --Lo Ximiendo (talk) 10:03, 18 January 2017 (UTC)
Share your experience and feedback as a Wikimedian in this global survey
[edit]Hello! The Wikimedia Foundation is asking for your feedback in a survey. We want to know how well we are supporting your work on and off 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. You have been randomly selected to take this survey as we would like to hear from your Wikimedia community. The survey is available in various languages and will take between 20 and 40 minutes.
You can find more information about this survey on the project page and see how your feedback helps the Wikimedia Foundation support editors like you. This survey is hosted by a third-party service and governed by this privacy statement (in English). Please visit our frequently asked questions page to find more information about this survey. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email through the EmailUser feature to WMF Surveys to remove you from the list.
Thank you!
Reminder: Share your feedback in this Wikimedia survey
[edit]Every response for this survey can help the Wikimedia Foundation improve your experience on the Wikimedia projects. So far, we have heard from just 29% of Wikimedia contributors. The survey is available in various languages and will take between 20 and 40 minutes to be completed. Take the survey now.
If you have already taken the survey, we are sorry you've received this reminder. We have design the survey to make it impossible to identify which users have taken the survey, so we have to send reminders to everyone. If you wish to opt-out of the next reminder or any other survey, send an email through EmailUser feature to WMF Surveys. You can also send any questions you have to this user email. Learn more about this survey on the project page. This survey is hosted by a third-party service and governed by this Wikimedia Foundation privacy statement. Thanks!
Your feedback matters: Final reminder to take the global Wikimedia survey
[edit]Hello! This is a final reminder that the Wikimedia Foundation survey will close on 23 April, 2018 (07:00 UTC). The survey is available in various languages and will take between 20 and 40 minutes. Take the survey now.
If you already took the survey - thank you! We will not bother you again. We have designed the survey to make it impossible to identify which users have taken the survey, so we have to send reminders to everyone. To opt-out of future surveys, send an email through EmailUser feature to WMF Surveys. You can also send any questions you have to this user email. Learn more about this survey on the project page. This survey is hosted by a third-party service and governed by this Wikimedia Foundation privacy statement.
But then what is burgeren? —Rua (mew) 20:32, 8 March 2019 (UTC)
It does not exist. Do you have any suggestions how the verb should be described? It's not a confix of in-+burger+-en. Because 'in' is not a prefix in this case.--DerRudymeister (talk) 20:42, 8 March 2019 (UTC)
neder-
[edit]I think your recent edits to Nederturk, nederpop, nederjazz and nederwiet are incorrect, this isn't the directional neder but a prefix neder- with the meaning "Dutch (adj.)". This meaning doesn't occur for the stand-alone term, compare kunst- (“artificial”) and kanker-. ←₰-→ Lingo Bingo Dingo (talk) 09:27, 11 November 2019 (UTC)
Yes you're right about that. I will undo those edits. Thanks! --DerRudymeister (talk) 14:14, 11 November 2019 (UTC)
compound vs. affix templates
[edit]Thanks for your recent updates of etymologies with suffixes. But here's a reminder that {{compound}}
does not interpret affixes like -en correctly, you will need {{af}}
or {{affix}}
for that. ←₰-→ Lingo Bingo Dingo (talk) 10:47, 25 February 2020 (UTC)
- Thanks for the message. It seems I forgot about that, good that you point this out. I will try to edit the entries that contain the mistake, but if you encounter more feel free to edit those. --DerRudymeister (talk) 11:04, 25 February 2020 (UTC)
-ierf, -ierp
[edit]The i is short in these combinations, so they were already listed at Rhymes:Dutch/i-. You may want to merge your additions into there. —Rua (mew) 12:30, 14 May 2020 (UTC)
- Thanks for the message, I undid the edits for those entries and put them in the right rhyming categories. That means we're still left with four empty rhyming pages, should these be marked for a merger or deletion? Or can you simply remove them with some moderator magic? --DerRudymeister (talk) 13:10, 14 May 2020 (UTC)
- I've deleted the pages now. —Rua (mew) 13:51, 14 May 2020 (UTC)
Thanks for adding sources!
[edit]DerRudymeister, thanks so much for going around adding sources to existing Proto-Germanic entries. I really appreciate that. Godspeed! --{{victar|talk}}
17:10, 1 October 2020 (UTC)
- Hi Victar, good to hear that it's appreciated! Most of the PGM reconstructions on the wiki can be found the etymogical dictionaries by Kroonen and Orel. I think it's worth the effort to add these references. I'm mostly focusing on verbs for the time being.--DerRudymeister (talk) 14:59, 2 October 2020 (UTC)
- Thanks again. FYI, in
{{R:gem:EDPG}}
,|1=
=|head=
,|2=
=|page=
, and|3=
or|passage=
, so you can just do{{R:gem:EDPG|*hurjan-|259|*harmjan-}}
. --{{victar|talk}}
16:31, 5 October 2020 (UTC)
- Thanks again. FYI, in
Hey DerRudymeister, can you please add |id=
to {{af|gmw-pro|*-jan}}
? So either {{af|gmw-pro|*-jan|id=denominative}}
or {{af|gmw-pro|*-jan|id=factitive}}
. Thanks. --{{victar|talk}}
00:41, 13 December 2020 (UTC)
Moving parameters
[edit]DerRudymeister, I noticed you moving around parameters in derivational templates, i.e. {{af|term1|t1=gloss1|term2|t2=gloss2}}
to {{af|term1|term2|t1=gloss1|t2=gloss2}}
. Any reason for that? -- Sokkjō 16:36, 31 March 2024 (UTC)
- Hi @Sokkjo, thanks for the message. I've added subcategories for -janą and -āną and I was adding those to the entries. I noticed that the order of the parameters is inconsistent on quite a few entries. Either we do it
{{af|term1|t1=gloss1|term2|t2=gloss2}}
or do it{{af|term1|term2|t1=gloss1|t2=gloss2}}
. I don't have a preference, but it should be done in a consistent manner for all entries. Please let me know what you think. DerRudymeister (talk) 16:56, 31 March 2024 (UTC)- Thanks for the reply. If you have a look at T:affix/documentation,
{{af|term1|p1=para1|term2|p2=para2}}
is the exampled method, as well as my preference. -- Sokkjō 17:26, 31 March 2024 (UTC)
- Thanks for the reply. If you have a look at T:affix/documentation,
PWG *-ōn derivatives
[edit]I appreciate your project of adding new PWG *-ōn derivatives. Thanks for doing that. --{{victar|talk}}
23:36, 10 July 2024 (UTC)
Could you take a look at Module:odt-conj? It's broken on a lot of pages. Just a heads-up, when you're working on a production module, it's a good idea to set up some test cases and keep an eye on CAT:E for any errors after you deploy. — Fenakhay (حيطي · مساهماتي) 00:16, 16 August 2024 (UTC)
- I reverted all your changes because they caused a lot of breakage. Benwing2 (talk) 06:26, 16 August 2024 (UTC)
- @Benwing2: It will only cause more errors since they have edited many entries using the new module's syntax. — Fenakhay (حيطي · مساهماتي) 06:28, 16 August 2024 (UTC)
- @Fenakhay Are you sure? There were 68 errors before and only 3 now. Benwing2 (talk) 06:29, 16 August 2024 (UTC)
- Hmm, I see, they will show up. OK I will hack
{{odt-conj-wk2}}
(and{{odt-conj-wk1}}
,{{odt-conj-wk3}}
) to do nothing. What a mess. Benwing2 (talk) 06:32, 16 August 2024 (UTC)- As a general rule, DerRudymeister, you should develop your modules in userspace and only deploy to production once you've got everything working. Don't do your development directly on the production module. Benwing2 (talk) 06:35, 16 August 2024 (UTC)
- @Fenakhay, Benwing2. Sorry to have caused so much trouble. The edits that I made yesterday to adjust the strong verb inflection, caused the issue. I shouldn't have left it in that state, it required more development. In the future I won't do development in the production modules, I promise. But I believe you have reverted too far back. The weak verb inflection that I created before that, actually worked fine. Which is also why I made all weak verb entries make use of the modules. If you will allow it, I will revert back to the situation on the 12th of August not the situation of the 4th February, because this broke the weak verb entries. Please let me know what you think. DerRudymeister (talk) 12:25, 16 August 2024 (UTC)
- That is fine, I didn't know what was working and what not so I reverted everything. Benwing2 (talk) 19:06, 16 August 2024 (UTC)
- @Fenakhay, Benwing2. Sorry to have caused so much trouble. The edits that I made yesterday to adjust the strong verb inflection, caused the issue. I shouldn't have left it in that state, it required more development. In the future I won't do development in the production modules, I promise. But I believe you have reverted too far back. The weak verb inflection that I created before that, actually worked fine. Which is also why I made all weak verb entries make use of the modules. If you will allow it, I will revert back to the situation on the 12th of August not the situation of the 4th February, because this broke the weak verb entries. Please let me know what you think. DerRudymeister (talk) 12:25, 16 August 2024 (UTC)
- As a general rule, DerRudymeister, you should develop your modules in userspace and only deploy to production once you've got everything working. Don't do your development directly on the production module. Benwing2 (talk) 06:35, 16 August 2024 (UTC)
- Hmm, I see, they will show up. OK I will hack
- @Fenakhay Are you sure? There were 68 errors before and only 3 now. Benwing2 (talk) 06:29, 16 August 2024 (UTC)
- @Benwing2: It will only cause more errors since they have edited many entries using the new module's syntax. — Fenakhay (حيطي · مساهماتي) 06:28, 16 August 2024 (UTC)
Module:odt-conj (2)
[edit]Because you've done quite some work on Module:odt-conj lately, I was wondering if you can make it so that the letter combination -cw- gets converted to -qu- in the past tenses of the verb 'cuman' (for example: cwam -> quam). Unfortunately I don't know how to do this myself, so I was hoping you can help. Preupellor (talk) 22:55, 6 November 2024 (UTC)
- @Preupellor. Well spotted! I've edited the module, so this is now fixed.