Mr 2nl (aka HansL) once said: ‘CafeTran's handling of Transit's language pairs is even better than that of Transit itself. You might also want to ask over at the CafeTran mailing list: !forum/cafetranslators where there is at least one ‘certified’ (ex) Transit user/ specialist, who goes by the name ‘2nl’ here on Proz: As far as I know, CafeTran can handle Transit projects, including its resources (language pairs). You might want to have a look at CafeTran (which has a free trial version). If for some reason your source files time stamp is newer than the target files time stamp (perhaps working in different time zones?), please change the target files time stamp to the current date/time. We've seen cases were some of these files confuse Xbench when trying to detect language files.Ģ. ENG, delete them (make a copy of the folder first).
If there are more files in the folder than merely. To make it work with Xbench v2.9 (development is frozen for v2.9), please try the following:ġ. It makes the assumption that target files should be newer than source. Xbench v2.9 uses the date of files in the folder to decide which is source and which is target. Here it is, in case anyone else runs into the same difficulties: I wrote to Xbench and immediately received a friendly, very accurate reply. Since I'm using the free 2.9 version, I didn't think it would do much good to ask for support from Xbench, so I posted my question here.
Is there a way to command Xbench to use one language as the source the other as the target? How does Xbench decide which is which? Do I need to set an option in the Transit language pairs themselves? Any help would be greatly appreciated! When I subsequently open the TMX in Olifant, I can tell it to swap the source and target there, but this is additional work and I need to remember to do this every time. This only happens with some sets of language pairs. When the project opens, I can see it begin to read "ENG" files instead of "DEU" files. I have also tried making a copy of the project file (.xbp) and editing the path to the language pairs using a normal text editor, in order to make sure that I am not accidentally setting some other option or neglecting to set one when creating a project in the GUI. I have tried setting the option "Swap source and target" in the project settings, but this does not have any effect. I have each set of language pairs in a separate customer-specific folder.Īll sets of language pairs are German / English. For others, it swaps the source and target and I can't find a way to correct this. An option is available to spell check any WPF text box. Once you have copied the files, you will notice that next time you start ApSIC Xbench, an additional entry named Spellcheck appears in the Check Group box. zip file into ApSIC Xbench’s installation directory (typically, C:\Program Files\ApSIC\Xbench). An 'Ignore Spelling' directive can be added in file comments to ignore specific words within it. To install the spell-checking plug-in, simply extract the contents of the language’s. With some sets of language pairs, this works fine. Added a solution/project spell checking tool window that is capable of spell checking an entire solution, a single project, or any combination of items selected in the Solution Explorer window. It seems that Xbench automatically detects which is the source and which is the target. There doesn't seem to be an option to define these, when creating the Xbench project. I'm having trouble with the source/target languages in Xbench. Excel for Microsoft 365 Word for Microsoft 365 Outlook for Microsoft 365 PowerPoint for Microsoft 365 Access for Microsoft 365 OneNote for Microsoft 365 Project Online Desktop Client Publisher for Microsoft 365 Visio Plan 2 Word for Microsoft 365 for Mac Word for the web Excel 2021 Word 2021 Outlook 2021 PowerPoint 2021 Access 2021 Project Professional 2021 Project Standard 2021 Publisher 2021 Visio Professional 2021 Visio Standard 2021 OneNote 2021 Word 2021 for Mac Excel 2019 Word 2019 Outlook 2019 PowerPoint 2019 Access 2019 Project Professional 2019 Project Standard 2019 Publisher 2019 Visio Professional 2019 Visio Standard 2019 Word 2019 for Mac Excel 2016 Word 2016 Outlook 2016 PowerPoint 2016 Access 2016 OneNote 2016 Project Professional 2016 Project Standard 2016 Publisher 2016 Visio Professional 2016 Visio Standard 2016 Word 2016 for Mac Excel 2013 Word 2013 Outlook 2013 PowerPoint 2013 Access 2013 OneNote 2013 Project Professional 2013 Project Standard 2013 Publisher 2013 Visio Professional 2013 Visio 2013 Excel 2010 Word 2010 Outlook 2010 PowerPoint 2010 Access 2010 OneNote 2010 Project 2010 Project Standard 2010 Publisher 2010 Visio 2010 Visio Standard 2010 Office 2010 Excel 2007 Word 2007 Outlook 2007 PowerPoint 2007 Access 2007 Project 2007 Publisher 2007 Visio 2007 More.I'm trying to convert Transit XV language pairs into a TMX file with Xbench 2.9.
0 kommentar(er)
