Opened 7 years ago

Closed 7 years ago

#1489 closed defect (fixed)

Show a more intelligible error for corrupted fields

Reported by: dstillman Owned by: simon
Priority: minor Milestone:
Component: word integration Version: 2.0
Keywords: Cc:

Description

Uppercase fields cause parseJSON error

​http://forums.zotero.org/discussion/7216/

Change History (2)

comment:1 Changed 7 years ago by simon

  • Priority changed from major to minor
  • Summary changed from Case-insensitive field code handling to Show a more intelligible error for corrupted fields
  • Type changed from enhancement to defect

Following some discussion, we've decided that the loss of field code case following use of Cmd-Shift-A is a bug in Word that we won't try to fix. That Cmd-Shift-C leaves the field codes intact while Cmd-Shift-A incorrectly converts the field codes to uppercase is inconsistent behavior that needs to be fixed on Microsoft's end. Furthermore, since custom citation text and page numbers may contain case-sensitive data, the only resolution would be to encode all Zotero field codes with uuencode or Base32, which is an ugly hack we'd like to avoid. Still, it makes sense to fail a little more gracefully.

comment:2 Changed 7 years ago by simon

  • Resolution set to fixed
  • Status changed from new to closed

(In [5155]) Show an error when field JSON is corrupt and allow user to re-select.

closes #1489, Show a more intelligible error for corrupted fields

Note: See TracTickets for help on using tickets.