Opened 15 years ago
Closed 14 years ago
#1576 closed Bugs (fixed)
cannot read non-ASCII output messages
| Reported by: | Owned by: | René Rivera | |
|---|---|---|---|
| Milestone: | Boost.Jam 3.1.17 | Component: | bjam |
| Version: | Boost Development Trunk | Severity: | Problem |
| Keywords: | Cc: |
Description
The changes in exent.c at changeset:38009 break non-ASCII output messages. Some Japanese compilers output diagnostic messages in Japanese (non-ASCII), but we cannot read them. This problem is caused by the following codes:
/* clean up non-ascii chars */
int i;
for ( i = 0; i < bytesInBuffer; ++i )
{
if ((unsigned char)ioBuffer[i] < 1 ||
(unsigned char)ioBuffer[i] > 127 )
{
ioBuffer[i] = '?';
}
}
Could you remove it?
Change History (2)
comment:1 by , 14 years ago
| Milestone: | Boost 1.36.0 → Boost.Jam 3.1.17 |
|---|
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.

(In [49882]) On Windows don't limit bjam output to ASCII as some tools output characters in extended character sets. (fixes #1576)