As an anonymous user, you can only add new data. If you would like to also modify existing data, please create an account and indicate your languages on your user page.

Meta:International Beer Parlour

From OmegaWiki
(Redirected from International Beer Parlour)
Jump to: navigation, search


Nuvola apps chat.png
Start a new discussion
Discussion pages
Strategic discussions
International Beer Parlour

- archives


List of Beer Parlours

International Linguists Beer Parlour

- Inflexions


Questions about words
Articles needing attention
Insect room (report bugs)

- archives


Functionality wanted

- archives


WT.social[edit]

Just created a so-called subwiki on the new social network: OmegaWiki - let's hope we get some more contibutors, fans, friends and/or followers. Klaas `Z4␟` V:  15:49, 12 January 2020 (CET)

I created an account and when going to the link I get nothing about OmegaWiki, but an invite to donate to wt.social to gain access to the site - weird, very weird - it's a bit like asking our contributors money to be able to add data. Hmmm ... or is there something I am missing? --Sabine (talk) 17:45, 12 January 2020 (CET)
Ok, I went to my profile and searched for OmegaWiki and so I could find the page. Well, I leave my first comment, so others that experience the same know that it is not necessary to pay. --Sabine (talk) 17:48, 12 January 2020 (CET)

Indeed it is not necessary to contribute with £,€ or $ just like in all WMF-projects as long as you do not become a member of what they call chapter. I have to get used to the interface since it is different from here and practically all "normal" wikis. Klaas `Z4␟` V:  13:12, 13 January 2020 (CET)

Server updated[edit]

I will put it here so that I can remove it from the Sitenotice.

The server (debian) has been updated with a new version of apache2, and php7. Mysql had been replaced by Mariadb. I don't know much about the latter but it seems to be no different than mysql and there was nothing particular to do for transferring the database.

Mediawiki has been upgraded from 1.27 to 1.31. 1.31 is the long term stable (LTS) release. I plan to stay up to date with LTS release mostly for security reasons, and then I don't have to upgrade as often as if using the normal stable releases. Some things have changed, some fonts, colors and some options for admins, but not much, and I did not have to change the OmegaWiki code. The search field (top right) now works for the Expression namespace without me needing to hack the code. However, it shows "Expression:" everywhere which I would like to get rid of (my hack was better...).

The html tables colors also have been a bit changed because I replaced some (stupid) html tag with some css to reduce the html size. I could define more colors in css. I think for the moment tables in edit mode are all white. I can also add borders, etc. I am not good with design so I take any advice.

At some point I will try to use nginx instead of Apache to see if it is faster (I heard rumors). I have already a test server running with nginx, but configuring nginx is always a bit of a mystery and finger-crossing.

Everything at a rather slow space, the combination of home office stuck with two young very noisy kids does not give me much free time and sleep and Konzentrationsfähigkeit.

Please report any weird behaviour to me. --Kip (talk) 13:38, 1 June 2020 (CEST)

Thanks a lot for this update. I could use the site almost all the time during the update. I've also noticed some helpful changes in the CSS of some forms that improves their usability. Great job. Ascánder (talk) 03:20, 8 June 2020 (CEST)

Need help in importing TSV[edit]

Hello, i need some help in importing translation of English to Santali bilingual with definition and translation. I have exported TSV then translated and added definition offline. I want to import the same by importing TSV, but unable to due to non-administrative privilege. Prasanta Hembram (talk) 07:51, 20 June 2020 (CEST)

Hi, I have given you the necessary import rights (I think).
Please try first with a small subset to see that it works fine (it has been some time since we last use automatic import, so it is mostly to see that there is no bug in it)
and then you can import the rest.
In any case, if there is some problem, tell me and I can usually solve it by modifying the database directly. (we don't have a revert function like a normal wiki...).
Thanks for contributing. --Kip (talk) 15:15, 20 June 2020 (CEST)
Thanks, Kipcool. I will try and inform you. Prasanta Hembram (talk) 17:30, 21 June 2020 (CEST)

Nginx[edit]

The OmegaWiki is now using Nginx (instead of Apache2). I will see if it makes any difference in terms of speed.

Also (note for me :) ) I disabled Varnish cache which did not bring much but took a lot of memory. --Kip (talk) 15:24, 30 July 2020 (CEST)

And I doubled mysql memory usage ( SET GLOBAL innodb_buffer_pool_size=268435456; ) . It's never a good idea to change many parameters at once, but it's more fun. --Kip (talk) 15:47, 30 July 2020 (CEST)

Noticed a page is broken on the community data page[edit]

I saw this page http://www.omegawiki.org/Special:Ow_downloads was broken as I was browsing the intro pages Michael Tran (talk) 14:23, 3 August 2020 (CEST)

Thanks for reporting. I had not seen that. That should be fixed now!
(error was caused because we have an older version of MediaWiki and they changed some function names and changed our codes with it) --Kip (talk) 14:55, 3 August 2020 (CEST)

External complements included in the definition[edit]

In many cases, a complement, which is not included in the meaning of the word, is included in the definition. For instance DefinedMeaning:bypass_(1112487): "To avoid an obstacle by going around it.". Strictly speaking, this definition seems to me incorrect, because "to bypass" just means "To avoid (...) by going around it.". The obstacle has to be expressed separately, as in "We bypassed the mountain."; it is not included in the verb. Let's now see a correct example: DefinedMeaning:cook_(479132): "To prepare a meal or a single dish." and DefinedMeaning:prepare_(839220): "To make ready for eating or drinking.". This is clear: the object is included in the 1st definition, so the verb is intransitive, as in "She is cooking.", but it is not included in the 2nd definition, which obviously needs an object, as in "She is cooking the hare.", the verb being transitive here. But in Castilian, the 2 definitions (for "cocinar") are respectively "Preparar una comida o un solo plato." and "Hacer que algo esté listo para ser comido o bebido.", so both verbs seem to be intransitive, the object being included in the definition itself, and it is confusing. Why do we add such complements inside the definition? Usually because the usual grammatical construction needs it, or to indicate a specialisation of the main word. For instance, to "bypass" doesn't mean to avoid anything or anybody: the avoided thing must be an obstacle. Sometimes, the difference between 2 words depends only on a complement, as for "to breastfeed" v. "to suckle". I suggested in 2010 a set of rules to make this clear both for humans and translation machines (though the current state of the art doesn't use this kind of information): International_Beer_Parlour/Archive20110831#.22Usage.22_fields (See also Help_talk:DefinedMeaning#Connotations.2C_level_of_language.2C_degree_of_specialisation.2C_idiomaticity_and_degree_of_accuracy). My proposal was not accepted. So I make a simpler one: to put between brackets, inside definitions, complements which must be expressed separately from the word being defined. For instance: "To avoid [an obstacle] by going around it. --Fiable.biz 2020-08-18.

I agree with the brackets!
The tlfi uses this syntax (for "cuisiner"), with a different use of [ ] and ( ).
  1. Préparer, accommoder (un plat, des mets).
  2. [Le compl. d'obj. désigne une manifestation de l'esprit hum.] Préparer avec soin (en secret ou d'une manière peu avouable).
I think it would make sense to use the same difference between the two brackets, since we already use (sometimes...) [ ] for words that are difficult to define in a standard way. For example for but (en). --Kip (talk) 11:23, 18 August 2020 (CEST)

How to move page[edit]

I was working on a DefinedMeaning, DefinedMeaning:Cacique (1756849), and I didn't realized that the name was in upper case. I need to change it to "cacique" in lower case. Is there a way I can do this? I didn't find a "move page" on the special pages... --Luk3 (talk) 23:23, 21 September 2020 (CEST)

Click on 'More' next to the 'search'-field under your name. One of the options will be 'move' if you have this permission. If not you may ask an admin to do it or give you the privilege. It's done now. Klaas `Z4␟` V:  23:13, 28 September 2020 (CEST)
Sorry for the late reply,
No, the DefinedMeaning pages should not be moved, this only creates problems but will not solve the page name. It is enough to correct the translation (as you did), and that Expression:cacique is ok. The rest should be done automatically by the software, when we program that... It is bothering us since the beginning (if only I had some time to program this... don't make kids). --Kip (talk) 13:08, 30 September 2020 (CEST)