Ticket #456 (closed defect: fixed)

Opened 2 years ago

Last modified 3 months ago

Problem with Thai word segmentation in HTML!

Reported by: mbuntan Owned by:
Priority: major Milestone: 2011.2
Component: Browse mode Version:
Keywords: Cc:
Operating system: Windows XP Blocked by:
Blocking:

Description

It appears that later versions of NVDA has shown worng word segmentation in Thai when viewing html files. Such problem does not occur when working with MSWord or WordPad?. I'm wondering what changes have been made to such feature which causes the problem.

Change History

comment:1 Changed 2 years ago by jteh

  • Milestone changed from 2009.1 to 2009.2

Please provide more specific information.
What is the problem you are seeing? Please provide an example and steps to reproduce.
If you believe this is a regression, what was the last version of NVDA where the issue didn't exist?

comment:2 Changed 2 years ago by mdcurran

Could we please have an example HTML file or URL?
It may be related to the change where we now do not allow a word in virtualBuffers to span over multiple nodes. Though why this would be annoying to Thai specifically I am not sure. Does the HTML have specific tags for Thai letters such as Ruby lettering or something?
Does this problem occure on all Thai websites?

comment:3 Changed 2 years ago by mdcurran

  • Component changed from Core to Virtual buffers
  • Milestone 2010.1 deleted

Moving out of 2010.1 for now as no examples from reporter. If useful examples ca be provided then we will again consider it for 2010.1 if it is serious enough.

comment:4 Changed 2 years ago by mdcurran

  • Type changed from task to defect

comment:5 Changed 7 months ago by mdcurran

Hopefully fixed by changeset:main,4493. I would be greatful if someone who can read Thai can verify that this is in deed fixed and then close the ticket. Thanks.

comment:6 Changed 3 months ago by mdcurran

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone set to 2011.2

Due to no answer from reporter I guess this has been fixed. Please reopen if not.

Note: See TracTickets for help on using tickets.