Edgewall Software

Changes between Version 5 and Version 6 of TracDev/ReleaseNotes/0.10


Ignore:
Timestamp:
Jul 7, 2006, 11:25:01 PM (18 years ago)
Author:
ErikRose
Comment:

Spelling, grammar, flow

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/ReleaseNotes/0.10

    v5 v6  
    5757
    5858  ''We should probably package that plugin separately,
    59   but put it right besides the Trac packages, on the TracDownload page.''
     59  but put it right beside the Trac packages, on the TracDownload page.''
    6060
    6161== Wiki syntax improvements ==
    6262
    63 Numerous improvements have been made on the WikiFormatting syntax.
    64  * Headings can optionally be given explicit ''id''
    65  * MoinMoin `["internal free link"]` syntax is now supported
    66  * Introduced citation syntax for the Wiki (e-mail style)
    67  * More robust parsing and formatting of Wiki lists and robust coupling of lists and quotes
    68  * Improve the way external links are displayed.
     63Numerous improvements have been made in the WikiFormatting syntax:
     64 * Headings can optionally be given explicit ''id''.
     65 * MoinMoin `["internal free link"]` syntax is now supported.
     66 * Introduced citation syntax for the Wiki (e-mail style).
     67 * Added more robust parsing and formatting of Wiki lists and robust coupling of lists and quotes.
     68 * Improved the way external links are displayed.
    6969 * Lots of new ways to refer to specific repository views (`diff:from//to`, log:, `[x:y]`, `rx:y`)
    7070 * `htdocs:`, useful for refering to local resources in TracStandalone
     
    7272 * Removed support for direct embedding of images using links: use the ![[Image]] macro instead.
    7373
    74 == Developer visible changes ==
     74== Developer-visible changes ==
    7575
    7676=== `unicode` everywhere ===
    7777
    7878Trac used to handle text content by using `str` objects,
    79 in which bytes where encoding Unicode characters using the UTF-8
     79in which Unicode characters were represented using UTF-8
    8080encoding. This lead to various problems with most non-western
    81 languages, and the decision was made to use the dedicated `unicode`
    82 datatype to be able to handle consistently text written in any
     81languages. We now use the dedicated `unicode`
     82datatype to consistently handle text written in any
    8383language.
    8484
    85 This removed all the problems we had when cutting UTF-8 encoded strings
    86 in the middle of a byte sequence for encoding one character.
     85This removes all the problems caused by mistakenly cutting a UTF-8-encoded string between the bytes of a multi-byte character.
    8786
    8887=== Better way to programatically generate of HTML fragments ===