Does Bash imitate Locale-Specific Translation from C?
up vote
3
down vote
favorite
Bash manual mentions that
3.1.2.5 Locale-Specific Translation
A double-quoted string preceded by a dollar sign (‘$’) will cause the
string to be translated according to the current locale. If the
current locale is C or POSIX, the dollar sign is ignored. If the
string is translated and replaced, the replacement is double-quoted.
Does this way of specifying a string literal exist in C language or some C library?
Does bash imitate this way from C?
bash string c
asked Nov 19 at 23:09
Ben
2769
add a comment |
up vote
3
down vote
favorite
Bash manual mentions that
3.1.2.5 Locale-Specific Translation
A double-quoted string preceded by a dollar sign (‘$’) will cause the
string to be translated according to the current locale. If the
current locale is C or POSIX, the dollar sign is ignored. If the
string is translated and replaced, the replacement is double-quoted.
Does this way of specifying a string literal exist in C language or some C library?
Does bash imitate this way from C?
bash string c
asked Nov 19 at 23:09
Ben
2769
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
Bash manual mentions that
3.1.2.5 Locale-Specific Translation
A double-quoted string preceded by a dollar sign (‘$’) will cause the
string to be translated according to the current locale. If the
current locale is C or POSIX, the dollar sign is ignored. If the
string is translated and replaced, the replacement is double-quoted.
Does this way of specifying a string literal exist in C language or some C library?
Does bash imitate this way from C?
bash string c
asked Nov 19 at 23:09
Ben
2769
Bash manual mentions that
3.1.2.5 Locale-Specific Translation
A double-quoted string preceded by a dollar sign (‘$’) will cause the
string to be translated according to the current locale. If the
current locale is C or POSIX, the dollar sign is ignored. If the
string is translated and replaced, the replacement is double-quoted.
Does this way of specifying a string literal exist in C language or some C library?
Does bash imitate this way from C?
bash string c
bash string c
asked Nov 19 at 23:09
Ben
2769
asked Nov 19 at 23:09
Ben
2769
asked Nov 19 at 23:09
Ben
2769
asked Nov 19 at 23:09
Ben
2769
asked Nov 19 at 23:09
Ben
2769
2769
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
8
down vote
accepted
$"..." is Bash's way of accessing GNU gettext translations. In C code it would generally be gettext("...") or _("..."). Bash uses the system's default message catalog; a C application could also load up any catalogs it wanted to use.
The $" syntax is a Bash extension to resemble the existing parameter expansion syntax, and I suppose particularly the $' ANSI-C quoting it took from ksh and which may make it into POSIX in future. The C language does not support or have a parallel for the syntax itself.
answered Nov 19 at 23:32
Michael Homer
44.9k7117156
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
accepted
$"..." is Bash's way of accessing GNU gettext translations. In C code it would generally be gettext("...") or _("..."). Bash uses the system's default message catalog; a C application could also load up any catalogs it wanted to use.
The $" syntax is a Bash extension to resemble the existing parameter expansion syntax, and I suppose particularly the $' ANSI-C quoting it took from ksh and which may make it into POSIX in future. The C language does not support or have a parallel for the syntax itself.
answered Nov 19 at 23:32
Michael Homer
44.9k7117156
add a comment |
up vote
8
down vote
accepted
$"..." is Bash's way of accessing GNU gettext translations. In C code it would generally be gettext("...") or _("..."). Bash uses the system's default message catalog; a C application could also load up any catalogs it wanted to use.
The $" syntax is a Bash extension to resemble the existing parameter expansion syntax, and I suppose particularly the $' ANSI-C quoting it took from ksh and which may make it into POSIX in future. The C language does not support or have a parallel for the syntax itself.
answered Nov 19 at 23:32
Michael Homer
44.9k7117156
add a comment |
up vote
8
down vote
accepted
up vote
8
down vote
accepted
$"..." is Bash's way of accessing GNU gettext translations. In C code it would generally be gettext("...") or _("..."). Bash uses the system's default message catalog; a C application could also load up any catalogs it wanted to use.
The $" syntax is a Bash extension to resemble the existing parameter expansion syntax, and I suppose particularly the $' ANSI-C quoting it took from ksh and which may make it into POSIX in future. The C language does not support or have a parallel for the syntax itself.
answered Nov 19 at 23:32
Michael Homer
44.9k7117156
$"..." is Bash's way of accessing GNU gettext translations. In C code it would generally be gettext("...") or _("..."). Bash uses the system's default message catalog; a C application could also load up any catalogs it wanted to use.
The $" syntax is a Bash extension to resemble the existing parameter expansion syntax, and I suppose particularly the $' ANSI-C quoting it took from ksh and which may make it into POSIX in future. The C language does not support or have a parallel for the syntax itself.
answered Nov 19 at 23:32
Michael Homer
44.9k7117156
answered Nov 19 at 23:32
Michael Homer
44.9k7117156
answered Nov 19 at 23:32
Michael Homer
44.9k7117156
answered Nov 19 at 23:32
Michael Homer
44.9k7117156
44.9k7117156
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f482859%2fdoes-bash-imitate-locale-specific-translation-from-c%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
