Bug 14878 – gap.awk makes bad conversion tables if u+0001.. u+0006 not mapped

Bug 14878 - gap.awk makes bad conversion tables if u+0001.. u+0006 not mapped


Summary:	gap.awk makes bad conversion tables if u+0001.. u+0006 not mapped

Status:	NEW

Product:	glibc
Classification:	Unclassified
Component:	localedata
Version:	2.17

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Not yet assigned to anyone

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-11-26 13:56 UTC by John Hughes
Modified:	2012-11-26 13:57 UTC (History)
CC List:	1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
charmap that shows the bug (1.32 KB, application/octet-stream) 2012-11-26 13:56 UTC, John Hughes	Details
patch to gap.awk and gaptab.awk to fix bug (1.03 KB, patch) 2012-11-26 13:57 UTC, John Hughes	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description John Hughes 2012-11-26 13:56:55 UTC

Created attachment 6753 [details]
charmap that shows the bug

If a charmap doesn't define a mapping for at least one character in the range
u+0001 to u+0006 then the translation table generated by gap.awk is broken. 
For example with the attached TEST charmap then u+0041 gets mapped to a \4a
instead of \x41.

The bug happens because gap.awk sets "last" (the last codepoint output) to
zero, instead of -1.  A patch to gap.awk and gaptab.awk is attached.

Comment 1 John Hughes 2012-11-26 13:57:48 UTC

Created attachment 6754 [details]
patch to gap.awk and gaptab.awk to fix bug