![]() “With projects that take advantage of memoQ’s TM, the connector will solve for the first time two recurrent but different problems: string status tracking and strings recycling. Working around multibyte IDs will no longer be necessary and this will allow for even more seamless integrations of source files without additional customer work.Ĭarlos Garcia-Shelton, Product Manager at XLOC, commentated: Increased support for String IDs (RSID), filenames and usernames containing multibyte characters. With the new connector, once the memoQ and XLOC projects have been linked, at the touch of a button, asset strings will move directly from XLOC to memoQ for translation and back to XLOC once translated, without the need for manual exports and imports, saving time and bringing more autonomy and streamlining to the workflow.ĭevelopment teams can push assets into the translation workflow with a click of a button and seamlessly retrieve the translated assets into the central XLOC repository, ready for integration and testing.Īdditional Key features of the XLOC 6.5 update include:Įnhancement of the QA “Suggested Translation” feature, allowing for quicker edits and helping prevent copy and paste errorsĪ more user-friendly experience with new advanced search features, file drag-and-drop functionality and ‘upload image’ capabilityĪdditional end user autonomy thanks to new ‘Supervisor’ user permissions ![]() ![]() The feature is being rolled out for all users as part of a major update for XLOC. The new ‘Connector’ for memoQ, the popular computer-aided translation tool, has been created to help streamline the localization workflow for global video games publishers and developers. It enables game developers and publishers to more efficiently manage and automate the process of localizing games content across multiple languages and platforms for simultaneous global launches and continuous publishing. Its proprietary software application can be integrated with any games development platform. If mouse.Founded in 2004 and acquired by Keywords Studios in 2017, XLOC has developed the leading web-based integrated globalisation content management system for video games (XLOC), supported by consulting and customisation services. If 0 not in obs_dict.values() and 1 not in obs_dict.values():Įnd routine: if mouse.x in range(xloc-150, xloc+150): SkipThisTrial = True # variable to use in feedback etcĬontinueRoutine = False # end this routine I was in the process of changing the code to make it translate to java and jon sent this suggestion: Notice I only removed the indexing 0 and 1 from xloc and yloc, not from the mouse.x or mouse.y. Then I think the only thing you should need to change is : if mouse.x in range(xloc-150, xloc+150): So assuming xloc and yloc are being defined correctly (and I think they are using the xloc = trials.thisTrial You had to use the 0 and 1 to index loc originally, because loc used to be a vector or a series of numbers, so you needed to pick out the first and second component of this (this is what the 0 and 1 are doing).īut now that you have xloc and yloc already defined as single numbers, you shouldn’t need to “pick out” or index any values from them, just use those variable names exactly as they are. I think the issue comes from doing xloc and yloc. Hi Tom, I think your method of defining xloc and yloc is totally fine, but a way to test this is just to insert some easy code/component in that might print out the values of xloc and yloc on each trial to confirm they are defined correctly.
0 Comments
Leave a Reply. |