Changes between Initial Version and Version 3 of Ticket #832


Ignore:
Timestamp:
11/28/07 18:01:37 (9 years ago)
Author:
simon
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #832

    • Property Status changed from new to assigned
    • Property Component changed from uncategorized to export
    • Property Summary changed from enforce-case formatting is supported. to Handle title case/sentence case properly
    • Property Priority changed from minor to major
    • Property Milestone changed from to 1.5 Alpha 1
    • Property Owner changed from dstillman to simon

  • Ticket #832 – Description

    initial v3  
    1 The title/sentence directive doesn't seem to be supported. 
    2 e.g. enforce-case { "title" | "sentence" }?, 
     1Some styles require title case ("Article Title Here"), while others require sentence case ("Article title here"). At the moment, a transform to title case is implemented (although it's not customizable). Unfortunately, sentence case is a much harder situation. Transforming titles like "Glycogen: a Trojan horse for neurons" and "Characterization of the SKN7 ortholog of Aspergillus fumigatus" from their title case equivalents will not be possible by algorithms alone. 
    32 
     3Suppose we provide an icon to toggle between title/sentence case in the edit pane. Then, if the user modifies something beyond the capitalization in either form, we determine the minimum number of deletes and inserts to transform it (classic dynamic programming problem), and if this includes insertion of a new word, we capitalize it/put it in lower case as appropriate. This will require some modifications to the database schema, but is, as far as I can tell, the most intuitive all-encompassing solution.