If localstore.rdf has the tag selector persisted closed from before
zotero-persist, the 'state' attribute on the splitter that we now use
won't cause the tag selector to open.
This would previously have thrown an error. I'm not sure what these
documents would be, but it's a safe bet that they're not loaded in a
normal browser window.
Also fix weirdness trying to open collapsed tag selector after restart.
(The splitter's 'state' attribute has to be persisted, not the
'collapsed' state of the pane in question.)
If Zotero Standalone was opened before Firefox, closed, and opened
again, the user would see a message stating Zotero Standalone was open,
but the pane would not have closed. This was purely cosmetic.
- When opening the DB, always tell other Zotero instances to close it,
regardless of whether they are holding the lock.
- Don't let database re-open after it has been closed. This also fixes
some issues with connector switching.
This should make it much easier to debug startup errors, particularly in
Standalone.
This also adds a general mechanism to set Zotero initialization options via
command-line flags.
- Refresh Unfiled Items view when items are added
- Fix brief freeze ("too much recursion") adding an item to a search
where the new item doesn't appear. Now, select the library root
instead if a manually added item doesn't appear in the current view.
- Fix immediate closing of title field when adding an item to a
collection rather than the library root
nsISemanticUnitScanner doesn't seem to be able to deal with single
quotes, so protect those. (There might be other characters it doesn't
handle, but this is ancient code, so it stays as is for now.)
(ignoring some strings that were reverted due to small changes in the
English versions, which hopefully will be redone on Transifex before the
next pull)
It might be possible to write non-UTF-8 data by passing another charset
to TextEncoder, but I haven't tried it.
Firefox 19+ only, and for now, at least, only if data is passed as
string rather than input stream
This isn't technically any slower than before, but if people were using
multiple computers, they might not have had their entire full-text index
on a single computer before full-text syncing.
