Quantcast
Channel: ProZ.com Translation Forums
Viewing all 29885 articles
Browse latest View live

How to translate keyword entries in MadCap Flare files? | Workaround

$
0
0
Forum: SDL Trados support
Topic: How to translate keyword entries in MadCap Flare files?
Poster: Jorge Payan
Post title: Workaround

I preferably use MadCap Lingo in order to prepare Flare projects to be translated with SDL Studio (or with DVX, which is my favorite TEnT). MadCap Lingo is indeed able to correctly identify the files and parts (snippets, etc) which are candidates for translation. I don't know specifically about keywords.

My suggestion: Download the Lingo 30-days free trial and reprocess the Flare files in order to produce xliff files to be translated with Studio. I imagine that you can repopulate most of them using your existing TMs.

Font size in Trados Studio 2015 | Thank you so much

$
0
0
Forum: SDL Trados support
Topic: Font size in Trados Studio 2015
Poster: María Leonor Acevedo-Miranda
Post title: Thank you so much

It worked 100%. So, so useful

again thank you so much

[quote]Bob Scott wrote:

Hi Monica,

In Studio, go to File > Options > Editor > Font Adaptation, check the Adapt font sizes box, then enter the minimum point sizes you want. No restart necessary.

Hope this helps.

Bob [/quote]

How to translate keyword entries in MadCap Flare files? | MadCap Lingo

$
0
0
Forum: SDL Trados support
Topic: How to translate keyword entries in MadCap Flare files?
Poster: Alex Lichanow
Post title: MadCap Lingo

There is an actual import filter for MadCap XML files in Studio. I only needed to include the *.flsnp file type in its file type definitions since I didn't need to translate any TOCs or index entries.
As for the keywords, they are contained in the topic files (*.html) and are imported according to the HTML 5 file type settings.
They will be found in entries like documented in the screenshot in my original posting, which means that they are nested within header formatting tags. It is this nested structure that prevents me from importing them as editable contents.

Studio Trados doesn't recognize Multiterm entries

$
0
0
Forum: SDL Trados support
Topic: Studio Trados doesn't recognize Multiterm entries
Poster: Bruno Bertoni

Hi!

I have a massive job to deliver by Friday and I just can't work because the Multiterm termbase isn't recognized on Trados. I can add it to the project settings, but it doesn't return results on the text. I can access it on Excel so I know there are terms, but when I open it on the Multiterm software, it returns the following:

Error processing command line arguments: Method not found: 'Sdl.MultiTerm.Client.Connectors.ServerPrivilege Sdl.MultiTerm.Client.Connectors.ServerProxy.LogIn(System.String, System.String, System.String, Boolean, Boolean, Sdl.Enterprise2.Studio.Platform.Client.IdentityModel.PersistOption)'.
[...]

I'm not sure if it's a problem with Trados or the MT. I asked the client to resend me the TB, in case it was corrupted somehow, but it didn't solve the problem. I already tried to change the settings about fuzzy and search depth, but no deal. I have another TB for the same project that seems to work, but this specific one (the main TB for the project) doesn't.

Do you know how to solve it or some alternative plugins that work as Multiterm? I really need to finish this job in time and I can't keep searching term by term on Excel -- it would take 3x more time and I'd probably leave several basic terms without standardization.

Thank you

How to translate keyword entries in MadCap Flare files? | Why I use MadCap Lingo instead of the pertinent Studio file type

$
0
0
Forum: SDL Trados support
Topic: How to translate keyword entries in MadCap Flare files?
Poster: Jorge Payan
Post title: Why I use MadCap Lingo instead of the pertinent Studio file type

[quote]Alex Lichanow wrote:

There is an actual import filter for MadCap XML files in Studio. [/quote]

I am well conscious about the existence of that file type definition from Studio 2015 on. I tried to use it in the past for translating Flare projects, but I had to manually choose which files to translate (out of more than 300 hundred in my case!!) and needed tweaking a lot the embedded processors. That is why I resorted to use MadCap Lingo for automatically choosing the files and preparing them in order to translate using Studio (or DVX). I could translate in MadCap Lingo itself, but it offers a very deficient editor.

[quote]They will be found in entries like documented in the screenshot in my original posting, which means that they are nested within header formatting tags. It is this nested structure that prevents me from importing them as editable contents.[/quote]

I am quite interested in your problem and the way it can be solved it. I know that I may be a silly question, but ¿were you able to convert the nested elements to Studio inline tags? If so, ¿could you convert them to translatable using the MadCap parser settings?

Studio Trados doesn't recognize Multiterm entries | This might be related to your Multiterm version

$
0
0
Forum: SDL Trados support
Topic: Studio Trados doesn't recognize Multiterm entries
Poster: Jessica Grisogani
Post title: This might be related to your Multiterm version

Hello,

I had a similar problem yesterday. I use SDL TRADOS STUDIO 2017.
I checked online and found these results:
[url removed]
[url removed]

After reading this infomation I realized that I had recently updated the Multiterm version without doing the same for SDL TRADOS STUDIO.
After updating it (see Help -> Check for Updates on Studio and follow the instructions) the problem was solved and the interaction between Multiterm and STUDIO worked well as usual.

I hope this might help you.

Kind regards,
Jessica

How to translate keyword entries in MadCap Flare files? | Tags and parser settings

$
0
0
Forum: SDL Trados support
Topic: How to translate keyword entries in MadCap Flare files?
Poster: Alex Lichanow
Post title: Tags and parser settings

[quote]Jorge Payan wrote:

I am quite interested in your problem and the way it can be solved it. I know that I may be a silly question, but ¿were you able to convert the nested elements to Studio inline tags? If so, ¿could you convert them to translatable using the MadCap parser settings? [/quote]

Yes, I have managed to import the nested elements as tags, but unfortunately, this is not what I want to achieve since Trados doesn't offer any possibility to edit tags.
Another problem here is that the MadCap parser settings are irrelevant in this specific case because the keywords are not found in the Flare-specific files but in the topic files, which are "regular" HTML 5, but with proprietary MadCap markups.
Therefore, what I need to edit correctly at some stage is the parser settings for HTML 5.
And this is exactly what is slowly driving me crazy: I can define settings for h1 elements (which are translatable to begin with) and I can define settings for MadCap elements (which are not part of the default parser settings but must be created specifically). But I just cannot seem to find any solution to make MadCap elements NESTED WITHIN H1 ELEMENTS translatable.

QA Checker 3.0 > Check numbers | one more question

$
0
0
Forum: SDL Trados support
Topic: QA Checker 3.0 > Check numbers
Poster: Lenart
Post title: one more question

Source text: règlement no 207/2009

Correct Target text: xy

Regex source: règlement \d*

Regex target: .*

rule: if source and target match

I get a signal that regex source is recognized in source text and don't understand why. In source text a word „règlement“ is followed by word „no“ and not by a number. Anybody sees the problem?

thank you!

[Edited at 2019-06-19 14:55 GMT]

Can't export target document when translating from Japanese Excel file

$
0
0
Forum: SDL Trados support
Topic: Can't export target document when translating from Japanese Excel file
Poster: Facundo Pallero

Hi all,

I'm having trouble exporting target documents when working with Japanese Excel source files. The error I get is "Object reference not set to an instance of an object".

Everything works fine when I translate from Japanese in any other file format or from other languages in Excel.

Any idea what could be causing this? Any input would be much appreciated.

Best,
Facundo

Problem with xlf file | Noted!

$
0
0
Forum: SDL Trados support
Topic: Problem with xlf file
Poster: Anne Gaujard-Scott
Post title: Noted!

Thank you for this piece of advice, Anna, I will give it a try.
Really I should invest some time in properly training myself with Trados! I much prefer other simpler softwares but I assume it could save me a lot of time if I actually knew how to use it properly! :)

Double click does not open files or packages in Studio 2017

$
0
0
Forum: SDL Trados support
Topic: Double click does not open files or packages in Studio 2017
Poster: Avraham Levi

Hi,

in the last few weeks, since I installed and removed Studio Trados 2019, double clicking on projects or packages or single files in Studio 2017 does not open them. I am forced to first open the software and only then I can open the project, package or single file from within.

Can someone help?

Thanks

Article 0

$
0
0
Forum: SDL Trados support
Topic:
Poster: Lenart



[Edited at 2019-06-22 11:48 GMT]

Problem with xlf file | I need help too

$
0
0
Forum: SDL Trados support
Topic: Problem with xlf file
Poster: lundeghe
Post title: I need help too

I created file in trados 2017 and shared with many translators. The translators have returned their work and I am unable to merge all the translations into 1 file.

Double click does not open files or packages in Studio 2017 | Maybe...

$
0
0
Forum: SDL Trados support
Topic: Double click does not open files or packages in Studio 2017
Poster: Giovanni Guarnieri MITI, MIL
Post title: Maybe...

the package file extension has been changed and associated to Studio 2019 program when you installed it and now that you have uninstalled it, you need to associate it to Studio 2017 again, otherwise they won't open...

Only half of the translated file was exported in Trados 2015 | had the same problem with graphics....

$
0
0
Forum: SDL Trados support
Topic: Only half of the translated file was exported in Trados 2015
Poster: Kean Hall
Post title: had the same problem with graphics....

[quote]Christine Andersen wrote:

There was an untranslatable section of graphics in the text, and after this the target file remained untranslated.
Strange, because there were several earlier sections of graphics, which were ignored by Trados, and so they caused no trouble.

As it was only a small section, I cut and pasted the text from Studio into the target file, but it took me extra time! [/quote]

Had the same problem with Trados 2017...after the first graphic the finalised file was all in the source language. I had to delete all the graphics and run it back through as a new job & then finalise and add the graphics back in. Ultimately not too much extra work but nonetheless heart-stopping when you're on a tight deadline! Thankfully I came across this thread and managed to sort it out!

Can't I delete a newly added target language from a project? | It worked!

$
0
0
Forum: SDL Trados support
Topic: Can't I delete a newly added target language from a project?
Poster: Marina Torruella Bonsoms
Post title: It worked!

Hi,

Sorry I didn't see your reply for a while!

Removing just the Language Direction tag worked for me! Which is a relief, because there were many other instances of the language code.

Thanks a lot for your help!

Double click does not open files or packages in Studio 2017 | Repair Trados Studio in Control Panel

$
0
0
Forum: SDL Trados support
Topic: Double click does not open files or packages in Studio 2017
Poster: NeoAtlas
Post title: Repair Trados Studio in Control Panel

Go to Control Panel, search for the Trados Studio item, right-click on it and select Repair.

Trados 2019 - Parameter not valid!

$
0
0
Forum: SDL Trados support
Topic: Trados 2019 - Parameter not valid!
Poster: Gabriele Demuth

Hi there,

When typing in Trados I often suddenly receive the error message "Parameter not valid!" and I am unable to continue. I temporarily resolve this by closing and reopening the file I am working on, but it reappears and is getting progressively worse. I am also unable to copy within the document.

I have tried repairing the application, but it didn't help.

Has anyone experienced this and/or has any solutions?

Trados 2019 - Parameter not valid! | Nobody seems to have these problems?

$
0
0
Forum: SDL Trados support
Topic: Trados 2019 - Parameter not valid!
Poster: Gabriele Demuth
Post title: Nobody seems to have these problems?

Hm, it seems that this is not a common problem.

I never had any problems with Trados 2015, but since upgrading to 2019, especially after the last upgrade its dreadful.

It also seems copy/paste in the editor is not always working, now TM fails to update... I just feel littered with error messages and problems since changing to Trados 2019. Also termbase management is not working that well... and I don't think its just me.

I have sent a support message, but somehow I feel quite upset by the prospect of signing up to a support contract and paying more to have a system sorted out that used to work well for me but since upgrading has cost me so much time and annoyance.

SDL Trados automaticly replace terms

$
0
0
Forum: SDL Trados support
Topic: SDL Trados automaticly replace terms
Poster: Dmitrij_1980

Hallo.
There is a question about working with Trados. In trados, is there such a setting that (using machine translation from Google API) allowes trados automatically replace some words of machine translation with words from the terminological base?

Well, for example, the matter that needs to be translated into German often contains the word "management". The mashine translator from Google API uses automaticly also the word "management". But I would like that trados independently and automaticly after the mashine translation would replace the word "management" with the german word "steuerung" (which is in the terminological database as a translation of the word "management"). Thera are a lot of such words for my translation. So i would like to have the replacement automaticly. Machine translation is needed in order to create the ground structure, with which it will be possible to work.

Unfurtunatelynow i have only the testversion of SDL Trados and there its even not possible to use the multiterm plugin for terms and to try it out. And its also not possible to use other plugins in the test version. In the next vew day i have to decide which translation programm to buy. And this option, which i discribed above would be very useful.

Lg
Viewing all 29885 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>