Swathanthra Malayalam Computing - Tasks: task #12560, Automate Rendering Testing
You are not allowed to post comments on this tracker with your current authentication level.
task #12560: Automate Rendering Testing
Submitter: | Hrishikesh K B <hrishikesh_kb> | ||
Submitted: | Tue 02 Apr 2013 09:14:39 PM UTC | ||
Category: | rendering | Should Start On: | Tue 02 Apr 2013 12:00:00 AM UTC |
Should be Finished on: | Tue 31 Dec 2013 12:00:00 AM UTC | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | None | Percent Complete: | 0% |
Open/Closed: | Open | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-f8d8.
Corresponding source code
Automated Rendering Testing system for Indic languages. Currently there exists 3 main rendering engines in computing world - Uniscribe of Microsoft, CoreText (Apple Advance Typography - AAT) of Apple and Harfbuzz for *nix systems. The Opentype font specification is maintained by Microsoft and implemented in Uniscribe, which is used as baseline for Harfbuzz. At present, there is no automated mechanism to determine if Harfbuzz is rendering complex Indic text correctly or not - someone expert in relevant language has to manually inspect the output from hb-view. The project aim is to identify and implement an automated method to test the rendering. One method to do this might be to check the order of glyphs/glyph indices output by the rendering engine - this depends on the font too. A related topic is UTRRS