Hello! I am new MadCap Flare (version 6.1.0) user and have just started trying out language skins. I have noticed that no matter what language skin I choose two accordion items are never translated: Table of Contents and Favourites. I poked around and discovered that the labels for these two items are not translated in the stylesheet.xml file when the Web Help is build.
For example, if I use the German language skin then the following section should be
<Style Name="AccordionItem">
<Classes>
<StyleClass Name="TOC">
<Properties>
<Property Name="Label">Inhalt</Property>
But instead it is
<Style Name="AccordionItem">
<Classes>
<StyleClass Name="TOC">
<Properties>
<Property Name="Label">Table of Contents</Property>
As I stated above this is also a problem for Favourites but the Search and Glossary accordion items are fine. I checked the language skin settings and the proper translations are part of the skin. It seems that for some reason the stylesheet.xml file is not being updated correctly. If I manually change these settings and reload the Web Help page then I see the correct terms but obsioulsy I don't want to have to make a manual change every time I build it.
Can anyone help with this?
Thanks!
Vanessa
Language Skins Issue
-
nessmonster
- Propeller Head
- Posts: 10
- Joined: Tue Sep 06, 2011 12:04 pm
- Location: Ottawa, Canada
-
rob hollinger
- Propellus Maximus
- Posts: 661
- Joined: Mon Mar 17, 2008 8:40 am
Re: Language Skins Issue
Open the WebHelp target file.
Click on the language tab.
Select the output language you want to use (German).
Build and it should now be translated.
Click on the language tab.
Select the output language you want to use (German).
Build and it should now be translated.
Rob Hollinger
MadCap Software
MadCap Software
-
nessmonster
- Propeller Head
- Posts: 10
- Joined: Tue Sep 06, 2011 12:04 pm
- Location: Ottawa, Canada
Re: Language Skins Issue
Hi! I already did that of course and that is how I noticed that some of the accordion items were translated while others were not. I am attaching a screenshot of what I see after changing the language to German.
As I said, I checked this out with a developer here at my work and we discovered that it is a problem in the stylesheet.xml file.
Any other ideas?
Thanks!
Vanessa
As I said, I checked this out with a developer here at my work and we discovered that it is a problem in the stylesheet.xml file.
Any other ideas?
Thanks!
Vanessa
You do not have the required permissions to view the files attached to this post.
-
nessmonster
- Propeller Head
- Posts: 10
- Joined: Tue Sep 06, 2011 12:04 pm
- Location: Ottawa, Canada
Re: Language Skins Issue
Solved!
Rob Hollinger figured it out:
When you type text into the Labels of you project skin, they will over-write the Language skin.
Open your projects Skin file.
Click on the Styles tab
Open AccordionItem and select TOC
Under General, I assume you see "Table of Contents".
Select the text and delete it.
It should default back to "TOC".
Build and verify the TOC item is now from the language skin.
Do the same for the Favorites tab.
~~~
Rob Hollinger figured it out:
When you type text into the Labels of you project skin, they will over-write the Language skin.
Open your projects Skin file.
Click on the Styles tab
Open AccordionItem and select TOC
Under General, I assume you see "Table of Contents".
Select the text and delete it.
It should default back to "TOC".
Build and verify the TOC item is now from the language skin.
Do the same for the Favorites tab.
~~~
Re: Language Skins Issue
I am also new with and I have an same issue in Macap Flare 2017 with the Glossary text content
I have set the right language to Dutch but on the (output type) PDF file the name of Glossary is still in the English language and not in Dutch
I have set the language in the Project properties also to Dutch, but it does not help.
I have set the right language to Dutch but on the (output type) PDF file the name of Glossary is still in the English language and not in Dutch
I have set the language in the Project properties also to Dutch, but it does not help.
You do not have the required permissions to view the files attached to this post.
-
SKamprowski
- Sr. Propeller Head
- Posts: 277
- Joined: Fri Feb 13, 2015 8:25 am
- Location: Germany
Re: Language Skins Issue
Hi Beaver,
I can offer a workaround:
Instead of choosing "Generate glossar proxy" for your advanced PDF Output option you may add a topic with a heading of your choice which contains a Glossary Proxy.
For German users it is possible to modify the text used for "Generate glossar proxy" in advanced PDF Output option by changing it in a language skin based upon what MadCap has translated: I changed the German value for label Accordion item.Glossary in the section Print and Online (see attached screenshot) and it is reflected in my PDF.
I can offer a workaround:
Instead of choosing "Generate glossar proxy" for your advanced PDF Output option you may add a topic with a heading of your choice which contains a Glossary Proxy.
For German users it is possible to modify the text used for "Generate glossar proxy" in advanced PDF Output option by changing it in a language skin based upon what MadCap has translated: I changed the German value for label Accordion item.Glossary in the section Print and Online (see attached screenshot) and it is reflected in my PDF.
Kind regards,
Sabine Kamprowski
DocToHelp MVP (by ComponentOne)
Sabine Kamprowski
DocToHelp MVP (by ComponentOne)
Re: Language Skins Issue
Thanks Sabine very much
I have added File type "Languages Skins" and can change the Glossary name to Woordenlijst (as on your picture)
How does my (PDF) Target know to use this new Language Skin.
In the Target Editor i can not found on the different tabs where i can select this Language Skin
Thanks inadvance.
Kind regards,
Beaver (from Holland)
I have added File type "Languages Skins" and can change the Glossary name to Woordenlijst (as on your picture)
How does my (PDF) Target know to use this new Language Skin.
In the Target Editor i can not found on the different tabs where i can select this Language Skin
Thanks inadvance.
Kind regards,
Beaver (from Holland)
-
SKamprowski
- Sr. Propeller Head
- Posts: 277
- Joined: Fri Feb 13, 2015 8:25 am
- Location: Germany
Re: Language Skins Issue
Hi Beaver,
I only had to choose exactly the same language in pdfs language settings to get it work
I only had to choose exactly the same language in pdfs language settings to get it work
Kind regards,
Sabine Kamprowski
DocToHelp MVP (by ComponentOne)
Sabine Kamprowski
DocToHelp MVP (by ComponentOne)