If only people would use this phrase more often instead of “it’s impossible”. Recently I’ve heard that it’s impossible to export LQA settings from memoQ server via API. And I’ll use this post to explain it’s not true. Plus, I believe it would be interesting to get familiar with a bit broken format of mqres file. Which is an XML, like most things in memoQ’s world. We’ll start by downloading the settings.
I have a personal git server for several years now, but I’ve used GitHub for “brag” code. It was easier, GH is well known and I could even collaborate with others from time to time. However, recently GH has, not blocked me as I could still manage my repos and commit code, but flagged my account. Which means it was not visible to the public. There was no email notification about it.
My first computer was Atari 65 XE. We’ve bought it from some friend of my uncle. I’ve received it with lots of games and quite a collection of computer magazines and literature. These were the days when your magazine printed full code listings which you could then type into your computer and have a working program, or a game. It was usually in Basic. I’ve never did it. I was about 10 then.
JSON files shouldn’t contain a lot of data, but sometimes they do. Recently I’ve received huge JSON file. It consisted of more than 100k lines and had more than 300 unique keys (attributes if you will). In memoQ you can create a filter for JSON files and then you can define which keys should be translated. You need to add your JSON to the filter and then populate the list of keys, then you can edit this list either in flat or structural view.
As per memoQ’s help page this is what causes your Translation Memory to store duplicated translations: Translation memory may have duplicate entries after the import: This happens if the translation memory allows multiple translation for each source segment, or when the translation memory uses double context. In the latter case, you may want to remove the duplicates because the context is not relevant. To get rid of duplicate entries, open the translation memory for editing.
Another year and another adventure. AoC doesn’t disappoint. It somehow was better for me this year, even though I’ve got lower score. It’ll sound as an excuse, and maybe it is, but I’ve started new job in December. So, I couldn’t spent whole day dealing with the problems, as I had to focus on my new role. And this was actually a good thing. Yes, I’ve gained less stars. But, I wasn’t spending a lot of time poking around, and basically running circles.
Somebody has shared this image with me as supposedly funny. But I completely agree. I have very little time to play video games. And I practically only play Souls games. Why? Because you can do a lot in 15 minutes. You can approach a boss at least three times, and even defeat him. You can complete entire stage and get all the loot. You can farm. I’ve bought Red Dead Redemption 2 recently and oh boy.
Recently we’ve had some huge Translation Memory to cleanup. It was built by copying segments from two other TMs, so it was a mess. It had over million segments and we needed to shrink it. So the obvious thing to do was to get rid of duplicates. Unfortunately our CAT tool isn’t very good at it, or rather very fast. But we can export/import TM in TMX format which is basically an XML.
When I want to contribute to some repository on GitHub I always check Issues section first. And this is how I’ve started with the repo I’ll discuss in this post. I’ve found an improvement request and wanted to implement it. First I’ve learnt how to do that, as I’ve not done it before. And then I’ve started to analyse the code in order to add this new feature, as I’ve only glanced at it before.
After Advent of Code has ended I’ve started looking for another challenge and found weirdtext. It’s a recruitment test, but as I’ve found it quite interesting I’ve decided to do it and have coded it in Go. To make initial version of encoder and decoder was quite easy, but then I’ve started to add other cases to my tests and made some improvements, and also fixed some bugs. I’m not big fan of TDD, but I’m fanboy of unit tests.