[MDEV-7304] [PATCH] build failure in cp932 Windows environment caused by ISO-8859 incompatibility Created: 2014-12-11 Updated: 2014-12-15 Resolved: 2014-12-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Connect |
| Affects Version/s: | 10.0.15 |
| Fix Version/s: | 10.0.16 |
| Type: | Bug | Priority: | Major |
| Reporter: | hiroshi HATAKE | Assignee: | Olivier Bertrand |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | connect-engine | ||
| Environment: |
Visual Studio 2013 |
||
| Attachments: |
|
| Description |
|
ISO-8859 encoding does not have encoding compatibilty against cp932(Windows-31J) which is mainly used in Japanese edition of Windows. ~~~ c:\jw\workspace\dmbvc2013\powershell\work\source\storage\connect\frids.h(26): error C2143: 構文エラー : ';' が 'case' の前にありません。 [C:\jw\workspace\dmbvc2013\powershell\work\build-vc2013-zip-32\storage\connect\connect.vcxproj] c:\jw\workspace\dmbvc2013\powershell\work\source\storage\connect\frids.h(26): error C2001: 定数が 2 行目に続いています。 [C:\jw\workspace\dmbvc2013\powershell\work\build-vc2013-zip-32\storage\connect\connect.vcxproj] c:\jw\workspace\dmbvc2013\powershell\work\source\storage\connect\frids.h(27): error C2143: 構文エラー : ';' が 'case' の前にありません。 [C:\jw\workspace\dmbvc2013\powershell\work\build-vc2013-zip-32\storage\connect\connect.vcxproj] ISO-8859's `é";' string does not correctly interpret in cp932 env by MSVC. Attached "friids.h" is saved with UTF-8 encoding and build log in cp932 environment. |
| Comments |
| Comment by Olivier Bertrand [ 2014-12-12 ] |
|
Curious bug indeed because only lines 25, 26, 27 raise an error while many other lines contain the same not understood characters (1, 3, 7, 12, 14, 20, 41, 44) I am not sure I understood what you said by At least, this curious bug can prevent when "frids.h" is saved by UTF-8 encoding. Did you mean that saving this file in UTF-8 fixes the bug? If so, thanks for telling me how to fix this bug. Note that the file frcas.h should also be UTF-8 encoded although it is not included in your particular build. If not, if you work on a source distribution, just remove or comment out lines 35 to 42 into rcmsg.c. As a matter of fact, all this business is to prepare for future versions that should provide the ability to choose the language used for messages. However, as this bug shows, this is not yet operational and documented. |
| Comment by hiroshi HATAKE [ 2014-12-12 ] |
|
> Did you mean that saving this file in UTF-8 fixes the bug? Yes, I mean saving this file with UTF-8 to fix bug. > If so, thanks for telling me how to fix this bug. It's my pleasure. You might already know that gcc cannot read source saved by UTF-8 with BOM. > If not, if you work on a source distribution, just remove or comment out lines 35 to 42 into rcmsg.c. Sorry, I can't do this strategy. |
| Comment by Olivier Bertrand [ 2014-12-15 ] |
|
Fixed by just commenting out the loading of French message files until this feature is fully implemented. |