Victionarium:Taberna

E Victionario
Salire ad: navigationem, quaerere
Haec est taberna Victionarii ubi potes si dubia habes, explanationes quaerere, nuntia ad nos mittere et cetera.
Ut sententias antiquiores legas vide tabernae acta priora.
Compendium:
VT:T
Quaestio nova
Hic colloqui possumus.

New model[+/-]

We need a new model to work with. I prefer the french model mixed with some other dictionaries. If you have any other ideas, i'll hear from you. -- DenisWasRight (disputatio) 15:59, 30 Maii 2016 (UTC)

I agree, the French model is acceptable, though it's not very different from other wiktionaries, or is it?
Up to now an outstanding property of Victionarium was the fact, that there's no agglomeration of multiple language entries on one page. Each language has its own page and there's a kind of disambiguation page (like in Wikipedia, but called "discretiva") which has links to all existing pages of the same or a similar lemma in different languages. It's my opinion that this property should be kept, independently of the new layout of an individual page. --YaganZ (disputatio) 16:57, 30 Maii 2016 (UTC)
I will make some examples and let you decide which one is the right one. Your idea about the discretiva is good. We keep it that way. -- DenisWasRight (disputatio) 18:12, 30 Maii 2016 (UTC)
Some examples are a good idea. Why not simply create a complete example page the way you want it to look like? --YaganZ (disputatio) 19:35, 30 Maii 2016 (UTC)
YaganZ, if you agree the model should look that way. Still much needs to happen. I need to translate Module:Article sections/data and Module:Types of words/data, but my latin is not the best. And also a lot of categories will be needing an translation. Btw the template for the translations will be changed with trans-top if we able to create it here. -- DenisWasRight (disputatio) 09:12, 31 Maii 2016 (UTC)
I viewed your example page. You'll find your proposal together with mine on Usor:YaganZ/arenaria. Unfortunately you used an old incomplete page as an example, but I added most section names that can occur. You might use the Latin dictions to modify the module data. More word classes and section names you'll find in Categoria:Victionarium:Formulae. All word class templates should provide the proper categorization too (word class and language).
In my opinion the sequence of the three leading sections is essential, because one lemma (diction) can belong to different word classes, while pronunciation, alternate forms and etymology are common.
The numbering [1], etc. isn't very effective if not done automatically. I know that the German wiktionary is using this style, but it often leads to confusion when meanings are modified and the complete numbering scheme becomes invalid. I prefer the direct description of the meaning as it is done in the English wiktionary and in many others. --YaganZ (disputatio) 12:15, 31 Maii 2016 (UTC)
I agree, but I dont want to use the bullet for the synonyms etc. Because again you shall need to use numerals to point the meaning 1,2 and 3. How about using # for them too? As for the lemma, we can have more sections under 1 language. Not like Latina 1, Latina 2 etc. Can you translate those, please? -- DenisWasRight (disputatio) 15:35, 31 Maii 2016 (UTC)
You don't have to use bullets for anything. If you make a template and/or module which correctly organizes the numbers in all sections, go ahead! But I don't want to do this manually. Be aware that the translation section of en.wiktionary, we are going to use, is based on meanings not on numbers. And who knows which number has what meaning when the page is somewhat longer. --YaganZ (disputatio) 22:09, 31 Maii 2016 (UTC)
I understand. I'll make a new example and see if you like it. Some more needs to be translated. Can you also check this for spelling. -- DenisWasRight (disputatio) 09:26, 1 Iunii 2016 (UTC)
I thought you were for the french model, but I can't understand why you putting the pronunciation above (under the level 2 section). If the pronunciation and the etymology are above, then you create a empty space on the right. Otherwise it can be looking that way. As for the pronunciation goes, I shall need to copy the french template. -- DenisWasRight (disputatio) 09:50, 1 Iunii 2016 (UTC)
I don't see any empty space in porta, do you? Yes I'm for the French model, but I don't think it's reasonable to hide an important topic like the pronunciation section somewhere in the background. That's a weak point in the French model I wouldn't like to imitate here. (signature)
I see! Do you want me to put the etymology above the Fontes? Cause I really don't like to have both the pronunciation and the etymology among each other. Btw in a real dictionary is the etymology showed under the meanings and examples. -- DenisWasRight (disputatio) 12:25, 1 Iunii 2016 (UTC)
OK, put the etymology section where it's suitable for you. I don't mind. --YaganZ (disputatio) 12:41, 1 Iunii 2016 (UTC)

YaganZ, I did my best. If you want an extra sub-section under the Nomen substantivum named Meanings (in latin) I'll hear from you. -- DenisWasRight (disputatio) 15:20, 3 Iunii 2016 (UTC)

Denis, it looks fine. No subsection "Meaning" is needed. But you should fix two grammatical issues:
I. — figurativus: abbreviation 'fig.' stands for 'figurative' (adverbium of figurativus).
II. — Latina: that's ambiguous, standing alone it means "female inhabitant of Latium". In 'lingua Latina' it's the female nominative of the adjective 'Latinus', because 'lingua' has female gender. Standing alone it should read 'Latine' (adverbium of Latinus) with the meaning '(in) Latin'. "Latine loqui" means "to speak Latin". --YaganZ (disputatio) 19:14, 3 Iunii 2016 (UTC)
I'm not good in cases and genders in Latina. The fig. is fixed, the Latina can't. If I change the Latina in Latine, then the all thing changes. I think we should go back to the old old way. -- DenisWasRight (disputatio) 19:55, 3 Iunii 2016 (UTC)
Not back to the old, old way! Try {{#invoke:languages/templates|getByCode|la|getOtherNames|1}} for Latina and {{#invoke:languages/templates|getByCode|la|getCanonicalName}} for Latine, or use the access functions getCanonicalName() and getOtherNames(). --YaganZ (disputatio) 21:17, 3 Iunii 2016 (UTC)
You have to define the access mode first, before you can use getCanonicalName() and getOtherNames()[index], something like this:
    -- Récupération du nom de la langue
        local lframe = require("Module:languages").getByCode(code) -- access by language code
        if lframe then
                section_langname = lframe:getCanonicalName() -- language name
                cat_langname = lframe:getOtherNames()[1] -- inflected language name for category: Lingua <cat_langname>
        else
                section_langname = "ignote" -- unknown code
                cat_langname = "ignota"
        end
--YaganZ (disputatio) 07:08, 4 Iunii 2016 (UTC)
Thank you, but I don't think this is gone work. The modules:linguae and languages are different. I think we should probably write the Module:sectio and the others all over again. Unfortunately I'm struggling with the understanding of the Lua language and can't be useful. Is there any place to test this codes and to see what they provides? -- DenisWasRight (disputatio) 07:21, 4 Iunii 2016 (UTC)
When you agree to use this as model and also agree to have this as model for the forms (no empty discretive templates (only in words not in forms of words) and no useless sections) and want to rename the categories into: Nomina substantiva/Latina, Figuragtive/Latina, Informatica/Latina, Substantiva feminina/Latina and Nomina declinationis 1/Latina (so we do not to have to deal with genders and wheter the word is plural or singular) I'll here from you. But I will not use old templates and categories. -- DenisWasRight (disputatio) 07:46, 5 Iunii 2016 (UTC)

Testing the code[+/-]

I tested the above code temporarily with your module 'lingua' and the 'porta' page using the debug console. It worked, but the French code completely ignores flection, which is not needed in French, but essential in Latin. They only have one language name for all purposes, which isn't applicable to Latin. It would be a lot of work to completely separate the different name variants.

The best solution would be to rework all sections that are involved in language names, or to begin from scratch writing your own code while improving your LUA knowledge. For Latin you'll need a more sophisticated model and additional methods than for French.

Then I would recommend to cease from using the French language names database, because it's not very effective to maintain two databases. The English database is needed for the translations anyway.

I noticed the incompatibilities. You used there a flag 'porta = true' to assign that there's a page "Auxilium:<language>". That's no good idea, because anybody who would create a new Auxilium page surely won't update the linguae/data file. If you want to know whether an Auxilium exists or not, you should test the existence dynamically using an appropriate function. --YaganZ (disputatio) 08:12, 4 Iunii 2016 (UTC)

It will take me a long time to write one. I need to learn all this codes. I should've noticed the diference betwen the two languages. Maybe we should use the old way for the moment. The sections are working fine by the way, but not the language section. -- DenisWasRight (disputatio) 08:52, 4 Iunii 2016 (UTC)
I agree, it's the best solution to temporarily restore the old language header until the problems are solved. Could you please update the 'porta' page with all features you've already realized (icons etc.) as an reference design example? --YaganZ (disputatio) 09:56, 4 Iunii 2016 (UTC)
I need to study how to replace the old modul:linguae with the modul:languages. -- DenisWasRight (disputatio) 14:20, 4 Iunii 2016 (UTC)

Gadget for adding translations[+/-]

We need the gadget for adding translations without editing the page. We can use the english tamplate trans-top and the script to create it. Unfortunately I'm not good at that. -- DenisWasRight (disputatio) 15:59, 30 Maii 2016 (UTC)

I'll take a look at how difficult or easy it is to transfer the template to Victionarium. I did a lot of interwiki template transfers, but sometimes it was necessary to transfer a complete infrastructure of sub-templates too. --YaganZ (disputatio) 17:38, 30 Maii 2016 (UTC)
Needs a lot of work, but I'm sure when is done it will make the entries much easier. In this time nobody wants to edit the whole page. So we need to make something easier to work with. -- DenisWasRight (disputatio) 18:12, 30 Maii 2016 (UTC)
In the meanwhile I imported all modules and templates. The translation section is working statically now. But the editor script remains passive. I put all necessary CSS and Javascript into my private common.css and common.js without success. Maybe I missed something, but it's thousands of lines of code. I have to do some more research, later. --YaganZ (disputatio) 21:01, 31 Maii 2016 (UTC)
I think you need to create the Conrad.Irwin/editor.js here and then modify it for your needs. It's not working that way. You can copy it to Usor:YaganZ/editor.js and then try. -- DenisWasRight (disputatio) 21:54, 31 Maii 2016 (UTC)
Thanks, that way it's working. It seems that the import script doesn't support interwiki access. --YaganZ (disputatio) 22:27, 31 Maii 2016 (UTC)
Good job. It showed up! -- DenisWasRight (disputatio) 22:24, 31 Maii 2016 (UTC)
Something seems to be missing at Lua error in Module:parameters at line 110: The parameter "<strong class" is not used by this template. -- DenisWasRight (disputatio) 22:33, 31 Maii 2016 (UTC)
I didn't notice any error. Where did you get it?. --YaganZ (disputatio) 11:56, 1 Iunii 2016 (UTC)
It showed up when I tried to add an translation. But I guess you change something in the editor.js and it's working fine now. -- DenisWasRight (disputatio) 12:30, 1 Iunii 2016 (UTC)
I guess there'll be still something to be modified in editor.js. I only changed the obvious things and I'm not sure if I should translate the user interface into Latin or leave it in English. --YaganZ (disputatio) 13:28, 1 Iunii 2016 (UTC)
It should be in English I guess. Besides this why is every single translation linking to one page, in this case to porta? -- DenisWasRight (disputatio) 16:36, 4 Iunii 2016 (UTC)
I'm just introducing intelligent links to the translations module and previously red links are now reflected to the source page temporarily. This will be changed later. --YaganZ (disputatio) 17:18, 4 Iunii 2016 (UTC)

Bot[+/-]

We for sure will need a bot to make all this changes. I can't write one, so we will need to find someone els. -- DenisWasRight (disputatio) 15:59, 30 Maii 2016 (UTC)

OK, if we are going to have some specification of what has to be changed, I'll ask for help. --YaganZ (disputatio) 17:15, 30 Maii 2016 (UTC)
Once we decided how the model should look, we then see what we can do about it. -- DenisWasRight (disputatio) 18:12, 30 Maii 2016 (UTC)

MediaWiki[+/-]

We also shall need some new codes for MediaWiki:Common.css and .js to make working here easy. We can use some of the other wiktionary's -- DenisWasRight (disputatio) 15:59, 30 Maii 2016 (UTC)

I already inserted some CCS code into my private commons.css to make the inflection tables look better. The MediaWiki:* pages are protected, so we need administrator rights to modify. --YaganZ (disputatio) 17:12, 30 Maii 2016 (UTC)
It will take time, but I'm sure the la Wikipedia will give us the rights. -- DenisWasRight (disputatio) 18:12, 30 Maii 2016 (UTC)

Policy pages[+/-]

To make the work for our user easy we must write some policy pages to prevent users copying information from dictionaries with copyright on it. -- DenisWasRight (disputatio) 15:59, 30 Maii 2016 (UTC)

I don't think this to be an urgent topic but you might "borrow" some text from Vicipaedia. Since this is the Latin wiktionary, it would be a good idea to offer the policies in Latin too. --YaganZ (disputatio) 17:23, 30 Maii 2016 (UTC)
It's not so urgent but we keep that in mind. Maybe this is the most calm please of them all. In other dictionaries you have a lot of vandalisme. I don't see that here. -- DenisWasRight (disputatio) 18:12, 30 Maii 2016 (UTC)
There wasn't much vandalism during the time I've been here. It was easy to revert. I noticed some SPAM accounts and had to inform an active SPAM-fighting user. --YaganZ (disputatio) 19:28, 30 Maii 2016 (UTC)

Labels[+/-]

I will create templates for the labels so we can categorize words by topics. -- DenisWasRight (disputatio) 16:13, 30 Maii 2016 (UTC)

I'm not sure which kind of topics you mean. I spent a lot of work to categorize by linguistic topics inside templates. I guess you mean semantic or physical topics, but I'll see. --YaganZ (disputatio) 17:32, 30 Maii 2016 (UTC)
Now, labels for words that are about biology or science. That sort of topics. We can categorize words by using a template. -- DenisWasRight (disputatio) 18:12, 30 Maii 2016 (UTC)
Yes, that's OK. There are still a lot of those categories. Please take a look at Categoria:Per thema. You might find a more systematic way of categorization. So, go ahead with your templates. --YaganZ (disputatio) 19:01, 30 Maii 2016 (UTC)
What's better? Mythologia Latina or Lingua Latina/Mythologia. -- DenisWasRight (disputatio) 18:37, 31 Maii 2016 (UTC)
I think it should be "Mythologia Romana" as a sub-category of 'Mythologia". --YaganZ (disputatio) 19:03, 31 Maii 2016 (UTC)
Then we can as of now categorize the words per topic by using this template. You need to fill in the parameters {{Label|lang code|topic}} (or {{Label|lang code|topic|topic}}, which wil give you: (mythologia) (or (mythologia, historia) and the category - Categoria:Mythologia Latina (or Categoria:Mythologia Latina, Categoria:Historia Latina)... Unfortunately it's categorizing words per topics by only languages, not by cities, countries or any race. You can add here some more topics if you need. -- DenisWasRight (disputatio) 19:27, 31 Maii 2016 (UTC)
If this template is that inflexible, it's of very limited use. "Mythologia Latina" would mean the mythology of the Latin language (rather nonsense), or mythology of the Latium landscape or the inhabitants of Latium? Doesn't make much sense for me. It would be better to replace the language code by some geographical or taxonomic identifier. --YaganZ (disputatio) 19:54, 31 Maii 2016 (UTC)
Idk, but that's kind of a Wikipedia thing. Those labels use to categorize words with historical, mythological or biological meanings. How should we name them? See for example the english and french categories. -- DenisWasRight (disputatio) 20:12, 31 Maii 2016 (UTC)
I think this template might be OK for English, but can't be used for Latin dictions. It doesn't know anything about gender and declination. I tried {{Label|la|art}} with the result "Artes Latina", which is grammatically incorrect. It should read "Artes Latinae". --YaganZ (disputatio) 20:23, 31 Maii 2016 (UTC)
Uh I didn't know the language changes. But, what is your idea then? -- DenisWasRight (disputatio) 20:29, 31 Maii 2016 (UTC)
Why not doing the same thing as they've done in en.wiktionary? They avoid grammatical issues by using the language code only as a prefix. You could create a category "la:Mythologia" with a sub-category "la:Mythologia Romana‎" and so on. If you simply copy their categories model you only have to translate the final text. --YaganZ (disputatio) 20:48, 31 Maii 2016 (UTC)
Would it be then good if you have Cat:Lingua Latina, Nomina substantiva Latina, la:Mytologia, Nomina Latina declinationis 4 etc? The categories will not look the same. Or we can call them Latin terms with mythological meaning. -- DenisWasRight (disputatio) 20:53, 31 Maii 2016 (UTC)
You should strictly separate language specific categories from topic specific ones."la:Mytologia" means "Latin terms related to mythology". It's like a parallel world to the grammatical categories. The la:prefix is only a trick to avoid full text and makes it easier to work with generalized templates. --YaganZ (disputatio) 21:33, 31 Maii 2016 (UTC)
Do we need to make the other categories look also that way? Cause it's still not the same. -- DenisWasRight (disputatio) 21:46, 31 Maii 2016 (UTC)

Categories[+/-]

Nomina substantiva Latina etc. are related to the language itself. All are sub-categories of "Grammatica" or "Linguae". All of these categories are classified by specific templates, which determine the grammatical properties by word class and inflection. I made some templates which provide correctly declinated results of the language designators. I don't see any reason why this should be changed. It's part of the content. (this is only valid for the newly maintained pages, there are still a lot of old pages, which lack categorization at all). --YaganZ (disputatio) 21:25, 31 Maii 2016 (UTC)

The language on level 2 wil categorize the Lingua itself. The Part of speech wil be categorizing by the new section template. As for the Substantiva Latina feminina goes, we can create an common template like in the english wikt.. to add the word, the gender and or the plural and singular word. The audio/ipa template wil also need a categorization. And the words inherited en derived from other languages should also have their owno template. -- DenisWasRight (disputatio) 21:43, 31 Maii 2016 (UTC)
What dou you mean by level 2?
I aggree, the section templates should specify the word classes with properties like language, if verbs are transitive, intransitive, auxiliary etc.. I did this partially with the old section templates, but it's far from being complete because this can't be automatized.
The gender and grammatical classifcation of substantives, adjectives, pronouns and Numerals (as far as they can be inflected) is detected and assigned by the declination templates and doesn't need any additional handling. This is valid for Latin and German. I didn't touch those of other languages.
The audio template is obsolete, because it has some severe drawbacks and doesn't work reliably with MacOS. I replaced it by Formula:Audio - {{Audio|...}} which is used in the English wiktionary and many others. It doesn't have the drawbacks and is working smoothely in the background with all operation systems and browser afaik.

Vote for new administrators[+/-]

We have a vote for two new administrators here and here. Anonymous users are not allowed to vote. -- DenisWasRight (disputatio) 10:26, 31 Maii 2016 (UTC)

Have voted in both, and created a couple of redirects/technical pages for the future :) also putting myself forward for adminship to help out - RfA here Samtar (disputatio) 15:39, 1 Iunii 2016 (UTC)

Technical things[+/-]

I do a lot of work with the operations team and on Phabricator - if there's anything technical you need some help with, please let me know Samtar (disputatio) 15:41, 1 Iunii 2016 (UTC)

Couple of things[+/-]

Redirecting 'Community Portal'[+/-]

Hi @DenisWasRight: & @YaganZ: - I notice you two are doing some awesome work with getting the modules imported over, would it be okay to redirect Victionarium:Porta communis straight to Victionarium:Taberna, if only temporarily so that new users can find the page a little easier?

I think that's OK, so we'll attract more attention. --YaganZ (disputatio) 18:22, 1 Iunii 2016 (UTC)
Yes check.svg Done -- samtar talk or stalk 18:32, 1 Iunii 2016 (UTC)
Why is the Salve! in English? This is supposed to be an Latin dictionary. -- DenisWasRight (disputatio) 18:41, 1 Iunii 2016 (UTC)
Feel free to translate to Formula:Welcome-la/Formula:Welcome - I noticed this entire page of discussion was in English and thought it would be worth sticking to it for some things? -- samtar talk or stalk 18:49, 1 Iunii 2016 (UTC)
If your language interface is English then Yes. Unfortunately I don't speak Latin, not yet. -- DenisWasRight (disputatio) 18:53, 1 Iunii 2016 (UTC)
There's already a salve template in Latin, but I propose to create a bilingual (la, en) welcome message that will also address beginners without much knowledge of Latin prose. The reason why we use English on this page, is the fact that our English is much better than our Latin. --YaganZ (disputatio) 20:54, 1 Iunii 2016 (UTC)

Administrators Noticeboard[+/-]

When the wiki starts to get a bit busier, it's likely users will want a noticeboard to talk to admins to raise concerns/complain - what would be the best translate for Administrators Noticeboard? Victionarium:Administratores Forum?

-- samtar talk or stalk 17:23, 1 Iunii 2016 (UTC)

I didn't find any adequate Latin diction for "noticeboard". But we might use "Colloquia cum magistratibus", meaning "talking with the administrators" ("magistratus" is the usual denotation for "administrator" in Latin wikis). --YaganZ (disputatio) 20:24, 1 Iunii 2016 (UTC)

Script code[+/-]

pronunciation

What should be the code to move the audio template next to the IPA pronunciation just like this picture in Module:appellatio. -- DenisWasRight (disputatio) 19:00, 1 Iunii 2016 (UTC)

You have to create a table and and use separate columns for each element (view {{Audio}}). --YaganZ (disputatio) 21:03, 1 Iunii 2016 (UTC)
But I'm using a module, not an template. -- DenisWasRight (disputatio) 21:28, 1 Iunii 2016 (UTC)
That makes no difference. You are generating HTML code inside your module. --YaganZ (disputatio) 22:09, 1 Iunii 2016 (UTC)
I don't have any idea how to do it, do you? -- DenisWasRight (disputatio) 08:13, 2 Iunii 2016 (UTC)
language section

How can I put Lingua to Porta: .. name_language (see the code below)? -- DenisWasRight (disputatio) 21:28, 1 Iunii 2016 (UTC)

if (lang.has_porta(code)) then
local name_porta = 'Porta:' .. name_language
text_name = '[[' .. name_porta .. '|' .. name_language .. ']]'

Why don't you use string concatenation too? --YaganZ (disputatio) 22:09, 1 Iunii 2016 (UTC)

local name_porta = 'Porta:' .. 'Lingua' .. name_language

It's fixed, but now I don't get the categorization right. I use to get Categoria:Lingua Latina instead of Categoria:Latina. -- DenisWasRight (disputatio) 22:13, 1 Iunii 2016 (UTC)
What's the problem? Categoria:Lingua Latina is correct. --YaganZ (disputatio) 05:43, 2 Iunii 2016 (UTC)
OK, I see, you want to get "Categoria:Lingua Latina" but you obtain "Categoria:Latina".
As I understand your module code, Categoria is only defined in function p.get_rare_letters(), but this function always returns nil or an empty string on the debug console, so no category is assigned. I guess you should compare again your code with the original one, maybe something is missing. --YaganZ (disputatio) 06:53, 2 Iunii 2016 (UTC)
The french wiktionary hasn't defined any category code, cause they simply have only the language name in their category. We have Lingua. How can I write an code that does the categorization? -- DenisWasRight (disputatio) 08:13, 2 Iunii 2016 (UTC)
I think we need to do something with this code:
-- Catégorie
table.insert(text_title, b.done_category_content(language))

-- DenisWasRight (disputatio) 08:20, 2 Iunii 2016 (UTC)
Take a look at Module:basis and function b.done_category(text, key, writing). I guess this function is the only place where you can insert 'Lingua'. --YaganZ (disputatio) 09:09, 2 Iunii 2016 (UTC)
Unfortunatly I have study Business administration, not ICT and my knowledge is therfore limited. -- DenisWasRight (disputatio) 10:02, 2 Iunii 2016 (UTC)
If I put the ' Lingua ' between '.. cat and .. text .. I get the category right. But then the category:Nomina substantiva Latina is turning wrong. -- DenisWasRight (disputatio) 12:44, 2 Iunii 2016 (UTC)
function b.done_category(text, key, writing)
  local cat = writing and ':Categoria:' or 'Categoria:'
     if (text ~= nil) then
         if (key ~= nil and key ~= ) then
             return '' .. key .. ''
         else
             return '' .. cat .. text .. ''
         end
     else
         return 
     end
  end

Foreign code[+/-]

Denis, it's no shame that you, as a hobbyist programmer, are not able to master this in my opinion quite intransparent code. But I don't see why this should be necessary to perform such a simple task like category assignment. Therefore I'm not motivated to waste my time analyzing foreign code that might work or might not work for our purposes.
Be realistic: if there are parts of the code that do the job you want to be done, then use it and throw away all the category stuff. Category assignment can be done using the well known and robust language and word-class templates like {{-la-|{{subst:PAGENAME}}}}, {{substantivum|la}}, etc. by embedding those in your module invoking templates.
It's more worthwhile to invest time in an elegant page layout and an attractive user interface. Those were the aims I supposed you told me a few days ago. --YaganZ (disputatio) 14:28, 2 Iunii 2016 (UTC)
You don't understand. I'm trying to make everything on the model with Lua's instead templates. Do you want to modifi thousand of templates (cause you keep creating them)? If I said that I espected you will help me with writing or modifying those modules. Otherwise I shall not choose to contribute here. But I'm searching for an answer outside the wiktionary. -- DenisWasRight (disputatio) 15:09, 2 Iunii 2016 (UTC)
I think this is a misunderstanding.
I. — I don't create new legacy language templates like {{-la-}}, etc., I'm categorizing them and use the content to update Module:languages/data2‎, /data3... and others, the languages management database used by the translation framework.
II. — I thought of writing some LUA functions to provide the correct names for your language section header, but I've seen you have solved the categories problem yourself.
III. — I started to modify all essential language specific templates that are used by inflection tables and links, which are still based on the legacy templates, to retrieve the language information only from the Module:languages/data‎-files. The translation framework is providing powerful modules and functions for this task. The maintenance of all language names will be much easier, because all information is to be found in the languages management database.
IV. — I don't want to keep you away from using LUA modules. It's simply a question of success: if you are able to solve the problem with LUA, then it's OK, if not, then find another way. --YaganZ (disputatio) 18:36, 3 Iunii 2016 (UTC)
It's just fine to have more modules instead of templates. Templates are hardly to modifie and modules not. I fixed my problem in a verry strange way. I didn't know how to create an code for the categories. The existing one is already used for other categories. But never mind. It's working fine now. We do not need any of the -la-, -en- etc. templates. The template Lingua does the same thing. -- DenisWasRight (disputatio) 19:33, 3 Iunii 2016 (UTC)

Deletion userpages[+/-]

The following user pages needs to be deleted: Usor:DenisWasRight/StyleArticles.css, Usor:DenisWasRight/Probo, Usor:DenisWasRight/Translationes, Usor:DenisWasRight/common.js, Usor:DenisWasRight/common.css and Usor:DenisWasRight/ExpandableTOC.js. Thanks! -- DenisWasRight (disputatio) 06:44, 9 Iunii 2016 (UTC)

Transwiki import — trying to achieve consensus for enabling this feature at Victionarium[+/-]

At the moment I'm working on the new translations section and associated topics. There's a sophisticated module framework available at en.wiktionary which I tried to implement temporarily at Victionarium as a feasibility study. I've got a successful result and I think it's desirable to install these features permanently. Together with Usor:DenisWasRight we set up a demo page to show all the new features.

Now the question to all active contributors is: Should we enable "transwiki import" to use resources from other wikis? Your opinions please! --YaganZ (disputatio) 09:56, 10 Iunii 2016 (UTC)

Support: Needed feature -- samtar talk or stalk 10:15, 10 Iunii 2016 (UTC)

Changes submitted[+/-]

Transwiki import from en.wiktionary will go live on June 13 (15:00-16:00 UTC) -- samtar talk or stalk 16:38, 10 Iunii 2016 (UTC)

Request for interwiki bot status - please vote there[+/-]

There's an interwiki bot status request at Victionarium:Bots and we should provide a local community consensus. Voting has begun and will be open until 2016-06-23. Please participate! --YaganZ (disputatio) 09:37, 15 Iunii 2016 (UTC)

Voting is closed. Result: 2 pros, no contra, no neutral. --YaganZ (disputatio) 21:48, 24 Iunii 2016 (UTC)