Hello,
Am 03/22/2016 um 06:50 PM schrieb Legoktm:
> Hi,
>
> On 03/22/2016 03:52 AM, Jan Lühr wrote:
>
>> Thinking about release intervals, Debian is way slower compared to
>> mediawiki - thus Debian's packages for mediawiki become outdated with
>> very high probability. Is there a chance to
Hi,
On 03/22/2016 03:52 AM, Jan Lühr wrote:
> Thinking about release intervals, Debian is way slower compared to
> mediawiki - thus Debian's packages for mediawiki become outdated with
> very high probability. Is there a chance to see debian packages built by
> mediawiki some day soon?
The
Yeah ... for a while the Debian package for MediaWiki was distinctly
idiosyncratic (even by Debian standards), enough so that people were
recommended not to use it at all and just use the tarball.
For 1.19 it was less variant from upstream and well-maintained enough
to steer people to, but then
Hei folks,
looking at https://wiki.debian.org/MediaWiki the mediawiki-package for
Debian seems to be in not-so-good shape.
Debian is shipping 1.19 - Upstream Security support has ended, Debian
security seems to end soon.
We're running mediawiki on Debian for a small community project and I'm
Additional debugging tips (thanks Nikerabbit):
1) There is specific debug log for translation services:
$wgDebugLogGroups['translationservices'] = 'file',
2) Use the browser's developer console to inspect the AJAX requests to
see if it contains explicit
Hi Andrew, sorry for seeing your question only now.
What Apertium configuration are you using exactly? Can you detect any
pattern in the units which don't show the translation suggestion? For
instance, are they longer, or do they contain a lot of non-alphanumeric
text? If it seems completely
