riscv
/
musl
mirror of https://git.musl-libc.org/git/musl
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3353 Commits
2 Branches
78 Tags
7.6 MiB
Tree: a0bb50a142
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a0bb50a142'
${ noResults }
musl/src/network/hstrerror.c

19 lines
361 B
Raw Normal View History

initial check-in, version 0.5.0
15 years ago
#define _GNU_SOURCE
#include <netdb.h>
add support for LC_TIME and LC_MESSAGES translations for LC_MESSAGES, translation of strerror and similar literal message functions is supported. for messages in other places (particularly the dynamic linker) that use format strings, translation is not yet supported. in order to make it possible and safe, such messages will need to be refactored to separate the textual content from the format. for LC_TIME, the day and month names and strftime-style format strings provided by nl_langinfo are supported for translation. however there may be limitations, as some of the original C-locale nl_langinfo strings are non-unique and thus perhaps non-suitable as keys. overall, the locale support activated by this commit should not be seen as complete and polished but as a basis for beginning to test locale functionality and implement locales.
12 years ago
#include "locale_impl.h"
initial check-in, version 0.5.0
15 years ago
static const char msgs[] =
"Host not found\0"
"Try again\0"
"Non-recoverable error\0"
"Address not available\0"
"\0Unknown error";
const char *hstrerror(int ecode)
{
const char *s;
for (s=msgs, ecode--; ecode && *s; ecode--, s++) for (; *s; s++);
add support for LC_TIME and LC_MESSAGES translations for LC_MESSAGES, translation of strerror and similar literal message functions is supported. for messages in other places (particularly the dynamic linker) that use format strings, translation is not yet supported. in order to make it possible and safe, such messages will need to be refactored to separate the textual content from the format. for LC_TIME, the day and month names and strftime-style format strings provided by nl_langinfo are supported for translation. however there may be limitations, as some of the original C-locale nl_langinfo strings are non-unique and thus perhaps non-suitable as keys. overall, the locale support activated by this commit should not be seen as complete and polished but as a basis for beginning to test locale functionality and implement locales.
12 years ago
if (!*s) s++;
return LCTRANS_CUR(s);
initial check-in, version 0.5.0
15 years ago
}