Since T114105 was merged into this ticket, is there anything I could do to help solve this issue?
Nov 1 2015
Sep 30 2015
Related - perhaps, but not a duplicate. I don't see any problems with the numbering (which is what the other issue is about), sfn-style refs do not appear in re-use menu anyway, so no, this is not a duplicate.
Sep 29 2015
Sep 23 2015
In this GitHub thread one of the guys suggested there is a workaround solution. Could anyone code-literate (Mvolz ?) take a look at the proposed solution? It seems relatively easy (as in: setting boolean value to "yes"), but is it working?
Aug 30 2015
Thanks. Sadly it seems filing this at translation-server Github was a dead-end, apparently there's noone working on it. If only I paid more attention at my programming classes...
Aug 12 2015
Thanks for letting me know. I filed a new issue at GitHub, perhaps the Zotero guys could shed some light on this problem.
Weird as it is, the very same links I checked a couple of minutes before (1, 2) now work - but they are interpreted as web pages (cite web) and not as books, even though Zotero interprets them as such correctly. The link I posted in the issue description above still does not work. I'm at a loss now...
Aug 3 2015
Yesterday evening (CET) we had a citoid outage at Polish Wikipedia. No idea what went wrong, citoid window was simply not there in VE when you clicked on "Przypis" (Polish for "Reference"). I reported it at https://www.mediawiki.org/wiki/Topic:Sgikbv81nxsv7oy6, but it seems the problems disappeared on their own this morning.
May 29 2015
Just to make it clear, "special characters" means most likely any non-Latin 1 character.
Feb 19 2015
@Halibutt @tarlocesilion Thank you. This is very helpful. Unfortunately, Polish is not supported through Apertium presently and due to this the benefit of machine translation will be lacking for Polish users. However, the tool is useful without MT as well and if it helps for you to assess how good/bad the usability is in its current state, we will be happy to set up Polish on the beta environment for testing.
Feb 18 2015
Feb 11 2015
Well, most definitely English <=> all languages listed would be beneficial as English wiki has often the most referenced info even on CEE topics. But it all depends on whether such translation would actually be helpful. If it's anything near Google Translate, then I believe it's easier to copy the text and translate it by hand than to use some machine assistance.
Feb 2 2015
Judging from my experience with Slavic languages, the following could work quite nicely, provided the translation is direct and not through English or any other "middleman" language:
+1 to that. The basic problem with machine-assisted translations is that current systems too often employ English as a middleman (translate from Czech to English, and then from English to Polish). Such translations are mostly useless and even if the resulting text resembles the target language, it is often filled with erroneous statements resulting from such Chinese whispers. A prime example of that is Google translate: it works pretty well for translations within the Germanic group of languages (i.e. between Dutch and English), but is a waste of time in case of most other languages and at best gives some approximation of what the original text is about. We'd have to check if this tool works any better.
Just a quick note on "related languages": the easiest way would be to group the Slavic languages by their branches: Western Slavic (PL, SK, CZ, CSB), Eastern (BE, BE-X-OLD, UK, RU) and Southern (BS, SL, SH and so on). However, all Slavic languages are mutually intelligible to certain extent and the only major problem is transliteration to and from cyrillic (in case of, say, RU-PL translation). Other than that, we could definitely benefit from some machine-assisted translation tool. Let me know how can I help.