User talk:ZxxZxxZ

Definition from Wiktionary, the free dictionary
Jump to: navigation, search

Archives: April 2012 – July 2013

"Smart" link processing for Module:headword[edit]

The work on this module is more or less done, but I would like to add the full functionality of the link processing in Module:links to it. In particular, if the head= parameter or any of the words given as inflections contain links, add sections to them when possible. Otherwise, the head= parameter should remain unlinked, but a "default" link should be made out of the inflections. Both should also support reconstructed entries. If possible, links to the "current" page should not be links (like {{l-self}}). Language and script tags should not be added unless there is a way to preserve the current behaviour (concerning face= in particular). I can elaborate that further with examples if necessary. Can you help out or tell me what I would need to do? Module:links currently has no documentation about the functions it exports, so I don't know how to use it very well, or what to watch out for. —CodeCat 14:17, 16 July 2013 (UTC)

For inflections, remove lines 81-84 and use links.language_link(text, alt, lang, id), where lang is the language code and id should be the name of the language, languages[lang].names[1]. I've made some changes in Module:User:ZxxZxxZ/links, and suggest you to update Module:links based on this, this way you can omit id, and the third argument will be langinfo, or languages[lang]. The only problem would be avoiding self-linking, I had written its code (language_link_self), it works, but I haven't added it to the module for some reason (I'll work on this later). For headword, you can use something like if text:find("[[", nil, true) then language_link(text, alt, langinfo) end in format_headword, right before calling the script templates. However, note that language_link also checks for this condition, which means the else block in language_link will be redundant here. --Z 16:06, 16 July 2013 (UTC)
Like this? diff. It is causing some script errors on pages like back of beyond, but I'm not sure why. Should the alt parameter be something else than nil? I don't know what else could be put there. —CodeCat 16:39, 16 July 2013 (UTC)
Never mind, I fixed it. I copied your code but it was missing the id parameter. —CodeCat 16:42, 16 July 2013 (UTC)
It works now without errors, but it's not quite doing what it should. It's a bit strange. If I type {{head|nl|noun|head=[[test]] [[een]]|plural|[[twee]] [[drie]]}} then the inflections do have #Dutch added to them, but not the links in the headword. —CodeCat 16:50, 16 July 2013 (UTC)
Ok, got it working. Thanks for your help! —CodeCat 16:53, 16 July 2013 (UTC)
Found a bug that's probably related. Look at kwa; headwords are showing () after them now. —Μετάknowledgediscuss/deeds 18:07, 16 July 2013 (UTC)
I don't see it..? —CodeCat 18:40, 16 July 2013 (UTC)
Nor do I now. I guess it was just lagging. —Μετάknowledgediscuss/deeds 18:58, 16 July 2013 (UTC)

Babel on userpage[edit]

Hey there ZxxZxxZ. Would you mind adding some babel userboxes to your userpage so we know what languages you are proficient in? Thanks, Razorflame 16:00, 18 July 2013 (UTC)

Hi, added. --Z 10:29, 19 July 2013 (UTC)
Thank you! I will change my vote from Abstain to Support now on your RfA :) Razorflame 22:19, 19 July 2013 (UTC)

Question...[edit]

The function template_l_xform currently doesn't have any information about its usage. What does it do, and what is it intended for? I noticed it's used on inflection tables and apparently it adds links to the word in the same way that language_link does. So can they be merged? Also, as a sidenote, I tried to copy the code for "term" from your user page to the main module, and I made a few adjustments as well. I hope I did it right. —CodeCat 21:07, 20 July 2013 (UTC)

It was added by Kephir and has been used in {{t-SOP}}. Currently, its only unique feature is that it can wikilink words of the given text separately (based on white spaces, etc.): {{t-SOP|el|οικιακή οικονομία}} > οικιακή οικονομία; but I don't think it's a good idea as not every word should be wikilinked, and sometimes we want to link to a title which contains white spaces (say, a phrase or a compound verb), so why not simply use the same method in other linking templates: {{t|el|[[οικιακή]] [[οικονομία]]}}, {{head|en|verb|head=to [[do]]}}, and the text will be handled by language_link. --Z 22:05, 20 July 2013 (UTC)
I just did that. But that function is being used in other templates too, like {{pl-decl-noun/wlink}}. Does it actually make sense to use it there? —CodeCat 22:30, 20 July 2013 (UTC)
I replaced it with Template:l. --Z 22:45, 20 July 2013 (UTC)
{{t-SOP}} is nominated for deletion now, because it's redundant to the other translation templates that now also support links. Can I safely add error("This function is deprecated") to template_l_xform once {{t-SOP}} is no longer used anywhere? —CodeCat 22:55, 20 July 2013 (UTC)
Yes. --Z 23:03, 20 July 2013 (UTC)

𐡁𐡁𐡀[edit]

Any objection to changing the language header to just "Aramaic"? DTLHS (talk) 22:41, 20 July 2013 (UTC)

No, let's change it. --Z 22:48, 20 July 2013 (UTC)

Template talk:l#diacritic removal is broken now[edit]

What do you think is the best way to fix that? Turn the parameter back into lang? Or supply both lang and langinfo, but with langinfo allowed to be nil? —CodeCat 01:22, 21 July 2013 (UTC)

What about adding a field for language code to langinfo? --Z 01:28, 21 July 2013 (UTC)
That can work too, but making langinfo an optional parameter may be more convenient? —CodeCat 01:30, 21 July 2013 (UTC)
Hmm I don't like having both lang and langinfo there. I think we should make it language-code-based, or add language code to langinfo. --Z 01:40, 21 July 2013 (UTC)

Wiktionary:Beer parlour/2013/July#Can we phase out the script code templates?[edit]

This probably interests you... —CodeCat 01:49, 24 July 2013 (UTC)

sysophood[edit]

Welcome to sysophood. Please add an entry at Wiktionary:Administrators.

May I ask that you always have a second session open on Recent Changes whenever you are editing Wiktionary. You may mark good edits as "patrolled", revert vandalism and stupidity by either deleting new entries or by using the "rollback" function. You may block vandals at your own discretion.

Note: As there are times when no sysop is active, it would be useful if you start your patrolling from the time you last left the system. Cheers. SemperBlotto (talk) 12:54, 25 July 2013 (UTC)

Welcome to the team. — Ungoliant (Falai) 13:01, 25 July 2013 (UTC)
Thanks. --Z 14:48, 25 July 2013 (UTC)
Don't patrol; it's a waste of time. — [Ric Laurent] — 20:16, 25 July 2013 (UTC)
Says the sysop that's almost completely inactive. Razorflame 20:20, 25 July 2013 (UTC)
I have a life outside of the internet. Wiktionary's "no-bosses and everybody gets a say" format is not conducive to the production of a worthy product. Nothing is planned sufficiently and everything changes after a month or a year, anyway, so really wiktionary is a fun hobby that can be helpful in studying languages, but it will never be Langenscheidt or Routledge. You yourself have made a lot of piss poor edits, so I don't know why you would insert your nose in this particular area. — [Ric Laurent] — 14:01, 30 July 2013 (UTC)

diff[edit]

I've undone your edit because, while putting alternative forms up the top is the norm for normally-scripted languages, we don't actually do it that way in Egyptian (cf. Wiktionary:About Egyptian). The reason for this is that most words will have many alternative hieroglyphic spellings that usually represent the same transliteration - this is par for the course in Egyptian, and so we just list them in a table under Usage notes. This is 'curret consensus', but if you think that it should be changed, you're welcome to bring it up in the BP - after all, 'current consensus' in Egyptian is just User:Furius and I =P. Cheers. Hyarmendacil (talk) 06:49, 27 July 2013 (UTC)

Hehe, ok. --Z 16:33, 27 July 2013 (UTC)

New {{term}}[edit]

When is {{term}} going to get the extra features of {{term/t}}? I am growing impatient :) --Vahag (talk) 14:45, 28 July 2013 (UTC)

 :) We're working on it, the code is not perfect yet and needs some work before being ready to be used in more templates. --Z 17:08, 28 July 2013 (UTC)

I want to report a problem. Because of some differences between {{l}} and {{term}}, this revision categorizes into Category:Middle Persian entries which need Pahlavi script, while Baghdad is in Category:Middle Persian entries which need Inscriptional Pahlavi script. --Vahag (talk) 08:05, 30 July 2013 (UTC)

That's because the language name in {{rfscript}} doesn't match the name in {{Phli/name}}. All of this will be sidestepped when Wiktionary:Beer parlour/2013/July#The script request categories is done, though. Then the category will be Category:Middle Persian terms needing native script. —CodeCat 11:56, 30 July 2013 (UTC)

Z, if you think it's ready, can you make the change to {{term}}? —CodeCat 11:40, 1 August 2013 (UTC)

Are you sure that your recent edits work? (I haven't checked them exactly, I'm sure about the rest of the code) --Z 20:58, 1 August 2013 (UTC)
{{form of}} already uses it, as do {{termx}}, {{compound}}, {{prefix}} and {{suffix}}, and there are no errors except for a few occasional ones because the call to {{termx}} is missing a *. So I think it's ready. —CodeCat 21:29, 1 August 2013 (UTC)
OK, I'll Lua-ize it now. --Z 21:31, 1 August 2013 (UTC)
Shouldn't we change the "template" parameter to "face" as well? The naming is inconsistent now, as its corresponding variable is named "face". --Z 21:41, 1 August 2013 (UTC)
If you want, yes. It should be empty (nil) for {{l}} if possible. Technically this means we could make a version of {{l}} that makes headword-style links, too. :) —CodeCat 21:54, 1 August 2013 (UTC)
That's true, done. --Z 22:09, 1 August 2013 (UTC)
Just wanted to say I still haven't done it because I'm waiting for Category:Pages with script errors to be emptied, so that we can find any possible error more easily. --Z 00:13, 2 August 2013 (UTC)
MewBot is doing null edits on those entries to clear it out, most of it is done already. So I think it's ok. —CodeCat 00:19, 2 August 2013 (UTC)
Using action=purge must be faster than this way (which downloads the page content and send it to the server) if you can do it. --Z 22:37, 5 August 2013 (UTC)

A while ago I added automated character stripping for Armenian punctuation, namely <՞> <՜> <՛>, <՟>, but that has stopped working. Also, overriding manual transliteration for hy and xcl has stopped working. What should I do? --Vahag (talk) 22:17, 5 August 2013 (UTC)

The character stripping part apparently works well: {{term|lang=hy|abb՞}} > abb՞ (abb?), I fixed the issue about overriding manual transliteration. --Z 22:35, 5 August 2013 (UTC)
But not when the character is at the middle of the word. Try ab՞b (ab?b). --Vahag (talk) 23:08, 5 August 2013 (UTC)
But are they really used at the middle of the word? If so, we should add them to Module:languages instead (entry_name). --Z 23:43, 5 August 2013 (UTC)
Yes, they are placed over the stressed vowel and not at the end of the sentences as in European languages. How do I add them to Module:languages? --Vahag (talk) 07:28, 6 August 2013 (UTC)

Form-of templates[edit]

I was going to convert these to Lua, but then I realised that most of these are really just wrappers around {{term}} (in compatibility mode). They take the same parameters, and all that happens after that is wrapping it in <span class='use-with-mention'> with a bit of descriptive text. I converted {{form of}} to use {{term/t}} to demonstrate this. So is this really worth devoting a whole module to? —CodeCat 20:52, 31 July 2013 (UTC)

We can create a small function for it in Module:links, but since the template is not heavily used in a page, I think we should simply use {{term}} in the template. --Z 21:48, 31 July 2013 (UTC)
I realised that there are some form-of templates that are more intricate, like {{alternative form of}}. Some also add categories, which in turn means using format_categories in Module:utilities. And if some of the form-of templates are better off being converted to Lua, then we might as well convert all of them. Besides, thanks to the invisible "parameter passing" that templates do when invoking modules, if all form-of templates invoke modules directly, we can easily add more parameters to them if we decide to. This is a major problem with the current ones: each one was updated on its own so they all became out of sync and some supported parameters that others didn't, and it is quite a mess... —CodeCat 21:54, 31 July 2013 (UTC)
Yes, if they are so similar to each other, their code should be definitely centralized. I think we should put its function in another module (in order not to make Module:links too big) and use template_l_term there (as you know, we have to pass tables to it...). --Z 07:24, 1 August 2013 (UTC)

A problem with Template:suffix[edit]

Sometimes it's hard to foresee problems like this and even harder to solve them. This template has become unusable for reconstructed languages, because it adds a - before the * that is needed for reconstructed links, and the term then begins with -*. See Appendix:Proto-Germanic/alatjaną. Do you have any ideas for working around this? The most "correct" way, I think, would be to add the - to the parameter so that you always write the *- in the entry, but that would require updating lots of entries. On the other hand, if we do this, then we might as well abandon {{suffix}} altogether and use {{compound}}, because that template (when converted to Lua) can detect the presence of - and act accordingly. We could also get rid of {{prefix}} and {{confix}} too then. —CodeCat 21:20, 2 August 2013 (UTC)

It's easy to Lua-ize {{compound}} in such a way that works with initial "-" and "*-" (and therefore we would not need {{suffix}}), but we can't get rid of {{prefix}} and {{confix}} (as you know, final hyphen is not used only for prefixes, such as "al-" in your example, which is apparently a stem), is that ok? --Z 17:42, 3 August 2013 (UTC)
I made a post in the BP about merging them all into {{compound}}, but I didn't realise that not all terms ending in - are prefixes. That's kind of a shame because it seemed like a nice idea. —CodeCat 17:58, 3 August 2013 (UTC)
Yeah :( --Z 18:15, 3 August 2013 (UTC)
I converted {{compound}} to Lua anyway (Module:compound), and that was surprisingly easy to do thanks to all the other support code we already have. I wonder if we should start writing some kind of central page documenting all of these "libraries" so that people know they can use them. —CodeCat 18:21, 3 August 2013 (UTC)
Maybe we should remove documentations of our major modules and move their content to a single page? Otherwise we can list them in WT:LUA with a brief description about each module. --Z 18:54, 3 August 2013 (UTC)
We could introduce a new parameter for {{compound}}, "isrootN=1" or "notaffixN=1", which says that a part of a compound should not be interpreted as an affix. For *alatjaną it would then become: {{compound|*al-|isroot1=1|t1=to drive, move|*-atjaną|lang=gem-pro}}. Do you think this is workable? —CodeCat 18:31, 3 August 2013 (UTC)
That works, but since adding a parameter makes learning and using the template a bit harder, people may think it is easier to have a separate template as before. We should also make the title shorter. By the way, "compound" is not accurate I think, when we have an affix, we usually call the word a derivation, an affixed form, but not compound. --Z 18:54, 3 August 2013 (UTC)

Lua variable dump[edit]

I made a module Module:debug with (for now) a single function. This will produce a string that contains a dump of the value in a Lua-parseable format, recursing to show all values in a table. I thought it might be useful to you. —CodeCat 00:02, 7 August 2013 (UTC)

Good idea. --Z 00:06, 7 August 2013 (UTC)

Appendix:Proto-Slavic/bogynji[edit]

{{suffix}} is adding the wrong category in this entry. It's happening because prepare_title strips diacritics but it also adds the prefix for Appendix pages. That isn't wanted in this case; it should only do the diacritic stripping. Do you know of a way to solve this neatly? —CodeCat 13:31, 14 August 2013 (UTC)

I think we should create another function and move "Remove punctuation" and "Replace diacritics and other characters ..." parts to that function, and call the new function in prepare_title, before the "Link to appendix for reconstructed terms ..." part (these parts are currently after "Link to appendix for reconstructed terms ...", but should be before it), and in Module:compound, we will call this new function instead of prepare_title. --Z 13:45, 14 August 2013 (UTC)

fight#Translations[edit]

Hi,

Do you mind checking and romanising the Persian translations (verb) please? Please add the noun translations if you can, too. --Anatoli (обсудить/вклад) 00:43, 20 August 2013 (UTC)

Hi, done. --Z 04:41, 20 August 2013 (UTC)
Thanks :) --Anatoli (обсудить/вклад) 05:03, 20 August 2013 (UTC)

What to do when automatic transliteration isn't wanted?[edit]

There are some cases where automatic transliteration isn't wanted. How should this be disabled? —CodeCat 01:35, 26 August 2013 (UTC)

I think Greek "Αντιγκέα" (Adygea) should be manually transliterated as "Adigéa", not "Antigkéa" (automatic), like many loanwords. "ντ" and "γκ" are pronounced /d/ and /g/ in loanwords. There are some bits and pieces in WT:AEL and Module:el-translit but I'm not sure about the exact rules at Wiktionary for Greek. --Anatoli (обсудить/вклад) 04:45, 26 August 2013 (UTC)
So maybe we shouldn't override manual transliteration for Greek, let's discuss it with other users such as User:Saltmarsh as well. --Z 08:23, 26 August 2013 (UTC)
I don't really agree with having manual transliteration being overridden by an automatic one. At best, I think we should track such cases with a category, but those writing the entries should always have the final say over those writing the transliteration modules. —CodeCat 10:59, 26 August 2013 (UTC)
I agree with not to override manual transliteration if we remove all manual transliterations for languages that have automated transliteration first. --Z 12:31, 26 August 2013 (UTC)
A general good solution is passing an empty string to "tr", it's easy to use and easy to remember. Module:links is adding these terms to Category:Terms passing empty string to tr to make things ready if we decide to do this. --Z 08:23, 26 August 2013 (UTC)
I seldom work with Greek, only some occasional translations. Perhaps Greek editors should be consulted. I'll just follow the development. --Anatoli (обсудить/вклад) 08:32, 26 August 2013 (UTC)
Passing an empty string is not such a good idea, because it means that the module has to make a distinction between empty and not present. I think using tr=- is better. —CodeCat 10:57, 26 August 2013 (UTC)
An alternative is to use another template. The good news is that we already have one, {{l-self}}. —CodeCat 11:18, 26 August 2013 (UTC)
Let's avoid creating another template. I agree with tr=-, which is safer than tr=. --Z 12:31, 26 August 2013 (UTC)
Did you only read half of my message? —CodeCat 13:00, 26 August 2013 (UTC)
{{l-self}} is for inflection tables and headword lines, according to the docs. Is that, inflection tables and headword lines, the only places in which we may want to remove automated transliteration? --Z 13:17, 26 August 2013 (UTC)
quoted from the top' ":I think Greek "Αντιγκέα" (Adygea) should be manually transliterated as "Adigéa", not "Antigkéa" …"
(I'm sorry to let this run before jumping in) The place for pronunciation is in the "Pronunciation" section - the transliteration is just that "transliteration": an attempt to reproducibly represent Greek letters in Roman form. Can we have some exceptions where auto-translit fails. — Saltmarshαπάντηση 15:07, 28 August 2013 (UTC)
Apparently you have cases like "μπ" (i.e. "mp") = "b" and "ντ" (i.e. "nt") = "d" in the translit module, so the attempt to transliterate letter by letter in Roman form is not always consistent. That's fine to tweak the transliteration to make it practical and useful, especially with unpredictable exceptions. Imagine the use of transliterating English words in Greek letter by letter, ignoring the pronunciation. It's possible but is it useful? --Anatoli (обсудить/вклад) 15:25, 28 August 2013 (UTC)
But it is consistent (isn't it?) "μπ": is always = "b" initially and always "mp" medially (see: μπαμπάκι (bampáki)) which is handled as it should be. — Saltmarshαπάντηση 16:28, 28 August 2013 (UTC)

Links in head[edit]

Will you please stop doing that? Your edits are causing script errors, and lots of them too. What is it exactly that you're trying to do? Why isn't Category:Link with section right? —CodeCat 13:36, 26 August 2013 (UTC)

Sorry about script error.
I just opened your talk page to explain that. I do know Category:Link with section will cover entries in Category:Headword with transliteration in head, but most of those entries are not what I'm looking for, and are not urgent to be fixed (actually there's nothing to fix in most of them, using section in head is just a redundancy issue), but the entries that I'm looking for (in Category:Headword with transliteration in head) really need to be fixed and it's an important issue, so I dedicated a new category for them. These entries are the ones that have used {{l}} inside head, which is fail especially if {{l}} generates transliteration for that language. --Z 13:43, 26 August 2013 (UTC)
Yes, the category contains those too, see céad míle fáilte. The script error was caused because you were using "find" on head, but head was nil. —CodeCat 13:47, 26 August 2013 (UTC)
But even céad míle fáilte is not what I'm looking for, there's nothing to fix because {{l}} doesn't add transliteration there (my category excludes these entries). --Z 13:52, 26 August 2013 (UTC)
Ok, you are looking for something more specific. Do you think my category is useful too, though? —CodeCat 14:26, 26 August 2013 (UTC)
Yes, it's good to get rid of those redundant sections and {{l}}s to have a more clean code. --Z 14:30, 26 August 2013 (UTC)

Problems with automatic transliteration and embedded links[edit]

Wiktionary:Grease_pit/2013/August#.7B.7Bt.C3.B8.7D.7D_or_.7B.7Bt.7D.7D_issues_spotted Would you know how to help here? —CodeCat 01:52, 27 August 2013 (UTC)

Problem with links to same page when the term has diacritics[edit]

Thread:User_talk:CodeCat/la-noun strangeness Could you help with this? It should just display black text here but it's not. —CodeCat 12:51, 17 September 2013 (UTC)

Middle Persian in Latin script[edit]

Middle Persian isn't listed in Wiktionary:Votes/pl-2011-09/Romanization of languages in ancient scripts 2 so strictly speaking, any Middle Persian in Latin script is a candidate for immediate deletion. It could of course be possible to add more languages to that list, given that Middle Persian uses an obscure script. But that's hypothetical; de jure these are invalid. Mglovesfun (talk) 15:40, 17 October 2013 (UTC)

I'm creating them in Latin script because Book Pahlavi is not yet supported in unicode (these entries will be moved in future). --Z 15:58, 17 October 2013 (UTC)

wʾčʾlkʾn'[edit]

Is ' at the end a mistake? You're linking to wʾčʾlkʾn from վաճառական (vačaṙakan) and بازرگان. --Vahag (talk) 21:24, 17 October 2013 (UTC)

wʾčʾlkʾn was a mistake, I corrected them, thanks for pointing that out. --Z 04:49, 18 October 2013 (UTC)

Script detection[edit]

Isn't Module:links supposed to do script detection? If so, can all cases of Armenian in Latin script be found? --Vahag (talk) 21:40, 27 October 2013 (UTC)

Yes, I have plans to add a feature to the templates to detect invalid characters for each language/script (including IPA). --Z 16:28, 30 October 2013 (UTC)
OK, will wait for the implementation. --Vahag (talk) 16:52, 30 October 2013 (UTC)
Done, these entries will be listed at Category:Terms using script detection fallback/hy. --Z 20:01, 26 December 2013 (UTC)
Great! I'll cast my fishing line and wait for the little fishies to appear in the category. --Vahag (talk) 20:12, 26 December 2013 (UTC)
The category catches many false positives because of the character "—", invalid for Armenian. Where is the list of valid characters? I need to add some punctuation there. --Vahag (talk) 20:40, 26 December 2013 (UTC)
The list of characters is at Module:scripts/data, but if we add em dash to that list it will mess up other codes, because the character is not used only in Armenian. Instead I tried to fix this by changing Template:hy-decl-noun (my change also fixed a minor issue about showing the dashes). --Z 07:16, 27 December 2013 (UTC)
I didn't know about ifeq's functionality. The changes are perfect, thank you. --Vahag (talk) 08:44, 27 December 2013 (UTC)

Talk:ليمون[edit]

Take a look. — Ungoliant (Falai) 12:07, 31 October 2013 (UTC)

نار[edit]

How do you think we should handle cases of tanween assimilation in the transcription? For نَارًۭا لَّعَلِّىٓ, I think naral-laʿallī makes the most sense, but you seem to want nara l-laʿallī, which I think makes no sense at all. --WikiTiki89 17:54, 1 November 2013 (UTC)

We should not represent that in transcription to start with if you ask me, so it should be nāran laʿallī (I didn't change it to nāran laʿallī because I didn't want to change the transcription system you used; BTW you should change jaḏwatin mina to jaḏwatim-mina, for the sake of consistency). --Z 18:16, 1 November 2013 (UTC)
I already fixed that. I think we should indicate it, after all transcriptions are for showing what is written in the Arabic, and that is what is written in the Arabic. --WikiTiki89 18:33, 1 November 2013 (UTC)
Actually, I think maybe you are right, but then the question is should we show assimilation of الـ? --WikiTiki89 19:00, 1 November 2013 (UTC)
According to WT:AR TR, "ال always gives al- regardless of elision and sun and moon letters rules", I think it's a good practice. --Z 20:23, 1 November 2013 (UTC)
Ok, but that page needs serious revising anyway. --WikiTiki89 20:54, 1 November 2013 (UTC)

Wiktionary talk:About Arabic[edit]

Hi Z,

You may be interested in latest discussions there. --Anatoli (обсудить/вклад) 03:26, 4 November 2013 (UTC)

vein#Translations[edit]

Hi Z,

Could you transliterate Persian "سیاه‌رگ" at vein#Translations, please? --Anatoli (обсудить/вклад) 08:28, 12 November 2013 (UTC)

Hi, done. --Z 08:36, 12 November 2013 (UTC)

šamšir and his friends[edit]

Hi! What is your source for Parthian sfsyr (safsēr, sword)? None of my sources know about it, so they have to derive սուսեր (suser) from Syriac ܣܦܣܝܪܐ (sap̄sērāʾ). Parthian fits much better. We could do a little original research and claim the word is from Parthian, if it is indeed attested. Also, in general, could you please list your sources in a ===References=== section, like me and User:334a do? --Vahag (talk) 11:02, 12 November 2013 (UTC)

Hi, Parthian sfsyr (safsēr, sword) and the Middle Persian form have been mentioned in this article (page 34) as the root of the Syriac term. The article says "parth." before the word sfsyr, but it is a Manichaean Parthian word (judging by the spelling), it is attested in a Manichaean Parthian manuscript. Yes, I often forget adding the refernces that I've used, I added them to شمشیر and սուսեր. --Z 12:25, 12 November 2013 (UTC)
Thanks, references make Wiktionary much more valuable. --Vahag (talk) 13:22, 12 November 2013 (UTC)
Hi Z! I miss workin with you. You sane, sane person. Why can't there be more of you? And Vahag. Vahag, you know science. Clones on the double, man. — [Ric Laurent] — 17:10, 12 November 2013 (UTC)
Hey, HAHA, nice to see you around. --Z 17:38, 12 November 2013 (UTC)
We miss you too, buddy. Edit more often. --Vahag (talk) 18:10, 12 November 2013 (UTC)
I do a little bit here and there lol.... Trying to make myself of some small use in Armenian of recent. — [Ric Laurent] — 18:22, 12 November 2013 (UTC)
Make yourself useful in Arabic, Ric, which is almost dead here, since you stop adding conjugation templates. I'll get back to it with the module but it will take me forever. For me to work with Arabic I need books, quiet and motivation, which is often hard to get at one time. I can only work from home on it. For Armenian we have Vahag. Sorry, but he can do it better. :) Of course you can do it for your own benefit. --Anatoli (обсудить/вклад) 23:37, 12 November 2013 (UTC)
Hey man Arabic is hard lol. And yes, my attention to Armenian is highly selfish. :) It's hard to get excited about doing too much here the way some people comport themselves. Not that I'm the most agreeable person on planet Earth, but you know. :D — [Ric Laurent] — 23:45, 12 November 2013 (UTC)

Dari and Persian[edit]

Hi,

Do you think Dari can be merged with Persian? See Wiktionary:Requests_for_moves,_mergers_and_splits#Persian, Dari, etc. {{context|Dari}} can still be used. CC Dijan (talkcontribs). --Anatoli (обсудить/вклад) 04:56, 4 December 2013 (UTC)

Pahlavi dictionary[edit]

This Middle Persian-Farsi-Armenian-Russian-English dictionary published in Armenia may be useful in your work. Just letting you know about it. I can make a reference template, if necessary.--Vahag (talk) 17:25, 26 December 2013 (UTC)

Thanks for sharing it, it must be a good source, I'm downloading it (it may take a year or two though :))) --Z 17:30, 26 December 2013 (UTC)
Mullahs blocking the Internet? :) If you don't manage to download it, I'll send you the .pdf by email. --Vahag (talk) 17:39, 26 December 2013 (UTC)
LOL that's ok, just 20 minutes remaining (even if you email it, still I have to download the attached file). --Z 17:42, 26 December 2013 (UTC)

Module:links/testcases[edit]

This page is meant to test for script errors, but could you change it so that the page doesn't trigger a real script error? It's been in Category:Pages with script errors for a while now... —CodeCat 04:26, 12 January 2014 (UTC)

Kind of strange because in fact there's no real script error there, since we have used iferror. Anyway, after recent changes to Module:links only one test triggers script error, which was not very important, so I removed it. --Z 15:07, 12 January 2014 (UTC)
It's doing it again. It's really strange that there is no error on the page, but it still says there is one. —CodeCat 14:13, 21 January 2014 (UTC)
There are several similar strange cases in Category:Pages with script errors/hidden, such as User:-xfi-/common.js, we should report this at Bugzilla. --Z 07:40, 22 January 2014 (UTC)

[1][edit]

The diacritics seem to indicate muhassal, not sure whether they're wrong or the transcription is? Ƿidsiþ 15:06, 19 January 2014 (UTC)

It was correct. As you know, kasra (i) is shown by a diagonal line below the letter. However, if there's already a shadda on the same letter, this diagonal line is usually put above the letter, and immediately below shadda (fatha is also put above the letter, but immediately above shadda), most fonts follow this rule, and I guess this is what you are seeing on that page. --Z 16:14, 19 January 2014 (UTC)

Script error[edit]

Hey there! Would you happen to know why the script name is repeating 9 times in the main language categories and why it only shows the first script? (For example, take a look at Category:Persian_language). --Dijan (talk) 21:52, 20 January 2014 (UTC)

Hi, Category:Persian_language looks ok, apparently the issue has already been fixed. --Z 07:36, 22 January 2014 (UTC)
Yeah, it looked like it was fixed an hour or so after I posted this. Sorry for bothering you. --Dijan (talk) 20:33, 22 January 2014 (UTC)
One more question, possibly related to this. When linking words that contain the Devanagari visarga character via Template:l, it is automatically redirected to the entry without a visarga. For example, when you link छः, it automatically changes it to . --Dijan (talk) 08:46, 27 January 2014 (UTC)
The behavior is intentional, it is from line 50 of Module:languages, it contains a set of characters that should be removed from all entry names, and visarga is among them. I don't know who added it and why, but if you are sure it shouldn't be there, let's remove it. --Z 09:21, 27 January 2014 (UTC)
Thanks. I have no idea, but I've gone ahead and removed it. --Dijan (talk) 09:47, 27 January 2014 (UTC)
Hello again. Is this also the same reason why Turkish âşık automatically links to aşık? --Dijan (talk) 08:46, 6 February 2014 (UTC)
Yes, I made a change to Module:languages/data2, now it links to âşık. --Z 08:51, 6 February 2014 (UTC)

Thanks for etymology help![edit]

ZxxZxxZ, thanks a lot for your help with Farsi and Arabic etymology! You are helping a lot.

Cheers, Borovi4ok (talk) 08:37, 3 February 2014 (UTC)

You're welcome! --Z 10:42, 3 February 2014 (UTC)
Hi, can you please have a look at һәйбәт#Etymology?
I suspect this might be of Persian descent. Would be great if you could establish or refute it. Borovi4ok (talk) 08:27, 11 February 2014 (UTC)
Hi, done. --Z 09:10, 11 February 2014 (UTC)
Thanx a lot! Borovi4ok (talk) 09:26, 11 February 2014 (UTC)

Hi,

Can you please check the Persian source at һарай#Etymology - does it have the meaning of "cattle shed" alongside with "palace"? Borovi4ok (talk) 14:40, 27 February 2014 (UTC)

Hi, no, I couldn't find such sense for the Persian word. --Z 15:51, 5 March 2014 (UTC)

kʾlwʾn'[edit]

It's a Middle Persian entry, but I'm fairly sure Middle Persian didn't use the Latin script. Can you fix it? --WikiTiki89 23:44, 15 February 2014 (UTC)

We did not hold a formal vote but Middle Persian in Latin should be allowed by the rationale of this Vote. The transliteration table is at Wiktionary:PAL TR. Note also that Psalter Pahlavi, Book Pahlavi and Manichaean scripts are not yet available in Unicode. --Vahag (talk) 06:50, 16 February 2014 (UTC)
I was not aware of that vote and thought that romanizations can only be entries for languages that do not have full Unicode support, such as Ancient Egyptian. Why can't we use Inscriptional Pahlavi or Parthian? The rationale of that vote can be incorporated by having soft redirects from romanizations to actual entries in the correct script. --WikiTiki89 22:18, 16 February 2014 (UTC)
Because not all words are attested in Inscriptional Pahlavi or Inscriptional Parthian. --Vahag (talk) 06:40, 17 February 2014 (UTC)
But how different are they? As long as there is a clear correspondence between them it doesn't matter. For example, in the Latin script we don't differentiate between Roman, Insular, Fraktur, etc. And in Hebrew we don't differentiate between block script, cursive, or Rashi script. --WikiTiki89 06:54, 17 February 2014 (UTC)
They are quite different. Even the number of graphemes is different. Read Pahlavi scripts. There are proposals to include Book Pahlavi and Psalter Pahlavi in Unicode. --Vahag (talk) 07:27, 17 February 2014 (UTC)

About your revert in here[edit]

In which cases is the template buggy? I'm not native Persian so please let me know. --kc_kennylau (talk) 09:38, 22 March 2014 (UTC)

ā is pronounced short [ɒ] before final n and m in Iranian Persian, also the template interpreted ' as /ʔ/ instead of stress mark. --Z 09:43, 22 March 2014 (UTC)
I can always fix the problem just tell me the problems and I'll hack into the templates :) --kc_kennylau (talk) 09:48, 22 March 2014 (UTC)
It's easy to fix, I haven't fix it because I'm working on a new, Lua version of the template. --Z 09:54, 22 March 2014 (UTC)
Can I help you? --kc_kennylau (talk) 09:55, 22 March 2014 (UTC)
The code is actually ready, I just need some certain phonological information about some accents. --Z 10:04, 22 March 2014 (UTC)

Persian translation of tsar[edit]

Can you verify this edit? --WikiTiki89 17:36, 6 April 2014 (UTC)

کهربا[edit]

Hello,

what is the sense of removing the "Descendants" section? Borovi4ok (talk) 06:47, 16 April 2014 (UTC)

That section is for things like Latin to French, Italian, Romanian. Old English to modern English. It's not for borrowings. Bashkir isn't a descendant of Persian. — [Ric Laurent] — 02:05, 17 April 2014 (UTC)
It seems to be used that way a lot though. Is there a consensus on the issue? --WikiTiki89 02:10, 17 April 2014 (UTC)
Hey Ric, I disagree. Bashkir isn't a descendant of Persian but words derived from Persian are its descendants. E.g. words listed at भाषा#Sanskrit are descendants of Sanscrit, even if languages only borrowed from it and are not direct descendants. Yes, it is used that way a lot. There's no policy as such but a common practice. --Anatoli (обсудить/вклад) 02:57, 17 April 2014 (UTC)
Either the section should be renamed or it should be split up, otherwise we're going to have (neo-)Latin words in descendants of languages descended from Latin. I'm not into theoretical feedback loops. — [Ric Laurent] — 13:47, 17 April 2014 (UTC)
That's not exactly a loop, since neo-Latin words can't go back in time and influence descendants of Latin. --WikiTiki89 16:03, 17 April 2014 (UTC)