• State Suggested Answer
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 433 subscribers
  • Views 5389 views
  • Users 0 members are here
Options
Related

ini files in Studio 2015

Asta GM

How to translate ini files in Studio 2015? I have added manually an extension *.mqxliff but still the program does not recognize ini files. Anyone who could help me?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hello ,

    I think you may be a little confused here. If this is an INI file that would have been used in Trados then this is not translated itself. It can be used to create filetype settings in Studio to open another file, or it can be used in Trados to create a TTX which can then be handled in Studio without the need for an INI at all.

    If it's actually a file containing translatable text but with the extension INI then you need to create a custom filetype in Studio to handle this. Possibly not to difficult it just depends on the content. Can you share an example of this INI file?

    I'm not sure why you are referring to *.mqxliff as this really has absolutely nothing to do with this based on the information I have been able to glean from you so far.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0
    Save the files on your HDD. Right click any of those and say "Open with", then chose Notepad. This way you will see the structure of data in these files. recently we've had a similar task, where the translatable text started after the equal sign (=). So we just created a file type like Paul suggests, using the regular expressions text file type as basis.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Paul

    Hi Paul, thank you for the answer. I have never worked with *.mqxliff files on Studio. Actually I have a Word file and mqxliff.ini file. The instructions are as follow: 1. Open SDL Studio, go to the File Type option. Select the XLIFF filter, and add the *.mqxliff file extension to the existing XLIFF filters (File dialog wildcard expression: *.xlf;*.xliff;*.mqxliff). 2. Then create a project in SDL Studio, and import the *.mqxliff file (tried to import it on Project files step) SDL Studio will from now on recognize this file extension, since you added it to the existing xliff filter. 3. Use Save target as and deliver the file as *.mqxliff (instead of *SDLxliff). I dont see where I could attach the INI file in here 
  • 0 in reply to Jerzy Czopik
    Hi Jerzy, thank you for your answer. I looked through Notepad and it does not contain the text that should be translated, so as I understand I should create a *.mqxliff file myself from word file (if it is possible)? And in this case, in which stage I should apply that ini file that is provided (it's not a file for translation). I cannot fully understand how to create a file that Paul suggests
  • 0 in reply to Asta GM
    All your description sounds more than strange to me. Without seeing the files no one will be able to help. MQXLIFF files are natively supported by several versions of Studio, starting at least from 2015 AFAIR. If not, you just need to download this file type appstore.sdl.com/.../ and install it. Then Studio will recognize mqxliff with no problem.
    Can you post a screenshot of such ini file, opened in Notepad?

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Jerzy Czopik
    Actually all the files I have is a docx file and that ini file, its part is below (opened by Notepad) (this file does not contain the text which should be translated) (Is it possible to make a *.mqxliff file from docx file in Studio 2015?)
    [GeneralSGMLSettings]
    CaseSensitive=Yes
    DTDSpecification=
    DTDSpecificationType=None
    DOCTYPE=xliff
    DescriptiveName=mqxliff
    [Tags]
    Tag1=mq:export-path:External,Group
    Tag2=mq:historical-unit:External,Group,Other Attributes:mq:minorversionend,mq:minorversionstart,mq:status,mq:segmentguid,mq:lastchangedtimestamp,mq:maxlengthchars,mq:nosplitjoin,mq:firstlabel,mq:lastlabel,mq:autosplitjoinstate,mq:lastmodifrole,mq:multipleexactmatch
    Tag3=mq:tagdefelement:External,Group,Other Attributes:name,placeholder
    Tag4=mq:tagdefattribute:External,Group,Other Attributes:name,filtered,required,translatable
    Tag5=mq:minorversions:External
    Tag6=context-group:External,Group
    Tag7=header:External
    Tag8=mq:nosplitjoins:External,Group
    Tag9=commitinfo:External,Other Attributes:matchrate,role,timestamp,username,editingtime
    Tag10=xliff:External,Other Attributes:version,xmlns,xmlns:mq,xmlns:xsi,xsi:schemaLocation
    Tag11=mq:details:External,Group,Other Attributes:mq:type
    Tag12=mq:lqamodel:External,Group
    Tag13=mq:docinformation:External,Group,Other Attributes:mq:isabstract,mq:hashistory,mq:docname,mq:majorversion,mq:minorversion,mq:nosplitjoin,mq:langindepgroupid,mq:multidocgroupid,mq:origfile
    Tag14=target:External,Other Attributes:xml:space
    Tag15=bpt:External,Group
    Tag16=mq:originalsource:External,Group,Other Attributes:edited
    Tag17=mq:startingws:External,Group,Other Attributes:xml:space
    Tag18=ept:External,Group
    Tag19=mq:minorversioninfo:External,Other Attributes:mq:minorversion,mq:comment,mq:createdthroughview,mq:createreason,mq:creationtime,mq:creatoruser,mq:tag
    Tag20=context:External,Group,Other Attributes:context-type
    Tag21=mq:versioninfos:External,Group,Other Attributes:mq:majorversion
    Tag22=file:External,Other Attributes:original,mq:id,source-language,target-language,datatype
    Tag23=tool:External,Other Attributes:tool-id,tool-name,tool-version,tool-company
    Tag24=mq:tagdefinition:External,Group,Other Attributes:alignhighlight,caseinsensitive,rawhtml,showitags,basicformat,supersubscript,xmlcommands
    Tag25=ph:External,Group
    Tag26=mq:endingws:External,Group,Other Attributes:xml:space
    Tag27=trans-unit:External,Other Attributes:id,mq:minorversionend,mq:minorversionstart,mq:status,mq:segmentguid,mq:lastchangedtimestamp,mq:maxlengthchars,mq:nosplitjoin,mq:firstlabel,mq:lastlabel,mq:autosplitjoinstate,mq:lastmodifrole,mq:multipleexactmatch,translate,mq:locked,mq:lastchanginguser
    Tag28=mq:doccomments:External,Group
    Tag29=x:Internal,Other Attributes:id
    Tag30=source:External,Other Attributes:xml:space,mq:segpart,mq:hasfollowingobject
    Tag31=mq:commitinfos:External,Group,Other Attributes:xmlns
    Tag32=body:External
    Tag33=--end--
  • 0 in reply to Asta GM
    You cannot create a mqxliff in Studio. MQXLIFF is native format of MemoQ. Studio uses SDLXLIFF.
    The ini file looks like it would have been created for Trados 2007 and earlier.
    What exactly is your job? Translate the DOCX file? And deliver MQXLIFF? If so, you MUST have MemoQ, otherwise you need someone to create the MQXLIFF from DOCX for you. You can also download a test version of MemoQ and do it on your own.
    But anyway - without MemoQ it won't work. You do not create a file by changing the file name extension, you need to use a proper tool to do so.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Jerzy Czopik
    Thanks a lot for Your help! Now everything is much clearer to me. Have a nice day!