Changes between Version 5 and Version 6 of TracDev/ReleaseNotes/0.10
- Timestamp:
- Jul 7, 2006, 11:25:01 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/ReleaseNotes/0.10
v5 v6 57 57 58 58 ''We should probably package that plugin separately, 59 but put it right beside sthe Trac packages, on the TracDownload page.''59 but put it right beside the Trac packages, on the TracDownload page.'' 60 60 61 61 == Wiki syntax improvements == 62 62 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 quotes68 * Improve the way external links are displayed.63 Numerous 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. 69 69 * Lots of new ways to refer to specific repository views (`diff:from//to`, log:, `[x:y]`, `rx:y`) 70 70 * `htdocs:`, useful for refering to local resources in TracStandalone … … 72 72 * Removed support for direct embedding of images using links: use the ![[Image]] macro instead. 73 73 74 == Developer 74 == Developer-visible changes == 75 75 76 76 === `unicode` everywhere === 77 77 78 78 Trac used to handle text content by using `str` objects, 79 in which bytes where encoding Unicode characters using theUTF-879 in which Unicode characters were represented using UTF-8 80 80 encoding. This lead to various problems with most non-western 81 languages , and the decision was made touse the dedicated `unicode`82 datatype to be able to handle consistentlytext written in any81 languages. We now use the dedicated `unicode` 82 datatype to consistently handle text written in any 83 83 language. 84 84 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. 85 This removes all the problems caused by mistakenly cutting a UTF-8-encoded string between the bytes of a multi-byte character. 87 86 88 87 === Better way to programatically generate of HTML fragments ===