Goldug
-
Posts
17 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by Goldug
-
-
On 2/20/2018 at 6:14 PM, Jason Carr said:
Converting to Excel files doesn't sound like it would help unless it can go the other way (convert from Excel back into resx). Ultimately, it's the resx files that the app uses so that has to be the end result. Conversions do scare me a little since we have run into problems in the past with extra entries in the resx files, etc. So if you do find a new way to do it, it would probably be best to test it with one file before proceeding with the rest.
Yes of course I only try it one file at a time
And Zeta have the option to convert to excel and back from excel. I don't really know exactly what it does though, if it keeps all the info back and forth. I'm gonna look at the file in notepad++ before and after, just to see what really happens
-
1
-
-
1 hour ago, Opak said:
Or you just do it the old fashion way, without experiments
Yeah, but what's the fun in that?
-
13 hours ago, Jason Carr said:
Yeah, do be careful, because the last thing we want is to end up with a complete translation that we can't use. The important thing is that it ends up in the correct .resx format.
Uh-huh. I experimented a bit and found some interesting ways to do it. One of them worked very well when it comes to translating .resx files, but it couldn't export into .resx for some reason...
Another method involved converting .resx to .pot files and then back again. However, without a template-file for the translation files it includes everything, along with garbage (the first line in the converted file was "Bottom")... But it would be awesome to have/create a template-file first. Don't have the time/energy for it though.
Edit: I just noticed that Zeta can convert to excel-files. I wonder if that would help?
-
Just a little update: I haven't really started translating yet, been a bit busy with IRL stuff, but I'm gonna get going soon.
I just thought it would be a good idea for me to post updates a little now and then, seeing how the last translator disappeared without a trace.Oh and BTW, I might look into another app for translating, but it's for Linux. Don't know if it'll work though, so I'll always load the finished translations in Zeta just to be sure you can open them too
The Linux distribution is called Tuxtrans. It's a Ubuntu-based dist aimed at translators. It comes fully loaded with all kinds of translation tools and apps that you could ever use, so you don't have to be a linux wiz to use it either
-
1 hour ago, Opak said:
@Goldug The best way is to start Zeta Resource Editor, then click "Open Resource Files". There you highlight the (for example) Strings.resx and the Strings.sw-SW.resx and open them.
Then your screen should look like this:
Then you just need to type in the translation in the swedish column. You can leave the line empty if the text doesn't need to be translated.
If you're finished, hit the "Save all files" button at the top, close the files and go on to the next files.
I hope i could help you a bit.
Yeah I have no real problem with that part, but it's the spell-check thing I mentioned that's a problem.
Thanks though ?
-
Okay. It's for the best anyway, it's better if there's just one or two translators to keep a consistent language. Like when choosing what to translate "Close" to for example. I can choose either "Stäng" or "Avsluta". They both mean kind of the same thing.
However, I've noticed that Zeta isn't really that awesome... for one thing, it cannot find my Swedish dictionary files, even though I've put them in the correct folder and named them in every way possible. The only thing that works is to name my Swedish dictionary en_US, thus replacing the English dictionary, which feels dumb.
And Zeta has close to zero support too... But I'll try my best to work with it
-
1
-
-
21 hours ago, Lordmonkus said:
Version 8.0 - Released February 14, 2018
- Fixed: Valve/Steam decided to kill our API Key for no apparent reason (or at least none that we received any communication about), which broke the Steam import wizard. This has been fixed with a new API key. Hopefully they don't kill this one...
First of all: yaay!
Second: I was thinking, do you think they killed it because all of us were using it, so they thought it was used too much? Like they thought it was a malware/pirate attack?
-
23 hours ago, Jason Carr said:
Okay! Hit me up with the files to be translated, the ones in the OP seems to be a bit broken for me (the Swedish files). Unless he actually didn't translate anything, in which case I'll just start from scratch.
-
Yeah I agree, the tapatalk issue is a bit annoying. I've recently started using tapatalk for a few other forums as well, and I love it. I was really sad to see that it didn't work here now.
I only get a message saying something "network error (sign_in | LaunchBox Forum)"...
-
It seems that @Izzy hasn't translated a lot to Swedish, or am I wrong here? I took a look at the Swedish translation linked in the OP and... well the "translated" files are all 5Kb and empty. Completely empty.
So I could gladly take over the Swedish translation. I've translated several apps before and I don't have much of anything else to do these days
-
2 minutes ago, Jason Carr said:
The issue was caused by a glitch in the latest version of our deployment system, believe it or not. It had nothing to do with the LaunchBox code lol.
Haha, yeah those things happen sometimes I guess
Some more good news: I can finally import my Steam games!
-
2
-
-
17 minutes ago, Jason Carr said:
Beta 10 is out now guys; please let me know if it fixes it for you. If you're unable to update it normally because of the crashes, you can download the latest beta from the link below and manually install over top:
Yep, seems to work now. It took a long time getting through initializing though, even though it didn't seem to use any disk activity or cpu really, just 18mb ram. What was the fix? I'm really curious. If you don't want to share that info with us, that's okay
-
1
-
-
9 minutes ago, CDBlue said:
Hmm, isn't the latest release version of Windows 10 v.1709 build 16299.192? Maybe that's the issue, if windows isn't up to date, maybe a needed file for LB/BB (.net maybe?) is also out of date and causing the crash?
I really doubt that's the issue since .net has nothing to do really with what version of Windows 10 you're using.
However, I've tried updating to the latest Windows build with no luck. I've done everything except a complete re-install and it still won't work. I've even been in contact with Microsoft who can't figure out what the h* is going on... -
I just ran SimpleProgramDebugger on LaunchBox.exe and got some errors.
I've attached the logs, one is the first error only, the second (larger) file is a bit more detailed, and the third html-file is a lot more readable. Don't know what you prefer to read
It seems to occur right after loading C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll though.launchbox SimpleProgramDebugger.txt
-
14 minutes ago, Jason Carr said:
@Goldug Are you running Windows 7?
No, I'm on Windows 10 v.1703 build 15063.877.
-
I was literally just about to post the same thing.
I kind of need the beta too since steam importing isn't working in v7.16.
I however do not have any beta-8 exe file to fall back on since I installed LaunchBox yesterday for the first time...I have turned on debugging in the settings.xml file, but beta-9 doesn't even get far enough to create a debug file.
Translating LaunchBox
in Features
Posted
Hey.
Just a little update on the Swedish translation: it's not going fast due to some IRL problems that popped up recently. I'm translating a little now and then when I have the chance though.
Just so you know.