https://bz.apache.org/ooo/show_bug.cgi?id=126405
--- Comment #4 from David Rankin <[email protected]> --- Also, to make sure I'm clear, when I say all forms of a citation are the SAME citation and should be placed on the SAME line, I mean the page numbers for all Marked Entries for that citation should should appear on the same line of the Index following the LONG FORM of the original citation. e.g.: Retamco Operating, Inc. v. Republic Drilling Co., 278 S.W.3d 333, 337 (Tex. 2009)..........................................i,iii,7,8,10,23,42,42. Each page number should only appear once in the collection of page numbers and there should be no 'p' indicating an entry appears more than once on a given page. Appellate courts require 13pt. proportional fonts of 10 pt. fixed font. If the party names are long, the citation may wrap on the first line. If this occurs, the leader (row of '...' between the end of the case cite and the beginning of the page numbers) should extend from the end of the citation on the second line to the beginning of the page numbers (just like what would occur if the citation had fit on a single line) Some court's local rules require different leaders to be used (period '.', '_', '-', 'em-dash', etc...)(i.e. period, underscore, hyphen, em-dash, etc...). So the leader character must be easily selectable by the user. Above all, even knowing how perfect the coding logic will be, the indexes should be able to be MANUALLY EDITED after they are generated (to add or fix) an index or cite before final printing or submission. This shouldn't require any special logic, rather you just must insure that there is some checkbox, etc... that allow the user to remove whatever protection prevents an entry from being edited after the index is generated. I don't know how the Writer code collects the entries for each citation (i.e. whether it is an array of structs with each cite having a unique index number, or list or tree of stacks for each citation, etc..., but it is a big time saver if the user can review/fix what entries Writer thinks are associated with each citation. (this can be as simple as allowing the user to scroll though the Entry dialog and click on any given entry and see what Full-Form citation it is associated with any given entry.)(This is also where the use of 'field-codes' allowing the user to pre-mark the entries for each index really shines) Thanks again for your help. -- You are receiving this mail because: You are the assignee for the issue.
