Mar 5 2019
I am sorry to say that the issue has come up again on Geman Wikipedia, so I have reopened the task for re-evaluation. @Cirdan has made a good point in describing the issue and the solution for dewiki above. In the meanwhile @Crazy1880 pointed out to an entry in OCLC that of course does contain the OCLC number, but not an ISBN. In German-speaking countries we rarely refer to OCLC ids. Also, we rarely use WorldCat, we prefer the catalogues maintained by our national libraries that issue ISBN and ISSN for German-language publications. So, I subscribe to Cirdan's description and I would be grateful if you please could change configuration accordingly.
Feb 19 2019
Just to make sure: This worked before, and it only happens in JSTOR, no other resource is affected. I did not change anything about the local configuration.
Feb 18 2019
Jun 5 2018
May 17 2018
Am 18.05.18 um 00:05 Uhr schrieb Denny:
Copyright has to be about some concrete expression.
May 14 2018
Am 14.05.18 um 22:36 Uhr schrieb Nemo_bis:
But law is a matter of quality rather than size.
But quantitative indicators can be a proxy for quality. A dataset with
just 200 statements has most likely been produced by dozens or hundreds
of entities none of which can claim any meaningful exclusive right.
Am 14.05.18 um 17:23 Uhr schrieb Nemo_bis:
But I'd argue that nobody would see such a dataset as problematic,
especially because it's so small (few hundreds data points).
Am 14.05.18 um 11:37 Uhr schrieb TomT0m:
The more I personnaly dig into this questions, the more issues are
opened and the less clear it becomes that there is an actual issue, and
if there is an actual issue if there is a legal risk. Or even if there
is a moral or ethical issue: I think we will all agree here that pure
facts can be used by anyone (beyond private life one).
May 13 2018
Am 13.05.18 um 13:43 Uhr schrieb Simon_Villeneuve:
May 11 2018
Please note that there is not one copyright law. There are as many copyright laws as there are legal systems Wikipedia and Wikidata content can be retrieved from.
May 9 2018
Apr 11 2018
@Esanders I have restarted Firefox on El Capitan with a fresh profile, and I have switched off auto hypenation on Meta Wiki. No changes, I'm afraid. :( Strange that it seems to work for you... Again, thanks for looking into this!
Apr 4 2018
Thanks for testing, @TBolliger ! Meanwhile I have upgraded to Firefox 59.0.2, still on El Capitan, and it still looks as bad as it was before on my machine:
Mar 28 2018
Yes, I run FF ESR 52.7.3 on El Capitan, and given that the release is already there tonight (is it?), I'm sorry to say that nothing has changed. :(
Mar 20 2018
Here is an example of what it looks like with me.
I'm afraid it is even worse than it was before. Text now looks blurred etc. even immediately after switching on syntax highlighting on my system (same as above, now FF 52.7.2 ESR). When we started out the effect appeared only when you began to enter some text in the editor...
Feb 9 2018
Because of the recent renaming of this task by @TBolliger I'd like to point out once again that this is not only an issue concerning Chinese text, but also latin scripts and fonts.
Jan 14 2018
I second the suggestion to introduce a switch for the template an author deems fit for a citation.
Jan 13 2018
I can confirm the issue with Firefox ESR 52.5.3 under El Capitan on German Wikipedia, i.e. no Chinese fonts, but monospace, viz. Courier. It first showed up right after T175223 was implemented. I am sorry that I didn't have the time since then to open another task. As was mentioned before, I have also found it helpful to toggle syntax highlighting, or to undo an edit in order to get rid of the blurry fonts. Also, it seems to make a difference whether you start typing underneath some text, e.g. on a talk page (more apt to show the fault), or whether you start editing in the middle of a text.
Jan 5 2018
I forgot I also have to change the status of this task in order to have it reviewed again.
Jan 4 2018
Shortly before I pass into the weekend I would like to thank you for applying the fix I requested.
Dec 15 2017
Dec 7 2017
Dec 2 2017
The more I work with VE and the new wikitext editor the more I get used to tools like citoid. For the time being, I switch from VE for creating a citation to wikitext for removing the ref tags in the Further Reading section.
I think the suggestion by @ManosHacker would be a good idea to start with.
I suggest to raise the priority of the task because it is really important to expert authors, as @Sadads has already pointed out.
I have opened a discussion on German Wikipedia.
Mar 22 2015
This is just to let you know that I can confirm that—for the time being, at least—I have been able to use OTRS with IPv6 disabled in Firefox, or in OS X Mavericks, for that matter.
Mar 12 2015
Today, I have got the advice to set network.dns.disableIPv6 in Firefox about:config to "true".
Feb 23 2015
Please note that the case of dual IPv4/IPv6 addresses is indeed one main problem we reproduced some weeks ago in issue T88224 which was soon closed and marked as a duplicate to this ticket. Such broadband connections are provided per default in this country.
Feb 17 2015
Please note that we have tried this out in
Feb 13 2015
I just would like to say that some of us have not been able to work in OTRS at all, including myself. I keep being logged out after some minutes, on some occasions after a few clicks, while the scenarios you are discussing are rather hypothetical, if I may say so.