This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | I18N - YAML editor could not handle file that contains Unicode characters. | ||
---|---|---|---|
Product: | ruby | Reporter: | tkrd_oiax <tkrd_oiax> |
Component: | Editing | Assignee: | Torbjorn Norbye <tor> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | kfrank |
Priority: | P3 | Keywords: | I18N |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | A YAML file that causes a ScannerException. |
Description
tkrd_oiax
2008-08-13 11:52:00 UTC
Created attachment 67244 [details]
A YAML file that causes a ScannerException.
This works fine for me - but that might be because I just yesterday updated the YAML parser to the latest version (changeset ae6cda6f80c9). I added a unit test for your file (changeset 85634280a792). Can you try a new build and verify that it works for you now? If not I'll have to dig deeper to find out why the file fails for you and not for me (and if so, attach the ScannerException too.) The latest builds are available here: http://deadlock.netbeans.org/hudson/job/trunk/ Wait about two hours from now if you want to pick up the other fix I just checked in for issue 143746. I spoke too soon - this problem is still there. I will forward this issue to Ola (who wrote the YAML parser). can filer tell which locale or reg setting they are running netbeans in and what the project encoding property is ? ken.frank@sun.com Fixed in changeset 7e38a615eb26 I discovered with a larger testcase (e.g. with text -after- the multibyte character(s)) that all of the YAML parser offsets are byte offsets, not the unicode/document offsets we need! Thus the highlights etc. were all off. I've fixed that now with integration a44448648373. Congratulations! to issue filer - does your last comment mean it can be verified as fixed ? ken.frank@sun.com to kfrank: Yeah, I think it has been fixed. I'm sorry for my ambiguous comment. v |