Translating the "See Also" concept link

[Skooter]

Anyone know how to translate the "See Also" concept link? The Russsian translators are asking me...

[Skooter]

Thought I'd found it... The "See Also" text is set in the stylesheet - Select Show Link Styles - mc-label property is "See Also"
In Lingo, I filtered the File List on *.css
Double-clicked on Styles.css

BUT no mc-label style is offered for translation!!!

[GregStenhouse]

Outside of lingo...
Tools>Manage Language Skins.
Russian appears for me (v5), but you have to create and translate it yourself.
"See Also" appears under Formats>Concept Link

Cheers
Greg

[swills22]

This might help...In Flare, go to Tools > Manage Language Skins > select the language > Open file for editing.
Select the style to change/view from the list in the left pane > Index Entry > Labels.

[Skooter]

Thanks for your suggestions. So when I'm prompted ""Select the language to use as a template for the new one" I choose English? (is no Russian option) and then enter the translated text??? Makes me think of the other issue I posted - why isn't there a proper Russian language skin by now!!

[Mette Nyberg]

I still don't get it and I need to get to the bottom of this. The solution offered in the preceding replies only applies when you are doing Webhelp. I am doing a .chm file and I have Related Topics (or See Also, if you like) in tons of my topics. I can see the style in Flare in the .css, but there is no way I will let the translator tamper with the .css. We are doing languages that I don't have a chance to validate (Chinese, Russian, Polish) and I need a foolproof way of translating this sort of element.
I checked Lingo and I don't see the text Related Topics in the grid.
What on earth do you do????

[Skooter]

Good question! I am compiling a chm too. The Russians are still waiting for my answer!

In Flare, I went to Tools > Manage Language Skins > selected the language > Opened file for editing.
Selected the style to change/view from the list in the left pane > Index Entry > Labels.
(why "Index Entry" and not some name related to Concept Link I don't know...)
I then pasted in the Russian text for IndexEntry, but this was not reflected in the exported Lingo project.
(even though the language set as part of project properties is "Russian"),
needless to say, it did not pick up the user-defined file I had just created in:

\Application Data\MadCap Software\Flare\Language Skins\ru.fllng

[Skooter]

Next thing I tried: create a StylesRUS.css and replace the mc-label with Russian translation for "See Also". Did not work.

Next thing: open the Skin used for the HTML help and replace the mc-label with Russian translation for "See Also". Did not work.

That's it then, out of options! Maybe one day madcap will provide a proper altrenative to CHM files (since CHMs out put obviously not supported)

[GregStenhouse]

Just ran a quick check on my sample project with HTML help, and it seems to work via CSS. You need to alter the MC-Label property for the class Madcap|conceptLink. We're on Flare v5

Cheers
Greg

[Skooter]

Thanks Greg. Yes it did work (after I changed the mc-label for the <DEFAULT> medium - I had changed it for the non-print medium but not selected it in my TEST target!)

[Mette Nyberg]

But we are still talking manual post processing and yet another thing you need to keep in mind to ask the translator to do. I would expect to see the text in the grid for the css so the translator can make the change from within Lingo. Obviously not an option at this point in time. Weird since you can see text added to for example the auto-numbering (if you want to add text such as Chapter in front of your numbering).

[Skooter]

I agree, although in my case it's one more thing for the tech writer to do for every Russian and Chinese build.