https://bz.apache.org/ooo/show_bug.cgi?id=126405

          Issue ID: 126405
        Issue Type: DEFECT
           Summary: Insert->Indexes & Tables Cannot Handle Short Form
                    Legal Citation
           Product: Writer
           Version: 4.1.0
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: P5
         Component: programming
          Assignee: issues@openoffice.apache.org
          Reporter: drankina...@suddenlinkmail.com

Writer Insert->Indexes & Tables cannot handle short-form legal citations
resulting in unwanted duplicate entries in the Table of Authorities. Legal
citations for cases reported in the regional reporters have the general
full-form citation of e.g.:

Retamco Operating, Inc. v. Republic Drilling Co., 278 S.W.3d 333, 337 (Tex.
2009)

where the parties are:
  Retamco Operating, Inc. v. Republic Drilling Co.

the reporter volume is:

  278 S.W.3d
  (volume 278 of the SouthWest 3rd Reporter)

followed by:

  333, 337
  (case begins on page 333 with a specific reference for the issue at hand
being page 337. The specific page being called a 'jump-cite' within the
citation. The origin being something along the lines of "you find the volume
and beginning page and then 'jump' to the specific page of interest).

lastly, the court information

  (Tex. 2009) indicating Texas Supreme Court in year 2009

After the case has been cited with its full-form citation, appellate courts
require a 'short-form' citation for all subsequent citations to a given case.
The short form citations for the Retamco case would be:

Retamco, 278 S.W.3d at 337.
(where the beginning page is substituted with 'at' and the court information is
dropped.

or if cited within the same paragraph, but separated from the first by an
intervening citation, the short form would be:

Retamco at 337.

or if following immediately, simply

Id. 

or if citing a different page

Id at 341.

The point being that the following are all the SAME citation and should be
handled be Index & Tables Entry and placed on the SAME line in the Table of
Authorities:

Retamco Operating, Inc. v. Republic Drilling Co., 278 S.W.3d 333, 337 (Tex.
2009).
Retamco, 278 S.W.3d at 337.
Retamco at 337.
Id at 341.
Id.

Following the directions at:

https://wiki.openoffice.org/wiki/Documentation/How_Tos/Writing_Legal_Briefs

it became painfully apparent that OpenOffice just cannot handle short-form
citation in any reasonable manner. (I would even delete the suggested entry and
paste the full-form citation, but any change in the 

How should it be handled?

Blasphemy, but Word handles it perfectly by having the entry dialog search
through the existing entries for strcmp matches of the case name (e.g. Retamco)
and automatically suggesting that the new entry is a 'short-form' of the full
citation. Word also provides a 'short-form' radio button that the user can
select if 'Id' is the citation so the user can then choose the correct
full-citation for the 'Id' cite (there being no way that any search of existing
entries would be meaningful for 'Id')

This manner of handling short form citation is very good and trivial to
implement.

Another, more robust manner Word allow handling short-form citation (and
building indexes in general) is to allow the use of field-codes (basically
non-printing tags) by the user to pre-designate entries for the various
separate indexes required in the Table of Authorities (i.e. CASES, STATUTES,
OTHER AUTHORITIES, and APPENDIX) Something similar in AOO would also be a
workable solution.

Give it some thought. Word has had the ability to handle short-form citation
since sometime around Word 1.0f in the early 90's. It is a critical feature in
word processing (not only for attorney's, but anyone handling citations).
Word-Perfect handled short-form in a similar manner.

This would be a great feature to implement to help bring AOO up to par with
other mature word-processors. Let me know if you need more information.

-- 
You are receiving this mail because:
You are the assignee for the issue.

Reply via email to