Test data for your Regex Assistant library?
A modest proposal and some worrisome news.
![May be an image of text that says "3 4 6 7 8 9 10 <? ?xml version="1. 0" encoding="UTF-8?>LE encoding= <rxb regexbuddy xmlns: http:/wwaf.febeo./e. xsd" version="4 .14" <libraryfile>LE <action id-"Nonbreakingapacefornunbe <flavor> LF Qbuiltin>csharp20k/builtin> </flavor>LE <regex> (1d+) lu0020? [cdkmnpp] ?m) </ regex> LE <replace>$1NBSP$2</replace> LE <description>Non-bzeakin -breaking space for number (s) + units</description> LE <teststring><! <teststring><!(CDATA(55.m [CDATA[55 mmLE purpose="replace" namedduplicate="1"> licate="1" 13 15 16 17 2nmLE 6NBSPcmLE 2-umLE -11></teststring> </action> </libraryfile>LE :regexbuddy> 19"](https://substackcdn.com/image/fetch/$s_!bVWG!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F15a4f7a4-2981-4a7a-b3ab-ecaeaed248c5_1027x385.jpeg "May be an image of text that says \"3 4 6 7 8 9 10 <? ?xml version=\"1. 0\" encoding=\"UTF-8?>LE encoding= <rxb regexbuddy xmlns: http:/wwaf.febeo./e. xsd\" version=\"4 .14\" <libraryfile>LE <action id-\"Nonbreakingapacefornunbe <flavor> LF Qbuiltin>csharp20k/builtin> </flavor>LE <regex> (1d+) lu0020? [cdkmnpp] ?m) </ regex> LE <replace>$1NBSP$2</replace> LE <description>Non-bzeakin -breaking space for number (s) + units</description> LE <teststring><! <teststring><!(CDATA(55.m [CDATA[55 mmLE purpose=\"replace\" namedduplicate=\"1\"> licate=\"1\" 13 15 16 17 2nmLE 6NBSPcmLE 2-umLE -11></teststring> </action> </libraryfile>LE :regexbuddy> 19\"")
I just added a suggestion on the memoQ Ideas Portal for which I would appreciate support. It involves adding test data to regex records in the memoQ Regex Assistant libraries.
https://ideas.memoq.com/ideas/PUBL-I-1222
The RegexBuddy tool does this, and it's really very useful for showing how a regular expression works. Having that features in the memoQ Regex Assistant would reduce the number of test data files I have to juggle and pass around.
Lately I have been looking at more ways to exchange valuable information and resources held by memoQ users with other environments for translation or writing where we might need to use them. I think the latest statements from the company about the desktop editions as a dead end with no real indication of how any value and control might be preserved for us after they drift off into Webland make such efforts all the more important.
I'll be covering topics like this more in the future, as I have little information at this point which inspires any optimism. Until that happens I just hope nobody - no individual, no company - asks me for any translation environment recommendations, because I don't know what I could honestly say.
If these memoQ development plans work out to some advantage for individual service providers and the boutique brokers I typically support, great. Deeper studies and updates of my past suggestions for interoperable workflows will just contribute to better integration with whatever partners they have with whatever working tools.
If things go in a less encouraging direction, then knowledge about salvaging and recycling our investments in tools, data, corpora, configurations and whatnot shall become critically important.
Either way, I’ll do whatever I can to help the individuals and companies deserving support.
I just read about this "development" earlier today. Having invested 17 years (and the corresponding amount of $$$ in licences and support agreements) in memoQ as a desktop client, to say that I'm less than thrilled about the prospect of the application being effectively deprecated is a gross understatement.
I haven't used any web-based translation environment for many years, but my hunch is that such an environmentally will inevitably come with constraints that don't apply to a desktop client. I'd also bet heavily on memoQ charging a monthly subscription that works out substantially more expensive than the annual fee I currently pay to keep my support agreement up to date.
The future does not look rosy.