Chemmacros scheme translation
How do governments keep track of their issued currency?
What language is the software written in on the ISS?
"You've got another thing coming" - translation into French
Soft question: Examples where lack of mathematical rigour cause security breaches?
Can a black dragonborn's acid breath weapon destroy objects?
PhD - Well known professor or well known school?
Arriving at the same result with the opposite hypotheses
What is the actual quality of machine translations?
Was Jesus good at singing?
Are there downsides to using std::string as a buffer?
Implement Homestuck's Catenative Doomsday Dice Cascader
Should an arbiter claim draw at a K+R vs K+R endgame?
Was the output of the C64 SID chip 8 bit sound?
How is water heavier than petrol, even though its molecular weight is less than petrol?
Is open-sourcing the code of a webapp not recommended?
Chemmacros scheme translation
How can I most clearly write a homebrew item that affects the ground below its radius after the initial explosion it creates?
Facebook Marketing API asset access suddenly denied
What's the largest optical telescope mirror ever put in space?
What are the peak hours for public transportation in Paris?
At what point in time did Dumbledore ask Snape for this favor?
Is using haveibeenpwned to validate password strength rational?
Frame failure sudden death?
How to officially communicate to a non-responsive colleague?
Chemmacros scheme translation
I'm trying to translate the word "Scheme" in the captions of chemmacros
schemes. I'm writing in spanish, so I want to change "Scheme 1" to "Esquema 1", for example.
I don't know if I'm not understanding the manual or how the package and module (lang
) work.
I tried a lot of things so far, but I have this and it gives error:
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
DeclareChemTranslationspanishschemeesquema
DeclareChemTranslationspanishSchemeEsquema
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
! Package translations Error: Unknown language `scheme'.See the translations package documentation for explanation.Type H for immediate help.... ...reChemTranslationspanishschemeesquema
I'm using this version: This is pdfTeX, Version 3.14159265-2.6-1.40.20 (MiKTeX 2.9.7000 64-bit) (preloaded format=pdflatex 2019.4.23) 3 JUN 2019 19:24
chemmacros spanish
add a comment |
I'm trying to translate the word "Scheme" in the captions of chemmacros
schemes. I'm writing in spanish, so I want to change "Scheme 1" to "Esquema 1", for example.
I don't know if I'm not understanding the manual or how the package and module (lang
) work.
I tried a lot of things so far, but I have this and it gives error:
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
DeclareChemTranslationspanishschemeesquema
DeclareChemTranslationspanishSchemeEsquema
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
! Package translations Error: Unknown language `scheme'.See the translations package documentation for explanation.Type H for immediate help.... ...reChemTranslationspanishschemeesquema
I'm using this version: This is pdfTeX, Version 3.14159265-2.6-1.40.20 (MiKTeX 2.9.7000 64-bit) (preloaded format=pdflatex 2019.4.23) 3 JUN 2019 19:24
chemmacros spanish
Please add to your question the complete error message you got in the log file (it is important to keep line breaks!). Which TeX distribution in which version do you use? Add the first line of your log file to your question, it tells us your used tex distribution and version number ...
– Kurt
9 hours ago
add a comment |
I'm trying to translate the word "Scheme" in the captions of chemmacros
schemes. I'm writing in spanish, so I want to change "Scheme 1" to "Esquema 1", for example.
I don't know if I'm not understanding the manual or how the package and module (lang
) work.
I tried a lot of things so far, but I have this and it gives error:
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
DeclareChemTranslationspanishschemeesquema
DeclareChemTranslationspanishSchemeEsquema
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
! Package translations Error: Unknown language `scheme'.See the translations package documentation for explanation.Type H for immediate help.... ...reChemTranslationspanishschemeesquema
I'm using this version: This is pdfTeX, Version 3.14159265-2.6-1.40.20 (MiKTeX 2.9.7000 64-bit) (preloaded format=pdflatex 2019.4.23) 3 JUN 2019 19:24
chemmacros spanish
I'm trying to translate the word "Scheme" in the captions of chemmacros
schemes. I'm writing in spanish, so I want to change "Scheme 1" to "Esquema 1", for example.
I don't know if I'm not understanding the manual or how the package and module (lang
) work.
I tried a lot of things so far, but I have this and it gives error:
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
DeclareChemTranslationspanishschemeesquema
DeclareChemTranslationspanishSchemeEsquema
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
! Package translations Error: Unknown language `scheme'.See the translations package documentation for explanation.Type H for immediate help.... ...reChemTranslationspanishschemeesquema
I'm using this version: This is pdfTeX, Version 3.14159265-2.6-1.40.20 (MiKTeX 2.9.7000 64-bit) (preloaded format=pdflatex 2019.4.23) 3 JUN 2019 19:24
chemmacros spanish
chemmacros spanish
edited 9 hours ago
Daniel Álvarez
asked 9 hours ago
Daniel ÁlvarezDaniel Álvarez
625
625
Please add to your question the complete error message you got in the log file (it is important to keep line breaks!). Which TeX distribution in which version do you use? Add the first line of your log file to your question, it tells us your used tex distribution and version number ...
– Kurt
9 hours ago
add a comment |
Please add to your question the complete error message you got in the log file (it is important to keep line breaks!). Which TeX distribution in which version do you use? Add the first line of your log file to your question, it tells us your used tex distribution and version number ...
– Kurt
9 hours ago
Please add to your question the complete error message you got in the log file (it is important to keep line breaks!). Which TeX distribution in which version do you use? Add the first line of your log file to your question, it tells us your used tex distribution and version number ...
– Kurt
9 hours ago
Please add to your question the complete error message you got in the log file (it is important to keep line breaks!). Which TeX distribution in which version do you use? Add the first line of your log file to your question, it tells us your used tex distribution and version number ...
– Kurt
9 hours ago
add a comment |
3 Answers
3
active
oldest
votes
One issue is here an error in the manual.
You have to use the following definitions
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
to get no error message. Please see that the order of parameters has changed! First key
, then language
and then translation
. In the manual this is simply wrong (see red arrow with flash), but the second command works as described ...
Perhaps because l3kernel has changed it seems that the definitions above do not find their way into the document. Please see the following code
documentclass[spanish]article % <====================================
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
%chemsetuplanguage=spanish
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
%DeclareChemTranslationsschemespanish=esquema % <==================
%DeclareChemTranslationsSchemespanish=Esquema % <==================
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
and its result (compiled with MIKTeX version pdfTeX, Version 3.14159265-2.6-1.40.20 (MiKTeX 2.9.7050 64-bit)
):
As you can see the language for scheme
has not changed!
Now adding
renewcommandschemenameEsquema
after begindocument
gives you the following result:
while adding the same line before begindocuments
results in an error because command schemename
is only known after document has started ...
I did not investigated now the code (I did not learn using l3kernel until now) what is the reason that the new defined translation for scheme
in spanish is not printed in the document.
I suggest you make a bug report for the maintainer of that package to get the manual corrected and to get an working translation ...
add a comment |
As @Kurt already mentioned, the manual is wrong and the language should come second. Moreover, the list of translation keys in the manual is also a bit confusing. The list mentions both scheme
and scheme-name
, but only scheme-name
works. This can be traced in the source code of the scheme module around line 250, where schema-name
is used for the predefined translation to German - but again somewhat confusingly in a ChemCompatibilityTo5.6
block, so it might be an old version of the syntax - but at least it works.
An issue on the Github page certainly looks like a good idea, to update the manual and/or the code to make the behavior more intuitive.
MWE:
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
DeclareChemTranslationscheme-namespanishEsquema
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
Result:
add a comment |
A way to change it is simply putting renewcommandschemenameEsquema
after begindocument
, but I don't know why I can't change the translation.
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
begindocument
renewcommandschemenameEsquema
beginscheme
captionLorem ipsum
endscheme
enddocument
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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%2ftex.stackexchange.com%2fquestions%2f494010%2fchemmacros-scheme-translation%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
One issue is here an error in the manual.
You have to use the following definitions
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
to get no error message. Please see that the order of parameters has changed! First key
, then language
and then translation
. In the manual this is simply wrong (see red arrow with flash), but the second command works as described ...
Perhaps because l3kernel has changed it seems that the definitions above do not find their way into the document. Please see the following code
documentclass[spanish]article % <====================================
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
%chemsetuplanguage=spanish
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
%DeclareChemTranslationsschemespanish=esquema % <==================
%DeclareChemTranslationsSchemespanish=Esquema % <==================
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
and its result (compiled with MIKTeX version pdfTeX, Version 3.14159265-2.6-1.40.20 (MiKTeX 2.9.7050 64-bit)
):
As you can see the language for scheme
has not changed!
Now adding
renewcommandschemenameEsquema
after begindocument
gives you the following result:
while adding the same line before begindocuments
results in an error because command schemename
is only known after document has started ...
I did not investigated now the code (I did not learn using l3kernel until now) what is the reason that the new defined translation for scheme
in spanish is not printed in the document.
I suggest you make a bug report for the maintainer of that package to get the manual corrected and to get an working translation ...
add a comment |
One issue is here an error in the manual.
You have to use the following definitions
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
to get no error message. Please see that the order of parameters has changed! First key
, then language
and then translation
. In the manual this is simply wrong (see red arrow with flash), but the second command works as described ...
Perhaps because l3kernel has changed it seems that the definitions above do not find their way into the document. Please see the following code
documentclass[spanish]article % <====================================
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
%chemsetuplanguage=spanish
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
%DeclareChemTranslationsschemespanish=esquema % <==================
%DeclareChemTranslationsSchemespanish=Esquema % <==================
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
and its result (compiled with MIKTeX version pdfTeX, Version 3.14159265-2.6-1.40.20 (MiKTeX 2.9.7050 64-bit)
):
As you can see the language for scheme
has not changed!
Now adding
renewcommandschemenameEsquema
after begindocument
gives you the following result:
while adding the same line before begindocuments
results in an error because command schemename
is only known after document has started ...
I did not investigated now the code (I did not learn using l3kernel until now) what is the reason that the new defined translation for scheme
in spanish is not printed in the document.
I suggest you make a bug report for the maintainer of that package to get the manual corrected and to get an working translation ...
add a comment |
One issue is here an error in the manual.
You have to use the following definitions
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
to get no error message. Please see that the order of parameters has changed! First key
, then language
and then translation
. In the manual this is simply wrong (see red arrow with flash), but the second command works as described ...
Perhaps because l3kernel has changed it seems that the definitions above do not find their way into the document. Please see the following code
documentclass[spanish]article % <====================================
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
%chemsetuplanguage=spanish
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
%DeclareChemTranslationsschemespanish=esquema % <==================
%DeclareChemTranslationsSchemespanish=Esquema % <==================
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
and its result (compiled with MIKTeX version pdfTeX, Version 3.14159265-2.6-1.40.20 (MiKTeX 2.9.7050 64-bit)
):
As you can see the language for scheme
has not changed!
Now adding
renewcommandschemenameEsquema
after begindocument
gives you the following result:
while adding the same line before begindocuments
results in an error because command schemename
is only known after document has started ...
I did not investigated now the code (I did not learn using l3kernel until now) what is the reason that the new defined translation for scheme
in spanish is not printed in the document.
I suggest you make a bug report for the maintainer of that package to get the manual corrected and to get an working translation ...
One issue is here an error in the manual.
You have to use the following definitions
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
to get no error message. Please see that the order of parameters has changed! First key
, then language
and then translation
. In the manual this is simply wrong (see red arrow with flash), but the second command works as described ...
Perhaps because l3kernel has changed it seems that the definitions above do not find their way into the document. Please see the following code
documentclass[spanish]article % <====================================
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
%chemsetuplanguage=spanish
DeclareChemTranslationschemespanishesquema % <===================
DeclareChemTranslationSchemespanishEsquema % <===================
%DeclareChemTranslationsschemespanish=esquema % <==================
%DeclareChemTranslationsSchemespanish=Esquema % <==================
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
and its result (compiled with MIKTeX version pdfTeX, Version 3.14159265-2.6-1.40.20 (MiKTeX 2.9.7050 64-bit)
):
As you can see the language for scheme
has not changed!
Now adding
renewcommandschemenameEsquema
after begindocument
gives you the following result:
while adding the same line before begindocuments
results in an error because command schemename
is only known after document has started ...
I did not investigated now the code (I did not learn using l3kernel until now) what is the reason that the new defined translation for scheme
in spanish is not printed in the document.
I suggest you make a bug report for the maintainer of that package to get the manual corrected and to get an working translation ...
answered 7 hours ago
KurtKurt
43.9k1050170
43.9k1050170
add a comment |
add a comment |
As @Kurt already mentioned, the manual is wrong and the language should come second. Moreover, the list of translation keys in the manual is also a bit confusing. The list mentions both scheme
and scheme-name
, but only scheme-name
works. This can be traced in the source code of the scheme module around line 250, where schema-name
is used for the predefined translation to German - but again somewhat confusingly in a ChemCompatibilityTo5.6
block, so it might be an old version of the syntax - but at least it works.
An issue on the Github page certainly looks like a good idea, to update the manual and/or the code to make the behavior more intuitive.
MWE:
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
DeclareChemTranslationscheme-namespanishEsquema
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
Result:
add a comment |
As @Kurt already mentioned, the manual is wrong and the language should come second. Moreover, the list of translation keys in the manual is also a bit confusing. The list mentions both scheme
and scheme-name
, but only scheme-name
works. This can be traced in the source code of the scheme module around line 250, where schema-name
is used for the predefined translation to German - but again somewhat confusingly in a ChemCompatibilityTo5.6
block, so it might be an old version of the syntax - but at least it works.
An issue on the Github page certainly looks like a good idea, to update the manual and/or the code to make the behavior more intuitive.
MWE:
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
DeclareChemTranslationscheme-namespanishEsquema
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
Result:
add a comment |
As @Kurt already mentioned, the manual is wrong and the language should come second. Moreover, the list of translation keys in the manual is also a bit confusing. The list mentions both scheme
and scheme-name
, but only scheme-name
works. This can be traced in the source code of the scheme module around line 250, where schema-name
is used for the predefined translation to German - but again somewhat confusingly in a ChemCompatibilityTo5.6
block, so it might be an old version of the syntax - but at least it works.
An issue on the Github page certainly looks like a good idea, to update the manual and/or the code to make the behavior more intuitive.
MWE:
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
DeclareChemTranslationscheme-namespanishEsquema
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
Result:
As @Kurt already mentioned, the manual is wrong and the language should come second. Moreover, the list of translation keys in the manual is also a bit confusing. The list mentions both scheme
and scheme-name
, but only scheme-name
works. This can be traced in the source code of the scheme module around line 250, where schema-name
is used for the predefined translation to German - but again somewhat confusingly in a ChemCompatibilityTo5.6
block, so it might be an old version of the syntax - but at least it works.
An issue on the Github page certainly looks like a good idea, to update the manual and/or the code to make the behavior more intuitive.
MWE:
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
DeclareChemTranslationscheme-namespanishEsquema
begindocument
beginscheme
captionLorem ipsum
endscheme
enddocument
Result:
answered 6 hours ago
MarijnMarijn
9,514639
9,514639
add a comment |
add a comment |
A way to change it is simply putting renewcommandschemenameEsquema
after begindocument
, but I don't know why I can't change the translation.
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
begindocument
renewcommandschemenameEsquema
beginscheme
captionLorem ipsum
endscheme
enddocument
add a comment |
A way to change it is simply putting renewcommandschemenameEsquema
after begindocument
, but I don't know why I can't change the translation.
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
begindocument
renewcommandschemenameEsquema
beginscheme
captionLorem ipsum
endscheme
enddocument
add a comment |
A way to change it is simply putting renewcommandschemenameEsquema
after begindocument
, but I don't know why I can't change the translation.
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
begindocument
renewcommandschemenameEsquema
beginscheme
captionLorem ipsum
endscheme
enddocument
A way to change it is simply putting renewcommandschemenameEsquema
after begindocument
, but I don't know why I can't change the translation.
documentclassarticle
usepackage[utf8]inputenc
usepackage[spanish]babel
usepackagechemmacros
chemsetupmodules=scheme
begindocument
renewcommandschemenameEsquema
beginscheme
captionLorem ipsum
endscheme
enddocument
answered 8 hours ago
Daniel ÁlvarezDaniel Álvarez
625
625
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX 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.
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%2ftex.stackexchange.com%2fquestions%2f494010%2fchemmacros-scheme-translation%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
Please add to your question the complete error message you got in the log file (it is important to keep line breaks!). Which TeX distribution in which version do you use? Add the first line of your log file to your question, it tells us your used tex distribution and version number ...
– Kurt
9 hours ago