Mon, Jan 8
To make sure that what I'm talking about is clear, here is a screenshot:
Hi @Nikerabbit thank you for taking care and put attention on that. :)
Tue, Jan 2
Ok, thank you @Nikerabbit. Then it would be good to add this shortcut inter parentheses. :)
Sun, Dec 31
Mon, Dec 25
So I started to play with discourse. One thing I wonder is what scope should this new discussion tool should target to have good chances to be complementary rather than a competitor with existing canal – if there is no long term goal to close some of them.
Sat, Dec 23
I didn't thought of the possible abuse, thank you @MarcoAurelio and @matmarex for relieving the potential problems. I agree with @Urbanecm that potential abuse should be taken into consideration without abandoning completely the feature.
Wed, Dec 20
Dec 8 2017
See https://www.mediawiki.org/wiki/User:Psychoslave/generic_glossary/eo for some related works
Nov 12 2017
I replied to https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/Wikidata/Add_en-us_as_a_separate_language which is linking here as follow:
Nov 1 2017
It would also be useful to be able to use a set of possible values provided by some template/module.
Support of a dark skin was not really my point, although I would welcome such a proposal. I would expect the development of a skin to be a far more huge effort than proposing the icons in both dark and light flavour.
Oct 31 2017
I will just have one question: are this icon designed with non-white background use in mind?
Oct 30 2017
Oct 28 2017
For draft template I'm working on for the Wikitionary, I came with things like |définition.1.4.exemple.2.description =. That is description of 2nd example of the 4th subdefinition of the first main definition. That might be a somewhat extreme example, but that would be nice to take it into account while treating this ticket.
That's something which would be extremely useful.
Sep 19 2017
Hello, I landed here after an answer to [[Wikitech-l] Is it possible to edit scribunto data module content through template edit popup of visual editor?](https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088773.html)
Aug 31 2017
Just for making reference in both side : https://www.wikidata.org/wiki/Wikidata_talk:Wiktionary#CC0_and_CC_BY-SA
Aug 27 2017
Well, the license of the lexeme namespace is indeed important, but what would be the rational behind using CC0? That would make for sure (legally) impossible to reuse Wiktionary materials which are CC-by-sa-3.0 (possibly dual licensed under GFDL).
May 26 2017
@Nemo_bis I don't know where I could check if the push access was granted, nor who to contact to know that, let alone make the access granted if it's not already grandted… Do you have hints about that ?
Apr 18 2017
En cours, merci de faire vos retours : https://framaforms.org/formulaire-de-demande-de-bourse-wikiconvention-francophone-1492421252/webform
Apr 13 2017
Mettre un mél comme solution de replis dans le formulaire comme c'est un service en bêta, mieux vaut éviter les problèmes techniques qui empêche les inscriptions
Penser à mettre en avant les possibilité de garde des enfants dans le formulaire
Un lien pour le Google Form ?
Feb 28 2017
Jan 24 2017
@Haythamabulela , but what would prevent editors to adapt formatting for each use case? The function can be in fact already be used for generating many output on any page on Meta. Adding more supported calendar won't change anything regarding this, it will just offer ability to provide more formatted output, but each function call have to provide parameters to indicate which format should be generated.
Lucky him. :)
Jan 23 2017
I'm not sure to understand your concern. The value is generated for the given parameters in the context where it appears. So if there are other context with tables where you would like to use this function, you can always adapt it, can't you? There is no table in the Technews related message.
On a side note, what is the origin of the banana reference?
Jan 20 2017
Jan 10 2017
Jan 6 2017
Thank you @cscott for your feedback. I fail to see what you might be suggesting, if anything, with "there is more to increasing diversity than simply translating your content", however. Are specific things you have in mind for this "more"?
Actually, as far I as can see, for translation units, content with several language should be a problem. But maybe others might see some problems I'm unaware of. Sticking to the example, the translation preparation might look like.
Actually, you might have several languages in the same sentence. For example in this Esperanto translation of the Perligata paper (work in progress), one can find:
Dec 25 2016
Dec 24 2016
Thank you @jayvdb for your precious feedback. Do you have more information on how 'build tools' internationalization can cause problems in you experience? If you have concrete example, it would be great.
Dec 22 2016
Sorry if the message on mailing lists didn't match you expectation, I didn't thought you had question in mind when saying "What are the general questions that you are referring about?".
Dec 21 2016
Dec 19 2016
I don't know, maybe this could make things harder to browse when you are in archive excavation mode. :)
By the way, do we have a dedicated phabricator project for 2017 ?
Not yet. Would you have list(s) where you would advise me to discuss the topic?
Dec 14 2016
Sure, but would such an approach be adopted this is not the form most users would consult the glossary, it just make it more structured with all the pro and cons of such an approach. Just like wikidata in fact.
Dec 12 2016
Dec 9 2016
A Scribunto implementation might look like this
Where and how should this term be stored? Within plain wikitext on the wiki, within a Scribunto Data Module, or within Wikidata?
Dec 5 2016
Shouldn't this also include a localized radix mark? Or is point fine here?
Actually, this apply to everything in https://www.mediawiki.org/wiki/Category:Glossary
If you mean the link below "Welcome to Wikiversity beta", then it's not what this ticket is about, as it doesn't provide a direct mean to go to the current interface language corresponding root in the sidebar. You have to go to the main page, and then follow this link, which is not the best browsing experience.
Nov 30 2016
Nov 24 2016
@Aklapper is there anything more I may do right now to make this topic go ahead?
Nov 18 2016
Hi, sorry the ticket flight out of my radar, I didn't see the previous replies. The proposed solutions by @Nemo_bis w would both be OK as far as I'm concerned. I don't have enough privileges to deploy any of it, though.
The ticket does overlap with T150417. But T150417 was created to go along the corresponding 2016 Community Wishlist Survey proposal.
Nov 17 2016
Most of those links basically refer to teaching programming languages
Nov 16 2016
Sorry, I mean beta.wikiversity.org
Yes, it would also be welcome on beta.wikimedia.org
Thank you for the suggestion of searching for related sources. Finding documentation on the subject is in fact, to my mind, very interesting and funny. Here are a few more or less relevant links:
Nov 15 2016
Ok, sorry for the misunderstanding.
Ok, T147896 seems a subproject for this one, doesn't it?
That's something that have been in a discussion on the wikisource-ml to.
Some errors introduced by Apertium migth be easily avoided, that is variable like $link and so on should not be translated. Could the Apertium instance be tweaked to avoid translating tokens which begin with a dollar?
Is that matching T150263: Create a searchable and shared glossary?
Nov 14 2016
Well, to begin we may use a module to store the data, this way the display would be far easier to evolve both in term of UX and storing structure.
Nov 13 2016
What is the expected benefit of making such a page sysops only?
Nov 11 2016
A glossary with context indication would be of far greater interest. One English entry can have several counterparts in other languages. It would be even better if we could link that to validated example, and "look for more occurrences on translatewiki".
@Krenair the local templates and modules maintenance are the responsibility of local communities. I don't think that on this regard this would add much to the current maintenance "nightmare", while it may add attraction to local technical contributions.
Nov 10 2016
Nov 6 2016
Nov 2 2016
Ok, thank you @Amire80 for the feedback. I think I can wait, it's not like there wasn't many tasks I can do without any other extension installed. Well, I reallly would like to advance on some translation, but I guess I may transfer the content on some wikipedia user page, make my translation and transfer it back to beta.wikiversity.
Ok @matmarex, thank you for the hint. That's huge thread, and it seems to already attract enough human resources. I will let it be for now and concentrate on other tasks. Feel free to contact me if you think my contribution on this point could bring anything useful at some point.
Oct 31 2016
Seems like it works now, thank you to those who helped. :)
Oct 25 2016
Guide for involving new volunteers is also a relevant pattern here.
The Harvesting new Wikimedians from social media. However I don't feel like me, myself and I would be enough to make a great team on so called social media. I don't even have an account on facebook and so on. Thus I don't have all the skills to use them as promotional tool. Plus there are certainly people out there who are more skilled than I on the general "public relation" topic. :)
I began to read some of the pattern documentation. The most relevant for this kind of task is certainly Matching newcomers to Wikimedia projects and activities: nurturing happy, passionate editors).