OS X Yosemite 10.10.5 XCode 7.2
我一直在阅读和试验整天,关于C中的宽字符/字符串,我仍然无法使其工作。
我正在尝试阅读仅由以下宽字符组成的文件:
んわらやま (Japanese)
我想一次只读一个字符,立即写在另一个文件中。
int main(int argc, const char * argv[])
{
FILE *source, *dest;
source = fopen( argv[1], "r");
if (source == NULL) {
printf ("could not open source file \n");
exit (1);
}
// if [dest] does not exist it is created
dest = fopen( argv[2], "w+");
if (dest == NULL) {
fclose(source);
printf ("could not open dest file \n");
exit (1);
}
fwide(source, 1);
fwide(dest, 1);
fileManipulator(source, dest);
fclose(source);
fclose(dest);
return 0;
}
void fileManipulator(FILE* source, FILE* dest)
{
wint_t token;
while ( WEOF != (token = getwc(source))) {
manipulateToken(token, dest);
}
}
void manipulateToken(wint_t token, FILE* dest)
{
char* pre = "- ";
char* post= " -\n";
if ( EOF == fputs(pre, dest))
{
// error handling
}
if ( WEOF == fputwc(token, dest))
{
// error handling
}
if ( EOF == fputs(post, dest))
{
// error handling
}
}
这是输出:
- „ -
- Ç -
- ì -
- „ -
- Ç -
- è -
- „ -
- Ç -
- â -
- „ -
- Ç -
- Ñ -
- „ -
- Å -
- æ -
我可以理解我的问题可能是关于我如何阅读数据,但如果我考虑替代方案,我就完全陷入了困境。
PS:关于该论点的进一步阅读的链接也非常受欢迎。有关此事的文件很少。
这个问题最初让我觉得 Jonathan Leffler 解决方案无效。事实上,如果我通过XCode CMD + R 或通过终端运行代码,代码会产生不同的输出。
AFAIK问题必须是XCode在运行时使用的某种属性/属性/设置,因为硬编码 源 和 dest < / em> 参数仍会产生错误的输出。
为了清楚起见,我为我的代码提供了导出的方案:
<?xml version="1.0" encoding="UTF-8"?>
<Scheme
LastUpgradeVersion = "0720"
version = "1.3">
<BuildAction
parallelizeBuildables = "YES"
buildImplicitDependencies = "YES">
<BuildActionEntries>
<BuildActionEntry
buildForTesting = "YES"
buildForRunning = "YES"
buildForProfiling = "YES"
buildForArchiving = "YES"
buildForAnalyzing = "YES">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "DA36663A1CCF4F8200615958"
BuildableName = "FileManipulator"
BlueprintName = "FileManipulator"
ReferencedContainer = "container:FileManipulator.xcodeproj">
</BuildableReference>
</BuildActionEntry>
</BuildActionEntries>
</BuildAction>
<TestAction
buildConfiguration = "Debug"
selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
shouldUseLaunchSchemeArgsEnv = "YES">
<Testables>
</Testables>
<MacroExpansion>
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "DA36663A1CCF4F8200615958"
BuildableName = "FileManipulator"
BlueprintName = "FileManipulator"
ReferencedContainer = "container:FileManipulator.xcodeproj">
</BuildableReference>
</MacroExpansion>
<AdditionalOptions>
</AdditionalOptions>
</TestAction>
<LaunchAction
buildConfiguration = "Debug"
selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
launchStyle = "0"
useCustomWorkingDirectory = "NO"
ignoresPersistentStateOnLaunch = "NO"
debugDocumentVersioning = "YES"
enableAddressSanitizer = "YES"
debugServiceExtension = "internal"
allowLocationSimulation = "YES">
<BuildableProductRunnable
runnableDebuggingMode = "0">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "DA36663A1CCF4F8200615958"
BuildableName = "FileManipulator"
BlueprintName = "FileManipulator"
ReferencedContainer = "container:FileManipulator.xcodeproj">
</BuildableReference>
</BuildableProductRunnable>
<CommandLineArguments>
<CommandLineArgument
argument = "/Users/Paul/TestDirectory/Source.txt"
isEnabled = "YES">
</CommandLineArgument>
<CommandLineArgument
argument = "/Users/Paul/TestDirectory/Destination.txt"
isEnabled = "YES">
</CommandLineArgument>
</CommandLineArguments>
<AdditionalOptions>
<AdditionalOption
key = "NSZombieEnabled"
value = "YES"
isEnabled = "YES">
</AdditionalOption>
<AdditionalOption
key = "NSDOLoggingEnabled"
value = "YES"
isEnabled = "YES">
</AdditionalOption>
</AdditionalOptions>
</LaunchAction>
<ProfileAction
buildConfiguration = "Release"
shouldUseLaunchSchemeArgsEnv = "YES"
savedToolIdentifier = ""
useCustomWorkingDirectory = "NO"
debugDocumentVersioning = "YES">
<BuildableProductRunnable
runnableDebuggingMode = "0">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "DA36663A1CCF4F8200615958"
BuildableName = "FileManipulator"
BlueprintName = "FileManipulator"
ReferencedContainer = "container:FileManipulator.xcodeproj">
</BuildableReference>
</BuildableProductRunnable>
</ProfileAction>
<AnalyzeAction
buildConfiguration = "Debug">
</AnalyzeAction>
<ArchiveAction
buildConfiguration = "Release"
revealArchiveInOrganizer = "YES">
</ArchiveAction>
</Scheme>
答案 0 :(得分:3)
此代码似乎有效。你可能不应该使用fputs()
和缩小字符串;您应该使用fputws()
和宽字符串:L"- "
。注意使用setlocale()
;这是至关重要的(尝试省略它,看看你得到了什么)。
#include <locale.h>
#include <stdio.h>
#include <stdlib.h>
#include <wchar.h>
static void fileManipulator(FILE *source, FILE *dest);
static void manipulateToken(wint_t token, FILE *dest);
int main(int argc, const char *argv[])
{
FILE *source, *dest;
if (argc != 3)
{
fprintf(stderr, "Usage: %s input output\n", argv[0]);
exit(1);
}
setlocale(LC_ALL, "");
source = fopen(argv[1], "r");
if (source == NULL)
{
fprintf(stderr, "could not open source file %s\n", argv[1]);
exit(1);
}
dest = fopen(argv[2], "w+");
if (dest == NULL)
{
fclose(source);
fprintf(stderr, "could not open dest file %s\n", argv[2]);
exit(1);
}
fwide(source, 1);
fwide(dest, 1);
fileManipulator(source, dest);
fclose(source);
fclose(dest);
return 0;
}
static void fileManipulator(FILE *source, FILE *dest)
{
wint_t token;
while (WEOF != (token = getwc(source)))
{
manipulateToken(token, dest);
}
}
static void manipulateToken(wint_t token, FILE *dest)
{
wchar_t *pre = L"- ";
wchar_t *post = L" -\n";
if (EOF == fputws(pre, dest))
{
fprintf(stderr, "Failed to write prefix string\n");
exit(1);
}
if (WEOF == fputwc(token, dest))
{
fprintf(stderr, "Failed to write wide character %d\n", (int)token);
exit(1);
}
if (EOF == fputws(post, dest))
{
fprintf(stderr, "Failed to write suffix string\n");
exit(1);
}
}
给定一个文件data
,其中包含:
$ cat data
んわらやま
$ odx data
0x0000: E3 82 93 E3 82 8F E3 82 89 E3 82 84 E3 81 BE 0A ................
0x0010:
$
(你没有odx
,因为我写了它,但xxd -g 1 data
产生或多或少的等效输出。)我运行程序(称为x37
),如下所示:
$ x37 data output
$ cat output
- ん -
- わ -
- ら -
- や -
- ま -
-
-
$ odx output
0x0000: 2D 20 E3 82 93 20 2D 0A 2D 20 E3 82 8F 20 2D 0A - ... -.- ... -.
0x0010: 2D 20 E3 82 89 20 2D 0A 2D 20 E3 82 84 20 2D 0A - ... -.- ... -.
0x0020: 2D 20 E3 81 BE 20 2D 0A 2D 20 0A 20 2D 0A - ... -.- . -.
0x002E:
$
使用GCC(5.3.0,自制)和Clang(Apple LLVM版本7.3.0(clang-703.0.29))在Mac OS X 10.11.4上进行测试。
根据工作代码,您可以尝试查找哪些更改至关重要。我还创建了使用单行调用报告错误的函数,而不是每个错误需要写3行或4行。 (实际上&#39;使用&#39;比创建&#39;更合适 - 我很久以前创建了这样一组函数,并且不断使用它们。)