Opened 6 years ago

Closed 6 years ago

#1800 closed enhancement (fixed)

OpenOffice.org plug-in does not work with Chinese code page

Reported by: simon Owned by: simon
Priority: major Milestone: 2.1 Final
Component: word integration Version: 2.1
Keywords: Cc:

Description

http://forums.zotero.org/discussion/16556/openoffice-could-not-communicate-with-zotero-error-begging-help/#Comment_83728

Yuck.

The state of OOo Basic's "Declare Function" capability is really a mess in OOo 3.3+, and my fix breaks it on non-Roman code pages. It seems like we have a few options:

  • Try really hard to get this to work in OOo Basic. I've tried to do this for an hour or so, but I'm not really too optimistic it's worth investing more time.
  • Write an UNO component in C++ for Windows users.
  • Write a Python component for Windows users, and bundle Win32API.
  • Use the shell. I'm not sure if we can pull the Firefox window to the front if we do this.
  • Decline to support non-Roman code pages.
  • Convince both the OOo and LibreOffice devs to fix their software.

Why does OpenOffice.org have to misbehave so badly?

Change History (1)

comment:1 Changed 6 years ago by simon

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

(In [8418]) Next-generation OpenOffice.org plug-in

closes #1767, Better error handling in OOo plug-in
closes #1800, OpenOffice.org plug-in does not work with Chinese code page
closes #1801, Reconsider how to communicate with OpenOffice.org Integration java component

Note: See TracTickets for help on using tickets.