WORD BY LETTER : English CROSSWORD SOLVER and others things ...
Words starting with : 
Words ending  with : 
Ledger Nano S - The secure hardware wallet
Find a definition : 

definition of the word Wiktionary:EDIT

by the Wiktionnary

IC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> User talk:Conrad.Irwin/editor.js - Wiktionary

User talk:Conrad.Irwin/editor.js

Definition from Wiktionary, a free dictionary

Jump to: navigation, search
If you are a programmer, you may find things of interest at User:Conrad.Irwin/editor_docs

After you have made an edit with one of the installed tools (instructions for which are listed below) a blue box appears in the top left corner containing:

  • Save page
  • Undo
  • Redo

No changes made to the page are recorded until you press Save.

You should see a line at the end of the table something like

  • Help         :                       Preview translation More
    ◻ masc. ◻ fem. ◻ neuter ◻ common gender ◻ plural
  • The first box is the ISO 639-1 or ISO 639-3 language code (for common languages you can put in the language name, and it will give you the code).
  • The second box is the translation to add. This should normally be one word, if you attempt to add many separated by commas you will get a warning. If you want to request a translation set the word to {{trreq}}.
  • The gender tick-boxes are normally only needed for nouns, "common gender" tends to be used for languages where male and female have combined into one class, whereas "neuter" is a separate gender that is neither male or female.
  • Clicking Preview will try to make the edit, and display the Save page button in the top left.
  • Clicking more opens the extra options (really intended only for advanced users)
  • The second line contains gender check boxes, normally only one should be ticked. Though occasionally more are needed.
    • Transliteration: (tr=) The word as it might be transliterated into the Latin alphabet.
    • Qualifier: This is used if the translation only applies in a certain specific context, or under specific conditions. Fox example: (informally) and (literally).
    • Page name: (alt=) the name of the page when the word includes diacritics that are only normally found in a dictionary. This box may be automatically filled in for some languages (even when it is hidden).
    • Script template: (sc=) this only needs to be specified if you want something different from what it suggests.

After adding a translation, two buttons will appear in the middle of the table:

  • Clicking "←" moves the first translation on the right to the end of the left list.
  • Clicking "→" moves the last translation on the left to the start of the right list.

If you enable this feature, each translation table has a ± in the corner.

  • Clicking on this brings up an edit box for the table's header.
  • Type what you want in, normally the first few words in the definition (without linking or formatting)
  • Click "Preview" - if you are not happy with the result, click ± again - otherwise click "Save" in the top corner

WARNING: This feature has not been well tested in all browsers yet. Please notify me if you have any problems.

You don't have the current version of the translation table gloss editor.

Logged in users
Go to Special:Preferences and the Gadgets tab, then check "Disable translation table editor buttons"
Logged out users
You don't have the current version of the editor.
NB. Logged in users can disable it here temporarily, using the first method is recommended.

I can't do an entire project like this on my own, and so I've tried to make the architecture reasonably well-interfaced so that new modules can be added without having to know what else is going on; while none of this is trivial, the complexity is in trying to maintain a correspondence between the HTML on the page and the WikiText.

At the basic level, edits can be made by passing an edit object to the editor. Edit objects consist of a "redo" function which modifies the page HTML to reflect the edit, an "undo" function which does exactly the opposite of "redo", an "edit" function which performs the edit, and a "summary" string to be added to the edit summary. There is another framework for creating edit-forms, which is slightly more complicated - but should be easy enough to copy.

This is a list of things that need to be done. I will get round to them as and when I have the chance. If you want to add to this list, just a brief sentence describing the exact change; if you want something complicated add a section in discussion. If you want to implement these changes, please, please, please do.

  • Enable context sensitive disabling of buttons (particularly save form, also trans-balancers, and preview)
  • Work out nested translation sections.
  • Handle API errors.
  • Check revision of page from API matches wgCurRevision
  • A field for additional edit summary
  • Allow adding checktrans translations.
  • Add translation table button.
  • Edit existing translations.
  • (Add example sentence/quotations buttons)
  • (Change the trans-top color when there are no translations).
  • Add translation gloss.
  • Add error checking or warnings for nonexistant language codes.


Can it be made to convert language names to language codes? Most users know the former better, I think.—msh210 23:02, 12 April 2009 (UTC)

I thought about this too, it could, though I'd rather not include the names of all the ISO languages in the script (there are almost a WT:BP-load of them :p). I think a reasonable compromise might be to include the names of the first 100 languages in WT:STATS - and while I might make the input box slightly wide, I'll still leave iso code in the instructions. Conrad.Irwin 23:15, 12 April 2009 (UTC)
It will now convert ISO 639-1 language names into the respective codes. Conrad.Irwin 11:49, 14 April 2009 (UTC)

There was a BP suggestion (but I'm responding here as I can't really open BP on this machine) that this be turned on by default for users. I might suggest that that would lead to vandalism; perhaps, if such a thing is possible, turn it on by default for autoconfirmed users only?—msh210 23:02, 12 April 2009 (UTC)

Such a thing is possible, and that might be a better first-step. I still think it would be an interesting experiment to see whether a more structured input field leads to higher quality editing - though whether we want to even try is a question for the community at large. Conrad.Irwin 23:17, 12 April 2009 (UTC)

Is it possible to add an option around the editing translation boxes to allow adding in a translation to be checked format, maybe inside the More section ?? Serpicozaure(talk) 13:21, 14 April 2009 (UTC)

We'd first need to fix {{ttbc}} to accept language codes. Conrad.Irwin 13:42, 14 April 2009 (UTC)
That's easy, and a fine idea. Done. Robert Ullmann 16:31, 14 April 2009 (UTC)

The script can not find the translation table in the wikitext if the translation table header contains some wikisyntax. For example, when someone write

{{trans-top|(''biology'') frog}}

instead of expected

{{trans-top|(biology) frog}}

See abort (as a verb) where such a trans-top is used.

When util.getTransGloss is called on the header "(<i>biology</i>) frog", then it returns "() frog" because <i> is not a text node.

for (var j=0; j< head.length; j++)
  if (head[j].nodeType == 3)
    ret += head[j].nodeValue;

Then, in util.matchGloss the "() frog" is splitted by spaces, which results in a "()" word. That word is not found in the wikiline provided by util.getTransTable so the script reports Could not find translation table...

It seems that it can be fixed by changing util.getTransGloss to get the text recursively. There are probably some nested tags in the translation headers somewhere (like '''''bold and italic'''''), so recursion would be the most error proof solution:

getTransGlossText: function (node) {
  var ret = '';
  var children = node.childNodes;
  for (var i=0; i<children.length; i++)
    if (children[i].nodeType == 3)
      ret += children[i].nodeValue;
    else if (children[i].tagName.match(/^(i|b)$/i)) // recurse into I and B tags
      ret += util.getTransGlossText(children[i]);
  // All characters except a-zA-Z0-9 are changed to spaces.
  // Handles differences between the HTML output and the corresponding wiki text.
  return ret.replace(/\W/g, ' '); 

getTransGloss: function (ul) {
  if(children[i].className && children[i].className.indexOf('NavHead') > -1)
    return util.getTransGlossText(children[i]);

Maybe I missed the real cause, since I don't know Javascript, how to debug the code and run the modified version.
Karelklic 19:17, 14 April 2009 (UTC)

Hi, thanks for the suggestion. Somethings just come up here, but I'll look in more detail later. My hope was to be as simple as possible and ignore all wikitext - even if I get "(biology)" it won't match the wikitext which will look like (biology) or (biology) or (biology). I think I will get the text recursively and then replace out all ascii chars. Or I could just use .innerText (or .textContent, or both...). If you want to get your own local copy for debugging, just create User:Karelklic/editor.js and modify your monobook.js like User:Conrad.Irwin/monobook.js. Conrad.Irwin 19:57, 14 April 2009 (UTC)
Thanks. You are right about the "(biology)" problem.
I updated the proposed solution. Now it works with abort, stick, and it should work even with Template:legal as we do not recurse into SPANs.
Karelklic 23:52, 14 April 2009 (UTC)
Cool, I'll do a quick test, and then upload it. Thank you very much! Conrad.Irwin 00:06, 15 April 2009 (UTC)
Committed changes. Conrad.Irwin 00:15, 15 April 2009 (UTC)

I tried to add a Korean word, but it kept blanking itself and would not enter anything. Now all of the boxes on every page are expanded and have a "ko" in them, and when I shrink them and remove the "ko", they ignore me and revert. How can I get it to shrink again? —Stephen 14:44, 15 April 2009 (UTC)

If a hard refresh and clicking "less" doesn't fix it. Then remove your cookies for wiktionary. 19:29, 15 April 2009 (UTC)
I managed to get it to work for Portuguese (Nazism), which resulted in the box shrinking back. But when I tried to do Yiddish, it blanked the entry and returned "Could not find translation entry for 'yi:נאציזם'. Please reformat". I had to enter the Yiddish manually. —Stephen 03:34, 16 April 2009 (UTC)
Attempting to enter the Yiddish caused the same problems as the Korean. Now the box is expanded again and won’t contract. I tried refreshing and clicking "less", but it makes no difference. So far I haven’t found anything that looks like a Wiktionary cookie. —Stephen 03:43, 16 April 2009 (UTC)
Nazism was an unfortunate choice of page, as the code to handle {{trreq}} had not yet been written. This should now be fixed. Sorry. (Are there any other templates I'm likely to come across, modulo {{ttbc}}) Conrad.Irwin 11:21, 16 April 2009 (UTC)

noted you added support for language codes with - in them, but you haven't (yet) got the general case. You want something like:

[a-z]{2,3}(-[a-z-]{1,7}|) or [a-z][a-z][a-z-]{0,8} would be okay

it is 2 or 3 letters, optionally followed by - and 6-7 more, that may contain -. Limit is 10. I usually just use [a-z-]{2,10}, although that allows "--abc" and other such nonsense (;-). We have zh-min-nan for example. (Although in that case we want to use cmn.) And, e.g., be-x-old (which, perhaps fortunately, has no wikt ;-) Robert Ullmann 14:43, 15 April 2009 (UTC)

Thanks. Will do. 19:29, 15 April 2009 (UTC)

If I enter and preview an addition, then undo, then enter and preview again, all three page editing buttons are disabled, and I'm stuck until I reload the page. Enter and preview, [x] in the page controls to cancel, enter and preview again, and the buttons are disabled also.

Just a heads-up. I can do some more testing and produce a more detailed report if it would help. Tested in Safari 4 public beta (for Mac). Michael Z. 2009-04-15 19:23 z

I had timing problems in firefox. Maybe it's a similar issue. I've got a windows Safari 4 to play with, so I'll have a play now. 19:27, 15 April 2009 (UTC)
I've set them to always be enabled, which while not ideal, is the only solution I've found. .disabled is being correctly set to "false" but the browser doesn't seem to notice. Conrad.Irwin 19:52, 15 April 2009 (UTC)

The add translation tool now works for IE7 but a problem remains: it does not add the entry in alphabetical order. For example, I added the Dutch translation to "hyperbolic" and it appended it to the end of the list, on the right side, whereas on Firefox it would (in the preview) show up in the correct place, between Czech and French, on the left side. —AugPi 02:18, 16 April 2009 (UTC)

Another problem: when I tried adding a second Dutch translation ("oudheidkunde") to "archaeology" in IE7, it would also append it to the end of the list, on the right side, ignoring the pre-existing Dutch translation on the left side. Then I tried Firefox which merged the new term with the old one, separated by comma: correctly. Also, the superscripted link to nl.wiktionary should not be positive (blue) but negative (red) because there is no "oudheidkunde" entry in nl.wiktionary. —AugPi 02:45, 16 April 2009 (UTC)

Now, I noticed that the AutoFormat bot corrected my "hyperbolic" edit. —AugPi 02:53, 16 April 2009 (UTC)

Now fixed. Yes, the sorting isn't perfect precisely because only AutoFormat knows what the real order is :D. Should now be a good enough guess that it looks right, and appends new translations to existing language sections. Conrad.Irwin 10:23, 16 April 2009 (UTC)

Does the permanent disable code assume that one has WT:PREFS enabled? I don't, and adding the code above hasn't done what it says it would, tho the disable button above did work. — Carolina wren discussió 04:04, 16 April 2009 (UTC)

No, the "Preferences" referenced there is specific to editor.js, that's really bizarre because the button just runs that code once. (The advantage of putting it in your javascript is that it runs it every time you log in). Conrad.Irwin 10:10, 16 April 2009 (UTC)

First, thanks a lot for a great great script ... I've never added this many translations before! Just wondering, how much work is it to import this script to other Wiktionaries? Would one have to do heaps of changes to it? --Eivind (t) 08:17, 16 April 2009 (UTC)

The first few hundred lines are boilerplate code that you can copy straight off. The hard bit is creating the plugins, at the moment there are two plugins one which adds translations (it's awfully in need of repair already ;D), and one which balances them (which is pretty nice still). If you were to transfer it to another Wiktionary (I have no time to do that currently, as my wiki-time is devoted to getting it working better here), you would need to write new plugins. Writing plugins isn't that hard in principle, you just need to create objects with three properties (redo, undo, edit and summary) and call "new Editor().addEdit()" with it. The "redo" and "undo" function modify the HTML page to provide a preview to the user, and the "edit" function edits the wikitext to provide the change; the complicated bit is ensuring that the HTML modifications accurately reflect the change - though "new Editor().page.parse()" will use the API to parse wikitext which can help. It would take a day or two of competent javascripting from someone who knows the formats used on the Wiktionary intimately. Conrad.Irwin 10:09, 16 April 2009 (UTC)
If I find a time for it, I plan to add it to the French Wiktionary... It's a matter of time. :( --AglarEdain 06:33, 17 April 2009 (UTC)
Cool. If you want to ask questions about it, I'm normally in irc://irc.freenode.net/#wiktionary as cirwin. Conrad.Irwin 09:00, 17 April 2009 (UTC)
I adapt this tool for Lithuanian Wiktionary. That is great script. --Vpovilaitis 08:39, 22 May 2009 (UTC)
Great! What changes did you have to make? Conrad.Irwin 21:39, 22 May 2009 (UTC)
In Lithuanian Wiktionary are use translation line (in exampl for english translation of word run:
{{env1}} {{t+|en|run}}


for this reason was needed to change line parsing code and new translation line formating code, include Lithuanian names of languages and its changing to 2-3 simbol codes. And was needed translate messages and interface to Lithuanian language. You can see this code lt:Naudotojas:Vpovilaitis/editor.js. --Vpovilaitis 14:05, 24 May 2009 (UTC)

When trying to add "benzoile" as the Italian translation of benzoyl I get error message "Could not find translation table for 'it:benzoile'. Please improve glosses". SemperBlotto 22:01, 16 April 2009 (UTC)

Fixed, though I need to do more work on this. Conrad.Irwin 09:15, 17 April 2009 (UTC)


Firstly, I want to report the jscript works fine with my Safari Version 3.2.1 (5525.27.1) running on Mac OS X 10.5.6 (9G55).

Secondly, I work to add French translations everywhere they're lacking (supposing I'm able to understand the definition) AND I WANT TO THANK YOU!

Until now, adding translations was hard work... Since then, with the great help of your awesome script, it's still work but it's easier. I think I will be able to work twice faster, maybe three times.

I can only find one criticism: The blue window is not so much easy to target on its top-left corner for new users. And it's only a small detail.

Really, thank you. May I say I love you. No, it's exagerated. But I really appreciate your concern about translation adders.

Best regards.

--AglarEdain 06:29, 17 April 2009 (UTC)

I've tried getting the window to flash bright green briefly, maybe this will make it easier to spot without hurting the eyes of other people too much. Conrad.Irwin 09:16, 17 April 2009 (UTC)
On my computer (XP running Internet explorer, the save buttons and greenbox appear underneath the stuff at the top of the page. These buttons should be included with the preview buttons and stuff, not shunted aquardly somewhere else.
If you clear your cache (ctrl+shift+F5) they should now appear above stuff in the top-left of your window, it's still not close to the preview stuff because I wanted to emphasise that you can make many changes and then one save. Conrad.Irwin 14:20, 17 April 2009 (UTC)

I now get the left/right balancing arrows, but not the option to add a translation. SemperBlotto 08:31, 20 April 2009 (UTC)

Now fixed. Sorry. Conrad.Irwin 09:38, 20 April 2009 (UTC)
Thanks - now OK - and can confirm it works with IE8. SemperBlotto 09:45, 20 April 2009 (UTC)

As we've discussed to keep the GUI sharp we really want to store facts about many languages in the Wiktionary: namespace just as we now store full English names for language codes. These facts I shall call "metadata".

There are a few basic differences in the major languages that will affect the GUI, and a whole bunch of exceptions we will have to put off until later.

  • Does this language use a script other than Latin?
  • If so which script?
  • If so provide a transliteration field in the GUI.
  • (exception: multiple scripts)
  • Does this language have grammatical gender for nouns?
  • If so which genders?
  • Provide these gender options in the GUI.
  • (exception: genders for other parts of speech)
  • Does this language have plurality of nouns? (Chinese and Japanese don't)
  • If so provide a field for the plural.
  • (exception: what about countable/uncountable)
  • Does this language have optional diacritics or vowels? (Hebrew, Latin)
  • If so provide a field for the full spelling and the basic spelling.

Any thoughts? — hippietrail 12:52, 20 April 2009 (UTC)

In the near future I'd like to store these in the script itself, there is already some metadata there, the two further options are either to store them in some custom storage on the toolserver, or to store them in Template space so that other on-wiki can use them. It's not high priority for me at the moment, I'd rather support nesting and editing first, but if you want to implement this, I'll be happy to merge the changes. Conrad.Irwin 13:01, 20 April 2009 (UTC)
Have a look at my metadata version of editor.js at User:Hippietrail/editor.js - it checks when you change the language code whether the new language has certain features and it automagically shows/hides the more/less section depending on whether the language uses either transliterations or optional vowels or diacritics. The text of the more/less button is not yet synched or I would be bold. The step after that is to make individual fields such as gender and plural hide/show. — hippietrail 01:17, 23 April 2009 (UTC)
Looks nice, though I wonder whether, if the user has explicitly opened the "More" box, it should stay open; and whether clicking More explicitly should show all the hidden components - just in case we have an error in our metadata. Conrad.Irwin 09:01, 23 April 2009 (UTC)

(Low priority.) If the only change is rebalancing, can it refuse to save (since AF will do the same, and also make other fixes, so don't waste the edit)? (I guess I should say, "Can the Save box only appear if a translation is added, not on rebalancing", but I'm not sure.)—msh210 17:37, 21 April 2009 (UTC)

I was going to tinker with not showing the balance buttons until a translation had been added - yes, I think that's a good idea. Conrad.Irwin 17:44, 21 April 2009 (UTC)
How about a third button that automatically balances? And how about a standard balancing algorithm so that AF and editor.js do it the same way perhaps? — hippietrail 03:56, 22 April 2009 (UTC)
As it will (normally) require just one ← or → I don't see too much problem with the user doing it and it makes my life much simpler. I'm not saying I won't do this, but at the moment there are many more pressing things to resolve; if you want to implement it, please feel free. Conrad.Irwin 09:14, 22 April 2009 (UTC)

Hey guys it's really too hard to track bugs and features on talk pages. That's why I fought for our right to use the Wikipedia Bugzilla for stuff exactly like this. Please make use of it, it's very handy and it's being neglected:

hippietrail 01:10, 23 April 2009 (UTC)

The main problem with bugzilla is that you don't instantly get to see all previous related discussion; and if you couple that with the need to create an account to use it, the techy-orientated interface, and the effort involved in getting CCs on a subset of bugs; my net feeling is that talk pages are much more suited to this kind of discussion. Yes, if we had a dedicated development team, that would be better - but as we don't, and bug reports come solely from people who can edit wiktionary, I feel that such discussion should be on the talk pages. Conrad.Irwin 08:58, 23 April 2009 (UTC)

Awesome! The GUI upating on change of language is lovely.

But there are bugs. When I try to "preview" additions I get a bunch of alerts with source code which I guess are exceptions being thrown for some errors.

This is fun to hack with you! — hippietrail 08:31, 24 April 2009 (UTC)

Ach, no those were there for debugging - sorry. You can remove them if you want, there does seem to be a problem when gender for a language is undefined though. Conrad.Irwin 09:21, 24 April 2009 (UTC)
Aha. Undefined gender, undefined language, or both? Examples? — hippietrail 09:58, 24 April 2009 (UTC)
I've been thinking about your reservations with having all the metadata in one data structure. To keep it centralized and make it possible for consumers to get just what they want I might be able to make a data server on the ToolServer. I'll keep the full set of data there and you can call it for which languages and fields you want. Then you can from time to time cut and paste that into your code. Seems like a bit of trouble but it's the only way I can think to keep it centralized and minimal for more than one application. Now to reenable my toolserver account... — hippietrail 07:55, 25 April 2009 (UTC)
That would make sense, it would also be useful if languages were divided into a few (largish) chunks, so that you can request lots of meta-data at a time. One chunk could be ISO 639-1, and then perhaps by letter for ISO 639-3. Conrad.Irwin 09:18, 25 April 2009 (UTC)
You mean request all languages which have ISO 639-1 codes? I could set it up as an actual database in which case it could be queried by any field really. It would be a pretty small and straightforward database so should be pretty fast and it would be read-only. But I think I'll do it as a Perl program first since I don't like databases until I really need their functionality (-: — hippietrail 12:19, 25 April 2009 (UTC)

I guess it would probably not be too easy to implement but Connel did hack Edittools to work with the search box once.

It's especially needed for languages that use non-Latin script and need rare diacritics for transliterations. Keyboard layouts don't have both )-: — hippietrail 11:08, 24 April 2009 (UTC)

Doesn't your operating system offer something that works everywhere? It seems a waste of resources to duplicate OS functions which are not specific to Wiktionary, like international text entry.
If you use a Mac, you can enable multiple keyboard layouts in System Preferences > International > Input Menu, and switch between them with the keyboard menu. Also enable the Keyboard Viewer to help learn the layouts, and the Character Palette for access to all of Unicode. If you're determined, you can make custom keyboard layouts with Ukelele (I have made two that I use all the time). Michael Z. 2009-04-24 14:23 z
I have four keyboard layouts installed. I am not aware of any keyboard layout which includes for example both Devanagari and the Latin letters with the diacritics needed for the IAST transliteration. Many of these diacritics are not available on any keyboard layout at all.
Rare character input as such is not an operating system function but a function of EditTools, which has filled this need and has been expanding for several years now on the English Wiktionary and has spread to many other wikis besides. But it does not allow entering rare characters into the editor.js fields, just the main text editing area. — hippietrail 15:53, 24 April 2009 (UTC)
There's no reason to restrict specialized text entry to wiki sites. It could certainly be useful on other websites, in your word processor, email program, etc. This is properly a function of the OS.
If you're using a Mac, then I can help create a keyboard layout for Devanagari + IAST. Perhaps the caps lock key can toggle between two modes. If IAST transliteration is deterministic, then another option is to create a text filter which converts any selected text to IAST, prompted by a Services menu item or keyboard shortcut. I'd have to do a bit of research, but I'm sure this is possible. Michael Z. 2009-04-24 16:20 z
Edittools exists precisely because people don't want to/don't know how to reconfigure their computer just to (in practice) use wiktionary. Yes, it would be great if everyone had all the keyboard layouts they need to hand; no it's not practical to assume them will [including people who use Wiktionary all the time, not just the one-timers or newbies]. Similar functionality to what you describe exists under Windows and Linux, but people are generally reluctant to tweak configuration (bizarre, I know). I don't have the time to put edittools there myself, but it shouldn't be too hard to steal User:Connel MacKenzie/keypad.js and modify it. (Though a much better {for everything} solution would be to move all of edittools into a javascript file that is include on edit pages and when the user clicks some button to show it). Conrad.Irwin 09:25, 25 April 2009 (UTC)
I planned to write that I'm not complaining about Edittools. But the more I think about it, the more I feel that this kind of work could be problematic in principle. I did go to some trouble to hide this and reduce other interfering page clutter in my Wikipedia user style. A developer spends energy duplicating OS functions for the project, and then I have to spend further energy hiding his work because it is obtrusive. We are working against each other. Edittools is unfinished or inadequate unless it works in every single text-entry field in Wiktionary, for both readers to search and editors to edit, but if it were completed, then it would sorely interfere with the site.
I do sympathize with the nightmare that changing even minor settings can become for Windows users. But the more specialized a computer user's needs, the more they need to use technical solutions to fulfil them. If they need to type Devanagari, then it may just make sense for them to learn how to bring up the Character Palette or Devanagari keyboard layout. Our resources are better spent helping them use their computers, then making a half-baked copy of software that they already have (great respect to our developers, but we don't have the resources and software framework of Apple or Microsoft).
I'm not able to help Windows users, but I am willing to help create a Mac keyboard layout if it will make a big difference for a Mac editor here. Michael Z. 2009-04-25 18:33 z
You are more than welcome to develop and announce on Wiktionary all the keyboard layouts you like. I can't afford a Mac. I don't know which OS our major Devanagari contributor, Dijan, uses or how he currently enters his scripts and transliterations. If you look through the edittools list you will see which alphabets, scripts, and sets of diacritics are used here. We use scripts including Arabic, Armenian, Bengali, Cyrillic, Devanagari, Ethiopian, Georgian, Glagoitic, Greek, Gujarati, Han, Hebrew, Hiragana, Kannada, Katakana, Khmer, Lao, Latin, Malayalam, Oriya, Punjabi, Sinhala, Tamil, Telugu, Thai, Tibetan. I've probably forgotten a couple. Some are used for more than one language and sometimes need different transliteration diacritics in different languages. And of course there are the pronunciation systems too. Others are not in great use here yet and might not have evolved one standard set of transliteration diacritics. Maybe if you ask on the Beer Parlour which of those would be most appreciated for our Mac-owning contributors you would know where to start first. Good luck. — hippietrail 00:08, 26 April 2009 (UTC)
As I've mentioned before (a while ago now), edittools should be moved into Javascript and there should be a way to enable it for all text boxes. Whether or not it is useful to you is irrelevant, the fact that almost every Wikimedia project uses it should convince you that it is, if totally "incorrect" from a technical point of view, a necessity for users. The chances are, if it were well written javascript, it could be a standalone library that any site could easily include to provide highly multilingual input. It is on my todo list, but it's a long way down. Conrad.Irwin 00:35, 26 April 2009 (UTC)
  • Edittools is actually part of MediaWiki rather than part of Wiktionary but it is customized by each site. There are a number of bugs and feature requests on BugZilla to address its inadequacies. Perhaps it would be more constructive to comment there where you will reach a much larger audience: https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=edittoolshippietrail 05:28, 26 April 2009 (UTC)
Well, I'm in favour of Conrad's plans, where do I vote? When I edit a page, EditTools bloats the requested HTML from 24 kB to 245 kB – that's one thousand percentMichael Z. 2009-04-26 16:21 z

See the recent history of cyclical.—msh210 17:27, 27 April 2009 (UTC)

Meh. You any good at user-interface design? - because apparently I'm not :(. Conrad.Irwin 23:17, 27 April 2009 (UTC)

Hi. Am I doing something wrong? I get an error saying "Could not find translation entry for '...'. Please reformat" every time I try to add a translation not to the first table. In eat, for example. It's the same in Opera 9, Firefox 3, IE8. Hard refresh doesn't help. --Vahagn Petrosyan 08:57, 28 April 2009 (UTC)

My apologies, I broke it a few days ago without noticing. (Why the function for searching for strings behaves differently from the function for searching for regular expressions only the language "designers" know). It should now be fixed if you clear your cache (ctrl+shift+F5). Conrad.Irwin 09:21, 28 April 2009 (UTC)
Thanks! --Vahagn Petrosyan 10:03, 28 April 2009 (UTC)

How do I add a translation under "Chinese"? You're excellent translation adding device will only let me add "Mandarin", but Chinese is the name that most people add translations under.

Fix {{zh}} or make a new language template, {{zh-real}} that will return Chinese. Please be patient, there are many other things I need to fix, and I have little time to fix them. (If you know javascript, you can probably help) Conrad.Irwin 09:14, 29 April 2009 (UTC)

I use {{zh-cn}} or {{zh-tw}} sometimes. But if the entry has Simplified Chinese and Traditional Chinese both, I use {{zh-ts}} instead of this tool.--Dingar 01:59, 30 August 2009 (UTC)

Hi. For {{cv}}, {{kk}}, {{ky}}, {{lez}}, {{mn}}, {{os}}, {{tg}}, {{tt}} languages {{Cyrl}} script should be automatically guessed. Can you add that?
And another small thing: I think it would be nice if the "Undo" button would fill back the boxes with the translation which is being undone. I, for example, almost always use Undo when I notice a typo after pressing "Preview translation". This way one wouldn't have to repeat the content. --Vahagn Petrosyan 08:33, 3 May 2009 (UTC)

Aha! Language metadata is my territory now. I'll add them right away. — hippietrail 10:12, 3 May 2009 (UTC)
Mongolian was already there but I've added the others too. Did you notice we can now also display just the appropriate fields for gender, plural, transliteration, and alt forms too? If you let me know those traits of the languages I'll add that as well. — hippietrail 12:10, 3 May 2009 (UTC)
Nice! Here are some traits I know:
{{az}} - leave nothing
{{crh}} - leave nothing
{{cv}} - leave only transliteration
{{kk}} - leave only transliteration
{{ky}} - leave only transliteration
{{os}} - leave only transliteration
{{tg}} - leave only transliteration
{{tk}} - leave nothing
{{tt}} - leave only transliteration
{{uz}} - leave nothing --Vahagn Petrosyan 16:02, 3 May 2009 (UTC)
Just to be sure I haven't misunderstood are you saying that noun of these languages have plurality for nouns? I thought that was rare outside East Asia. — hippietrail 22:49, 3 May 2009 (UTC)
OK done except for plurality until I hear some more. — hippietrail 23:28, 3 May 2009 (UTC)
Plurality had to be kept, of course. Now it's all correct. Thanks! --Vahagn Petrosyan 07:52, 4 May 2009 (UTC)

Hoi, I added a few translations and found the following

  • When there is whitespace in front and at the end of a new translation, the software fails.
  • When you remove this whitespace manually, the "other" magic does not happen

Thanks, GerardM 08:04, 4 May 2009 (UTC)

Hi, I will fix this by just stripping the whitespace from front and back, but I am confused by what you mean by "other magic"? Conrad.Irwin 09:13, 4 May 2009 (UTC)

It would be really nice if there were a way to request translations with editor.js adding {{trreq}}.

I'm not sure how to add it elegantly to the current GUI though. It would be better if the GUI wasn't there all the time but just had a couple of buttons [Add translation] [Request translation] that would bring up the rest of the GUI. — hippietrail 06:21, 7 May 2009 (UTC)

I'd put it under "More" as a seperate button, probably alongside a "TTBC" checkbox (as requested at the top of the page). If we decide to do anything other than translations, then we will need some way of turning the buttons on and off - the good thing about the translations is that the editing form is hidden.Conrad.Irwin 09:39, 7 May 2009 (UTC)
I just had an idea. How about keeping the edit form hidden until a big shiny new edit button between the arrow buttons on the table is clicked? The pages looks incredibly cluttered on a small screen with several small translation sections and a huge edit box in each one. — hippietrail 22:01, 7 May 2009 (UTC)
One of the aims of having the translation interface was to encourage people to add translations - already one of our strongest areas, but still very very incomplete. While this is possible, I think it would defeat part of the purpose; I envisage (at a later stage) having some kind of interface at WT:EDIT where people can choose which interfaces are visible by default. Conrad.Irwin 22:57, 7 May 2009 (UTC)

If you already saved the page, and try to save another edit on the same page, the log at the top left disappears. Thus you don't know what the script is actually doing. -- Prince Kassad 14:39, 8 May 2009 (UTC)

Fixed. Conrad.Irwin 02:19, 10 May 2009 (UTC)

editor.js currently just adds the edit comment "Assisted" with notes on which languages were added. But it should have in the "More" GUI a place to add a specific comment as well. For instance I just added several translations to alphabet from Wikipedia and I wanted to note that's where I got them from. — hippietrail 23:45, 8 May 2009 (UTC)

This can be added, I was waiting for you to commit your changes to alt-form generation before I played around too much. Conrad.Irwin 17:50, 9 May 2009 (UTC)
Ah OK I wondered why you hadn't been doing much. It's a rainy Sunday morning so I might get that done soon. — hippietrail 22:48, 9 May 2009 (UTC)

Hi, Conrad. I see you’ve added automatic transliteration to your TODO list. I don’t know how you’re planning to do it, but is it conceivable that some day the same functionality could also be used in inflection templates like {{ru-noun}} or {{hy-verb}} and everywhere else? --Vahagn Petrosyan 11:58, 10 May 2009 (UTC)

Well, in theory, yes. In practicality, not unless someone writes an extension (not that hard) and it then gets implemented on Wiktionary (very much harder, thanks to politics). It would also be possible to create some kind of Javascript that could create a button that when you clicked it, could transliterate some text in the edit box. In the general case, complete transliteration may not be possible automatically, but I think in a majority of cases a very good guess can be made. Are there any common problems that you can for-see an attempt like this running into? My current plan is to do something like User:Conrad.Irwin/ipa2sampa.js with a few hacks for specific problems in specific languages. Conrad.Irwin 12:53, 10 May 2009 (UTC)
At first, I thought it was better to rigidly bound transliteration feature to inflection templates like {{ru-noun}}, so that there was no way of changing the automatic transliteration result. That way we would be consistent with our transliteration standards because right now there are as many de-facto transliteration schemes, as there are editors. But now I see Javascript button is the way to go. With such button it’ll be possible to transliterate not only the inflection lines, but also Synonyms, Related terms, declension tables, etc., like in շեն. As to the problems that could arise, I don’t know Javscript, so can’t answer.
By the way, is User:Conrad.Irwin/ipa2sampa.js working? I've imported it, but I don’t see new buttons. I think I can use it for transcribing Armenian letters into IPA in pronunciation sections. The correspondence in armn2ipa.js will be regular 95% of the time. --Vahagn Petrosyan 14:36, 13 May 2009 (UTC)
No, it doesn't do anything, sorry - just proof-of-concept code. You say armn2ipa is 95% regular, how regular is Armenian -> transliterated Armenian? Conrad.Irwin 15:02, 13 May 2009 (UTC)
It’s 100% regular. But only if it is possible to take into accout this hack: the letter ու consists of two Unicode characters and should be transliterated as u. But whenever it’s constituent characters (independent letters themselves) are encountered separately, they should be transliterated as: ո - o, and ւ - w. Also, Georgian transliteration is 100% regular. So are Ukrainian, Belarusian, Bulgarian, Russian (no matter what Wiktionary:Russian transliteration says right now) and a dozen of other Cyrillic alphabets. --Vahagn Petrosyan 15:31, 13 May 2009 (UTC)

I'm just entering a couple of words from my Guatuso grammar. It turns out the Ethnologue/ISO/Wiktionary name for Guatuso is "Maléku Jaíka". editor.js just put "Maléku Jaíka" after "Maltese" which is wrong but it would be a bit of a pain to do either localised or accent-stripped sorting of language names in JavaScript. — hippietrail 07:20, 13 June 2009 (UTC)

The order is the same for AutoFormat, so it's "correct" in a way. By this order, Maléku Jaíka sorts after Malto and before Mam, and Ömie sorts all the way after Záparo, but still before ǃXóõ. If you try to change the order, AutoFormat will fix it anyway. -- Prince Kassad 08:25, 13 June 2009 (UTC)
I know it's a minor issue depending on your perspective but it's correct only in a "sorting by binary value" way which is meaningless to dictionaries and dictionary users. On which platform does AutoFormat run? If on *nix at least it shouldn't be hard to fix. And which programming language is it in? My next/previous extension sorts correctly using Perl running on Linux. It uses the underlying *nix UTF-8 locale which I think uses some official Unicode collation algorithm. This is not easy to achieve for editor.js but should be pretty easty to achieve for AutoFormat. I can help if need be. — hippietrail 08:41, 13 June 2009 (UTC)
I won't fix this. If you want the order to be correct, fix AutoFormat which will re-sort the entry after a few minutes if it is wrong on save. (Solution two, change the language name to Guatuso :p) Conrad.Irwin 09:35, 13 June 2009 (UTC)

Hi! First, thank you for this wonderful tool. Here is what brings me here: in the molt entry, when I push the <-- button in one of the translation tables, editor.js tells me that it can't find {{trans-mid}}. However, I fail to see anything wrong in the wikicode. Is this a bug? — Xavier, 15:20, 21 June 2009 (UTC)

Indeed, I can confirm this bug. It's not high priority since AutoFormat corrects any such translation tables, but it should be fixed. -- Prince Kassad 15:31, 21 June 2009 (UTC)
Should now be fixed, I'd forgotten that number points to the start of the line, while the other points to the new-line character just before it. Conrad.Irwin 17:11, 21 June 2009 (UTC)
Fixed, thank you! — Xavier, 21:48, 27 June 2009 (UTC)

Thanks for this great tool. One problem however: The gender check boxes disappear when I enter "nb" (Norwegian Bokmål) as language! (Should have the same genders as Norwegian.) Håkon 07:30, 23 June 2009 (UTC)

That's my fault. editor.js gets its data about which genders a language has from my language metadata server on the Toolserver. I probably wasn't sure whether Bokmål had 2 genders like Danish or 3 genders like Nynorsk. I'm on holiday and behind a firewall right now but I'll try to fix it as soon as I can. — hippietrail 01:44, 24 June 2009 (UTC)

Form of the tool is shown on printable version. Can somebody disable displaying of it while printing? --Alexander Widefield 15:45, 27 June 2009 (UTC)

now fixed if you clear your cache (ctrl+shift+F5). Conrad.Irwin 23:04, 3 August 2009 (UTC)

An interesting diff.​—msh210 22:13, 29 June 2009 (UTC)

See recent history of [[goodbye]].​—msh210 23:19, 2 August 2009 (UTC)

Fixed if you clear your cache (ctrl+shift+F5). (I think I introduced that regression when adding warnings about commas). As to the section above, I had hoped to have fixed that error shortly before you made that report - but I struggle to replicate it; if it is a persistent problem I can have another look - but otherwise I'll just shuffle it under the carpet for the moment (though if someone with more patience than me wants to replicate the conditions necessary for it, please let me know). Conrad.Irwin 22:36, 3 August 2009 (UTC)

Slovene could use this... replacing the accented characters manually is a bit of a drag. I'm not sure of all the possible combinations, but Slovene has five (or six) vowels (a, e, i, o, r (yeah), u) and 3 accents, acute á grave à and circumflex â. So theoretically 36 possible changes, counting lowercase and capitals and assuming each vowel can take each accent (which they probably can't, but just to be safe, you know).

They're all optional (ie only used in dictionaries and stuff) and shouldn't appear in pagenames. Thanks :) — [ R·I·C ] opiaterein — 01:43, 4 August 2009 (UTC)

Don't forget <ẹ> and <ọ>, and combining diacritics as accents on them! Also, combining diacritic would be used for <r̀> and <r̂>. Also, sometimes inverted breve is used instead of circumflex, so adding those as alternative cases would be advised.. --Ivan Štambuk 01:57, 4 August 2009 (UTC)
I've never seen the more complicated ones, I just wanted to make sure at least the basics were covered :D — [ R·I·C ] opiaterein — 02:22, 4 August 2009 (UTC)
Should I remove the under-dot from ẹ and it's other accented forms? I'm not sure if an error (like the inverted breve) should be ignored as that will presumably make occurrences of it harder to find in addition to providing a reason to perceive it as correct instead of an error. Conrad.Irwin 22:49, 4 August 2009 (UTC)
Ok, I've partly answered my own queries by looking at w:Slovene_language#Prosody. I am taking it on faith, and using the following:

And also removing: u'\u0301\u0300\u0302\u0311\u030f\u0323' (COMBINING ACUTE ACCENT, COMBINING GRAVE ACCENT, COMBINING CIRCUMFLEX ACCENT, COMBINING INVERTED BREVE, COMBINING DOUBLE GRAVE ACCENT, COMBINING DOT BELOW). Let me know if this is problematic or overkill. Conrad.Irwin 23:15, 4 August 2009 (UTC)

Yessir... the only characters that have non-optional accents are č, š, ž and their majuscule forms.
All of them might be overkill, I don't think I've ever seen the ones with double acute/grave used, but it's probably possible in some dialects, so... better to have it than not, I guess. — [ R·I·C ] opiaterein — 23:17, 4 August 2009 (UTC)
There ya go then, (I'll still say clear your cache (ctrl+shift+F5) because I like the template). Conrad.Irwin 23:28, 4 August 2009 (UTC)
Lol thanks man :) — [ R·I·C ] opiaterein — 23:41, 4 August 2009 (UTC)

There appears to be a pretty serious bug when you want to add multiple translations at the same time, and the new translations happen to be in a row of three (say, there's a Finnish and a Slovak translation, and you want to add German, Greek and Serbian, and the midpoint is not in this group). Then the following two things can happen when trying to add the third translation:

1. The third translation would end up in-between the first two. In this case you simply get an error.
2. The third translation would end up at the beginning or at the end of the group. In this case the translation will be shown correctly in the table, but it will not be saved when you click Save.

It used to work before so this seems to be a regression. It should be fixed as soon as possible. -- Prince Kassad 13:05, 21 August 2009 (UTC)

Urm, that sounds bad. I will look at it when I get the time, hopefully this week-end but I can make no promises. Conrad.Irwin 22:39, 21 August 2009 (UTC)
I tried adding Swahili Swedish and Tajik to WT:SAND in a few orders, and I got no error message, and it saved correctly. Can you be more specific with where you found problems? Conrad.Irwin 23:37, 23 August 2009 (UTC)
Indeed it doesn't work with that combination. Try the following combination for the first bug (where it breaks with an error): kum, lez, lbe (in that order). This always seems to work for me. (Also, try adding lez first and then all the others, which seems to not work at all for me either) -- Prince Kassad 03:54, 24 August 2009 (UTC)
Should now be fixed, if you clear your cache (ctrl+shift+F5). Conrad.Irwin 16:09, 30 August 2009 (UTC)

Adding the trreqs doesn't work if the language is one of the ones that can have stripped accents and stuff. LT, SL, HE... etc. The error given is the "don't use wiki markup" one. Enjoy :) — [ R·I·C ] opiaterein — 20:05, 2 September 2009 (UTC)

D'oh, I should have foreseen that. Now fixed, {{clear your cache}}. Conrad.Irwin 23:46, 2 September 2009 (UTC)

The editor's stopped working for me. I've cleared my cache, I've cleared all my temporary files and cookies, I've purged, and I still can't get it to appear. It works on Safari but not on IE8. —Internoob (TalkCont.) 17:42, 5 September 2009 (UTC)

Maybe I'm having this same problem. The error I'm getting is "Could not find translation entry for 'ca:parkour'. Please reformat". It worked immediately before, on this edit, but stopped after that. — [ R·I·C ] opiaterein — 22:19, 5 September 2009 (UTC)
Your problems are now sloved if you clear your cache (ctrl+shift+F5). (Internoob: I forgot to test in Internet Explorer recently, and as a result was using osome techniques that fail to work there). (Opiaterein: When it detects there is a trreq in the HTML it looks for the trreq in the wikitext, but on parkour the trreq was nested under the heading and so it tried to look for {{trreq |Chinese}}, which of course does not exist in the wikitext). Conrad.Irwin 23:45, 6 September 2009 (UTC)

The editor does not allow any more translations to be added after the X in the small box that appears in the top-left corner is clicked until the page is reloaded. Could you fix this please? BTW, the editor works in chrome 3. --Yair rand 05:35, 21 September 2009 (UTC)

This should now be fixed if you clear your cache (ctrl+shift+F5). Conrad.Irwin 00:56, 23 September 2009 (UTC)
Works great, thanks :) --Yair rand 04:20, 23 September 2009 (UTC)

After I added the Hindi definition to laudable and then tried to balance the table, it gave me this rather lengthy error message: ERROR:[Error: name: ReferenceError message: Statement on line 1709: Undefined variable: console Backtrace: Line 1709 of linked script http://en.wiktionary.org/wiki/User%3AConrad.Irwin%2Feditor.js&action=raw&ctype=text/javascript&dontcountme=s: In function editWikitext console.log(direction); Line 1701 of linked script http://en.wiktionary.org/wiki/User%3AConrad.Irwin%2Feditor.js&action=raw&ctype=text/javascript&dontcountme=s function (text) {return editWikitext(right, direction, text);} Line 398 of linked script http://en.wiktionary.org/wiki/User%3AConrad.Irwin%2Feditor.js&action=raw&ctype=text/javascript&dontcountme=s ntext = edit.edit(currentText); Line 1698 of linked script http://en.wiktionary.org/wiki/User%3AConrad.Irwin%2Feditor.js&action=raw&ctype=text/javascript&dontcountme=s: In function prepareEdits editor.addEdit({ Line 1662 of linked script http://en.wiktionary.org/wiki/User%3AConrad.Irwin%2Feditor.js&action=raw&ctype=text/javascript&dontcountme=s function(){return prepareEdits('←', left, right)} ... ] Enjoy :D — [ R·I·C ] opiaterein — 14:51, 21 September 2009 (UTC)

After a couple of edits to poetry, I'm hypothesizing that the problem only comes after already adding translations. — [ R·I·C ] opiaterein — 15:25, 21 September 2009 (UTC)
Hm, I don't notice this bug on water. Can you reproduce this in any way? -- Prince Kassad 17:22, 21 September 2009 (UTC)
This was fixed just after I woke up this morning - it came to me in a dream :). Conrad.Irwin 19:10, 21 September 2009 (UTC)

In this edit (diff), I first added a translation "plove", then realized that it is dialectical, and undid it. The edit summary says 't+da:plov t-balance t+da:pløje (Assisted)', but an additional line with the undone translation was added, leading to a duplicate entry for Danish. I'm using Firefox on a Macbook (OS X 10.6.1)--Leo Laursen – (talk · contribs) 08:47, 1 October 2009 (UTC)

If I request a translation with {{trreq}} then accidentally close the "presence" window without committing my change, then once more attempt to request a translation for the same language I get an error telling me I can't request a translation twice for the same language. — hippietrail 04:33, 5 October 2009 (UTC)

Fixed. Conrad.Irwin 13:59, 5 October 2009 (UTC)

I just used this tool for the first time, and stumbled over the lack of a link to help for the gender checkboxes. A precisely targetted page would be great, but failing that it would be at least useful to link to Wikipedia:Grammatical gender. (I was adding a Dutch translation, but needed to look up what "common gender" meant before I could be sure that "neuter" was really what I wanted.) Hv 11:55, 30 October 2009 (UTC)

Hi, I've added a sentence to the instructions above (which you can get to by clicking the "Add Translation" link on every page). I don't know enough about it to make any authoritative assertions - perhaps someone could create Appendix:Gender or similar (though perhaps the definitions on common and neuter are good enough?). Conrad.Irwin 13:27, 30 October 2009 (UTC)

Hello. Your tool is just great. It helps a lot. I wish we could have this on the French Wiktionnaire (we want it, but we would probably have to adapt the code to our syntax, and nobody has done that - I for example don’t know much about javascript, even less about AJAX and interaction with Mediawiki…). Keep developping such magical things ! --Eiku (t) 22:49, 5 November 2009 (UTC)

Hi, I think two other users so far have shown interest in porting it to fr.wikt - I `think` you'd be able to get away with just changing a bit of code in the "Util" object, and a lot of code in the TranslationAdders block - but I don't have the time to fully support this on any other Wiktionaries myself (I believe it's being used on lithuanian wiktionary, but they forked the code much earlier, when the code was arguably easier to understand and contained less very en.wikt specific features, and I think their template syntax is closer to ours than yours is). I'm very happy to lend a hand to anyone who wants to port it, I'm often to be found in #wiktionary on freenode, or this talk page, or by email. Conrad.Irwin 00:08, 6 November 2009 (UTC)

Is my computer acting weird or is there a glitch? o.O 50 Xylophone Players talk 22:31, 16 November 2009 (UTC)

I think it was changed so you can only t-balance while you're adding a translation. --Yair rand 22:33, 16 November 2009 (UTC)
Yes, there were several instances where people would just click the arrows for no benefit - if you want to use them without adding a translation, then add a translation and click undo, the buttons will still be available. Conrad.Irwin 12:00, 17 November 2009 (UTC)
Okay, thanks for telling me. 50 Xylophone Players talk 17:26, 17 November 2009 (UTC)

There seems to be a small bug with the new table labelling feature. Whenever I click on the "±" icon, it brings me straight to the top of the page. --Yair rand 04:09, 17 November 2009 (UTC)

Should now be fixed. Conrad.Irwin 11:58, 17 November 2009 (UTC)

When the table top contains a vertical bar without gloss such as {trans-top|}, clicking the +/- sign opens the field in the gray bar but the field is not blank, it contains the first translation. This situation is immediately visible on the web page because the gray translation bar contains only the +/- sign but does not contain the word "Translations". --Panda10 22:46, 22 November 2009 (UTC)

Hi, for fro and frm could you add the same options as for French. That is, masculine, feminine, plural (no neuter or common). Mglovesfun (talk) 14:38, 4 December 2009 (UTC)

Finally done. Conrad.Irwin 00:27, 20 December 2009 (UTC)

There seem to be some kind translation sections inside a template e.g. Template:color-colour (verb) in the verb section of color for which the tool does not work. Could this be fixed in the future or should these kind of template-translations be avoided ? Matthias Buchmeier 10:52, 4 March 2010 (UTC)

It cannot be fixed, {{trans-see}} is a better way of dealing with this. One or the other should be converted to an {{alternative spelling of}} entry. (And in a perfect world, we should consistently chose one form of English for all words in this category). Conrad.Irwin 11:15, 4 March 2010 (UTC)

Is there a legal problem with this in that it doesn't tell people that their edits are licensed? (In particular, are, in fact, their edits therefore not licensed?)

Also, it doesn't warn anonymous people that their IP addresses are going to be publicized. While this is probably not illegal, I wonder whether it's against WMF policy, considering that edit pages always so warn.​—msh210 18:20, 19 March 2010 (UTC)

The terms of use are linked to at the bottom of every page, and it clearly explains the licensing stuff, so it's probably not a problem. --Yair rand 02:30, 26 March 2010 (UTC)

#wikimedia on freenode, 21 Apr 2010 (times are off by several minutes from U.S. CDT):

[14:01] <msh210> Hi, all. Is there a WMF-wide policy for its projects that they warn an anon that his edit will reveal his IP address?
[14:04] <killiondude> Not that I've heard of.
[14:05] <bastique> It's in the MediaWiki software messages.
[14:07] <msh210> bastique, well, yes, except that enwikt has a JS-based way of editing pages that bypasses the action=edit page.
[14:07] <bastique> well, they should probably adjust that.
[14:07] <msh210> No, the point is that it makes it easy for peopel to edit. That is, the whole point is to bypass the edit page.
[14:08] <bastique> No, there's no policy.  It's good practice.
[14:08] == derp has changed nick to derp|brb
[14:08] <msh210> Oh, okay, thanks.
[14:10] <msh210> May I please copy-paste this conversation to enwikt, Cary, Killiondude?
[14:10] <bastique> only if you change my name
[14:10] <bastique> to...
[14:10] <killiondude> I don't mind.
[14:10] <bastique> Guest183832
[14:12] <msh210> Meaning, I can't quote you by name? That sorta defeats the purpose...  :-/  (I.e., I trust what you say largely because of who you are.)
[14:12] <msh210> thx killiondude
[14:12] <bastique> :)  Of course you can quote me
[14:12]  * msh210 confused
[14:12] <killiondude> bastique likes to joke. :-p
[14:12] <msh210> ah, ok. got it.
[14:12] <bastique> :-ð
If you think it is necessary, I am happy for this to display a notice if you can show me how it should look - probably best to show it on the save dialog, there's nothing trackable at the "preview" stage, and that way all kinds of edit get the warning. Conrad.Irwin 22:57, 21 April 2010 (UTC)

No rush, but Anglo-Norman should allow m., f. and pl. like French, Old French (etc.) Mglovesfun (talk) 18:48, 21 April 2010 (UTC)

How about this. Is it a bug, or more likely clever vandalism? Mglovesfun (talk) 16:07, 27 April 2010 (UTC)

It's a bug I thought I fixed a few months ago... Thanks for sharing. (I'll see whether I have permissions to edit the meta-data stuff for anglo-norman). Conrad.Irwin 17:33, 27 April 2010 (UTC)

When adding translations for Norwegian Bokmål, the interwiki code used is 'nb'. There is no 'nb' dictionary, however, so the code 'no' should be used with the 't' template in stead, which is a dictionary for both Norwegian Bokmål and Norwegian Nynorsk. --Harald Khan Ճ 17:01, 28 April 2010 (UTC)

Definition from Wiktionary
Content avaible with GNU Free Documentation License

Powered by php Powered by MySQL Optimized for Firefox