fbennett

About

Username
fbennett
Joined
Roles
Member

Comments

  • That does not work well in MS Word: I got exclamation marks (except for "o", "s" and "n" - but "n" is a normal "n", maybe because there is no "modified letter small n") (+ issues with typefaces);That's pretty much a show-stopper. Looks like we need …
  • The name output is the expected result. The correct way to address this is by providing language-specific formatting of citations. This is still experimental, but details of the technique (which can be used with Zotero 2.1 and citeproc-js) will be p…
  • The latest CSL processor version, at least, gives the correct result. I haven't tested with Zotero 2.1.6; if you can wait until the next Zotero 2.1 release, you may find that the problem corrects itself. On Chinese names, have you tried putting the…
  • @ajlyon, Common Japanese characters that might be used are covered in the list linked in my post above, but the unicode approach does have the problem of inflexiblity; it wouldn't be reasonable to put users to the task of securing an extension of t…
  • With some scratching around I've stumbled across a nice list of superscripted equivalents, which may cover many use cases.
  • Lowercase will force everything to lowercase, always. Sentence case currently forces everything to lowercase except for the first letter. Probably it should preserve uppercase for all-uppercase words in a mixed-case string. We'll look into this.
  • Thanks. Just a holding response for the moment; I'm letting myself be tied up with work on a small tool that I think will be useful in my own research workflow. If the final work on the style is urgent, just say the word; otherwise I'll probably get…
  • Affixes on the name-part should work with the citeproc-js processor, but I think that it's not allowed by the CSL specification, so a style that puts affixes there won't validate.
  • Yes, there is a Language field in Zotero, but it's not mapped to CSL currently. Both the variable mapping and support for language-specific styles will be addressed in the future.
  • Jinsong, The multilingual version of Zotero is capable of this. However, it is an experimental version, and the Zotero project does not provide support for it (meaning that if you had any problems with the experimental client, or with sync from the…
  • If this is the case, it would explain a batch of empty attachment files that we recently purged from one of our groups here: http://forums.zotero.org/discussion/17990/empty-files-in-download/ The user concerned had exceeded the 100mb quota on th…
  • The string is from the main text of the document itself? If so, that's very odd indeed ... would it be correct to assume that a parse error in the processor itself would not be the cause of that?
  • @sbuchoux: Well done. Have tried this out in the multilingual branch, and with a couple of fixes for the same issue (?) in other locations, proxy redirection and captures via proxy seem to be working well there under Linux.
  • That title renders fine in the Chicago styles in the English and the French locales ... is the problem limited to a particular style? Or perhaps other elements of the citation or other cites within the citation contribute to the error? If you can co…
  • After patching the multilingual branch to wake up proxy redirection in Linux, I'm getting this consistently, when Zotero is set to default of tab mode, FF is restarted in that state, I do a library lookup, log into the proxy, click through to the it…
  • @dgolds, @katsalmi, Good to know that you've been able to get past the error and back to work. In order to prevent this error in the future, I'll need to be able to reproduce it locally. The document itself actually won't help; what I need is the …
  • Of course; sorry for the confusion, and sorry for the extra trouble, Dan. dgolds: If you can export the citation that causes the error, paste to gist.github.com, save it as a public gist, and post the URL from the address bar back here, I'll take a…
  • I don't have access to the Debug ID queue; if Dan comes by he may be able to take a look at your ID and fetch out the relevant snippet. There should be some debugging trace info in the log that will provide a clue, at least.
  • Hmm. That's not good. If you can narrow down the error to a particular reference that causes it, it would be helpful to have an exported copy of that reference in Zotero RDF format. This error is most likely triggered by mismatched or oddly placed …
  • Your best bet is to wait for the next release, which may resolve this.
  • Okay, that makes sense. To be sure I understand this correctly, the database has registered the existence of an attachment in the SQL, but file storage has not synced the file data itself, from whatever machine created the attachment. Would that be …
  • Yay, that's good news. If you select "Save to Clipboard", the content of the export will be stored on the computer's clipboard, which is where "cut", "copy" stash things, and where "paste" retrieves them from. So for an export, you could "Save to Cl…
  • If it seems like a lot of trouble, you might just wait for the next release of Zotero, and see if that solves the problem.
  • There is an icon in the top bar of Zotero that looks like a gear cog. If you click on it, that's the gear menu. The aim in asking you to post an export of sample data is to save time. A picture is worth a thousand words, as they say.
  • Can you export the items used in your bibliography (a small set, if possible, that illustrates the problem) as Zotero RDF (gear menu -> Export), and paste the code to gist.github.com as a public gist? I'd like to try to reproduce the problem here.
  • Ah, sorry. I misread. The problem is with the sort order of items in the bibliography, yes?
  • Are you quite certain that you have Zotero 2.1.6 installed?
  • Thanks for the quick feedback. I'll take a look through the issues in the next few days. In the USGS example, I put the string with the filing numbers ("USGS Open-File Report 2007–1047, Short Research Paper 102") into a CSL number field, spliced in…
  • Here's the first draft of the style: https://gist.github.com/973212 I shifted around some of the field content. Here is the RDF of the data used for testing: https://gist.github.com/973218 In the data, you may notice that I used a funny syntax i…
  • This was caused by a bug in the CSL processor that generates citations. It was fixed some time ago, so the fact you are experiencing it suggests that you are running an old version of the processor. I haven't checked all of the bundles, but the sta…