18,700
edits
User talk:Paradox-01/Archive1: Difference between revisions
→OniSplit source code: current thoughts on this subject
Paradox-01 (talk | contribs) mNo edit summary |
(→OniSplit source code: current thoughts on this subject) |
||
| Line 24: | Line 24: | ||
:I said that he might rewrite OniSplit for .NET Core because he told me so :-) I think I have contact info for him, so I'll ask him about the state of OniSplit and a possible source release. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 22:18, 24 August 2016 (CEST) | :I said that he might rewrite OniSplit for .NET Core because he told me so :-) I think I have contact info for him, so I'll ask him about the state of OniSplit and a possible source release. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 22:18, 24 August 2016 (CEST) | ||
::Sadly, since I have been unable to contact Neo, decompilation is looking like a more relevant option lately. I will write details about this in a more central location in the future, but I am thinking of porting OniSplit's features to C. The conversion code in OniSplit (-create/-extract) is what's really valuable -- the splitting part (-import/-export) should be trivial to re-create -- so for the really technical parts of Neo's code that none of us understand at the moment, we may need to start just dumping in functions composed of OniSplit's decompiled C#, ported to C or C++, and then make sense of those chunks of code in the future, pecking away at them over time. Initially, at least, we won't need to understand them as long as they produce the right results, and over time we can add comments and apply better symbol names if the originals get lost in the process. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 17:00, 4 May 2017 (CEST) | |||
==Translations issues== | ==Translations issues== | ||