Well, that's a big disappointment. I don't know what I was expecting from the MSFS Localization Manager but whatever we got wasn't it.
I was kind of hoping that it would use Bing to automatically fill in translations but no such luck. Maybe I was too optimistic with that.
As far as I can see neither of the export options (XML or Excel) work. The XML export generates files with only a couple of lines. The Excel export generates nothing.
The editor itself seems to be no quicker than copy and pasting in the .loc file directly. I suppose the only advantage is that the editor generates the GUID for you.
I have already written a spreadsheet which allows me to easily copy and paste a bunch of Google translations into it and then export a text file which, with a bit of find and replace in notepad++ produces a localisation file. I think I'll keep using that method.
I was kind of hoping that it would use Bing to automatically fill in translations but no such luck. Maybe I was too optimistic with that.
As far as I can see neither of the export options (XML or Excel) work. The XML export generates files with only a couple of lines. The Excel export generates nothing.
The editor itself seems to be no quicker than copy and pasting in the .loc file directly. I suppose the only advantage is that the editor generates the GUID for you.
I have already written a spreadsheet which allows me to easily copy and paste a bunch of Google translations into it and then export a text file which, with a bit of find and replace in notepad++ produces a localisation file. I think I'll keep using that method.