Soly's Stash

Matt said:
I'm best cmd user.

Did the original file (with -- instructions) also use single dash? I always kept just getting the instructions no matter what I typed (even if I tried to convert without batch method), even if it was "unitxt --prs2json C:\unitxt.prs" or whatever.
Click to expand...
The original used double dash, because it came from a -shortoption vs --longoption kinda thing.
But I removed the short options.... The help now should show single dash in it.

I just tried and it worked for me
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\Soleil>unitxt -json2prs E:\unitxt.json
Processed E:\unitxt.json

C:\Users\Soleil>unitxt -prs2json E:\unitxt.prs
Processed E:\unitxt.prs

C:\Users\Soleil>
 
Yeah, your new version works perfectly for me now, can batch and process normally, thanks!
 
Yay, a new version of the unitxt tool!!
Just what everybody was waiting for.

Jokes aside, this last iteration (ugh) of the unitxt tool was made to merge all language files in one.
I don't know if this will end up being a good idea, but at least the code I wrote for this will let me separate them back into different files if required.

The 2 main reasons for doing this, are:
1) I need some nice library for Aselia, to manage the unitxt in different languages (part of multi language support stuff here).

2) All languages for a single string will be in back to back, so if you add or remove strings you literally can't break or desync it from the rest of languages (you can break it if you manually remove a string translation, use the -remove option if you want to remove a language).

I didn't extensively test the tool but I did create my new unitxt.json file with 7 languages so it should be working.

The help output of the program should be enough to get started.
 
Added vanilla unitxt(shop) files to a github repo, you can find links in the first post.

All translators agreed to share their work (not that you couldn't just steal it from other servers anyway) with exception of Univers-PS, I don't know who made the files but was told by members that could be used just fine.

The files, afaik, don't have any hidden branding but they might still have some Ultima stuff (I removed what I could), if you find anything weird/wrong, let me know.
 
And... I'm already thinking of going back to what I had before, still keeping the new code as I suggested in one of these replies...
For this I'll probably end up coding a new graphical tool to edit multiple files at once tho... so it might not happen soon.
 
And back to single language per file.
I'll add a GUI program sometime in the future.

You might need to re-export your json unitxt files as I have removed some parts of the json structure and it probably wont work with the latest build.
 
Hi Soly, the only pr2/pr3 pair of files I found on PSO1&2+ for GC disc for English language is TextEnglish.pr2 / pr3 but not all strings seem to be in the JSON file when extracting them with your tool ? I think I'm missing Item Names mostly. Are they contained in a different file or something ?

(using latest build as of april 25)
 
No, the item names get extracted into the JSON just fine. They're the first group of strings. It's possible the PSO+ file could have some subtle difference that's breaking the tool, though. I haven't tried to parse Plus files yet. :o
 
Well, I don't know 100% how the file is structured, so it's possible that it's not reading certain strings...
I have to yet figure out how the file keeps a string count.
If it's by pointers, like, once a group starts, I stop reading from the previous one or if it in fact has some string count for each group which is highly unlikely since there are no numbers related to that.
I might go and look back to those files to try and make some sense of them, maybe try to see what PSOPC does with it.
 
I'd like to request a feature for your itemPMT / PT / RT editors : Export data to CSV (Comma-Separated-Value) with value names as first entry of each datatype or something like that so that we have a reference and don't have to copy your app's column names... ^^"
Please give it a thought :)

(Wouldn't it be great to have a quick way of grabbing PSO GC data in a sure-fire way for instance ? If anything for conservation purposes)
 
Last edited:
I did before but I dropped it.
I'll think of it once I make some libraries I need for my server (so I can reuse the same code without duplicating it).

@Fire AKA Drazn needs that too so we'll see once I get to that.

The main goal is to use JSON tho, so depending on how it ends up being the json stuff, I might not add csv.
 
Last edited:
JSON rocks, it seems pretty flexible and there are libraries to parse it so it's all good ^_ ^

By the way, is ultima forums the only place to read about your progress on your server software ? I sometimes check there what you add / fix, you don't have a blog do you ?
(not asking for a repository link or read-access btw)
 
Indeed, that's the reason why I am using it, might not be the best for some of the files but who cares...

Yeah, only there, and is not everything cuz I'm too lazy to write it all up.
Even then, the code is not in a public repo (as it says in the github repo) and neither would give any access to it atm.
 
oh yeah about the "problem" I had extracting strings from TextEnglish (GC) and finding rare item names, I was using your PSO Console Text tool actually as the Unitxt GC link is dead. Not sure if it makes any difference... And yes it is my PSOPlus files I'm attempting to extract from.

I wanted to try out if I could "sanitize" some item names / descriptions so as to be able to differenciate AGITO and FLOWEN SWORD versions for instance :)
 
Last edited:
There is no more "unitxt gc" actually, it's now PSO Console Text since it attempts to work with XB/GC/DC.
Maybe I should change the name in the first post, I fixed the link but it still goes to my PSO Tools repo anyway.
 
You must log in or register to reply here.
Back
Top