mirror of
https://git.huckle.dev/Huckles-Minecraft-Archive/jpexs-decompiler.git
synced 2026-09-25 00:50:51 +00:00
Merge branch 'master' of https://github.com/jindrapetrik/jpexs-decompiler
This commit is contained in:
@@ -0,0 +1,36 @@
|
||||
# FFDec Frequently asked questions (FAQ)
|
||||
|
||||
## "Invalid SWF file, wrong signature" on opening file with .swf extension, what's that?
|
||||
This message means that you are opening file which is not really the SWF. FFDec can process only valid SWF files - those which can be played in Flash player. SWF file extension is not enough - also file structure must be compliant
|
||||
with SWF standard - it needs to start with FWS, CWS or ZWS bytes. If you are 100% sure there is something SWF related inside your file, then it probably needs some kind of
|
||||
decryption/unpacking routine first. Go where you got the file and search for an unpacking routine (loader), maybe you find something. FFDec cannot help you with this since decryption
|
||||
routine can be literally anything.
|
||||
|
||||
## Can I add new scripts? Or classes?
|
||||
No, this feature is not implemented, sorry. Editing is limited to existing scripts or classes.
|
||||
|
||||
## Direct editation of ActionScript gives me an error, what can I do?
|
||||
Direct editation of AS is experimental and in most cases not even working - it might damage your SWF file. We won't fix that, sorry.
|
||||
|
||||
## Can you implement new feature for me?
|
||||
No, we no longer work on the decompiler. But decompiler is opensource, you can implement feature yourself.
|
||||
|
||||
## But there are bugs, you will surely fix that
|
||||
No, sorry, we no longer fix any bugs. Ask somebody else.
|
||||
|
||||
## Is there a documentation for FFDec library?
|
||||
No, there isn't one.
|
||||
|
||||
## What's that thing with § character in scripts?
|
||||
A) Variable identifiers which have invalid characters in their name are displayed in the form `§name§` (for example `§s-r/rg§` ).
|
||||
This allows easier direct editation.
|
||||
|
||||
B) Also, there exist few special instructions/functions with prefix §§:
|
||||
- `§§push(item)` - pushes item on stack
|
||||
- `§§pop()` - pops from stack
|
||||
- `§§dup()` - duplicates value on stack
|
||||
- `§§goto(label)` - jump to address
|
||||
- `§§constant(number)` - unresolved constant (unknown constantpool)
|
||||
|
||||
These functions usually pop out when you try to decompile some obfuscated / unstructured code.
|
||||
You can try Settings/Automatic deobfuscation option for handle some kinds of this code properly.
|
||||
@@ -130,16 +130,17 @@ The application was made in Czech republic.
|
||||
* **Rtsjx** - chinese translation
|
||||
|
||||
## Contact
|
||||
### Issue Tracker
|
||||
For bug reporting and/or feature requests, our own Issue tracker exists :
|
||||
[https://www.free-decompiler.com/flash/issues](https://www.free-decompiler.com/flash/issues),
|
||||
but as of 2018/01, our support is *very limited*.
|
||||
Note that the decompiler is ABANDONED. We do not provide support of any kind.
|
||||
You might look for some answers to the old issues in our issue tracker on
|
||||
[https://www.free-decompiler.com/flash/issues](https://www.free-decompiler.com/flash/issues)
|
||||
But it's currently read only.
|
||||
|
||||
See [Frequently Asked Questions (FAQ)](FAQ.md) before you try to contact me.
|
||||
|
||||
### Email contact
|
||||
**Please contact us via Issue Tracker (see above)**
|
||||
|
||||
In case the tracker or *free-decompiler.com* domain is down,
|
||||
emergency contact to JPEXS developer is `[email protected]`.
|
||||
Emergency contact to JPEXS developer is `[email protected]`.
|
||||
But as stated previously, the development has stopped so there's no way
|
||||
for asking for new featureas and or fix bugs.
|
||||
|
||||
## Licenses + Acknowledgments
|
||||
### Application
|
||||
|
||||
+2
-7
@@ -26,7 +26,6 @@ If you would like to translate FFDec to your language, please follow these steps
|
||||
1. Check whether your language is not already present in the development branch:
|
||||
[dev/TRANSLATIONS.md](https://github.com/jindrapetrik/jpexs-decompiler/blob/dev/TRANSLATIONS.md)
|
||||
2. Find out your language code (See [table](http://www.loc.gov/standards/iso639-2/php/code_list.php) )
|
||||
3. Create new issue in [issue tracker](https://www.free-decompiler.com/flash/issues/) containing your new language name + code. (You should register first)
|
||||
4. Download `Language pack for translators (zipped)` from latest (including nightly) version on [releases page](https://github.com/jindrapetrik/jpexs-decompiler/releases)
|
||||
5. The archive contains all language files for newest version of FFDec. Each language in this pack has files with its own suffix which is standard language code.
|
||||
6. Extract Language pack ZIP file
|
||||
@@ -34,9 +33,5 @@ If you would like to translate FFDec to your language, please follow these steps
|
||||
8. Open `.properties` files with an editor. (`.properties` editor bundled with some Java IDE is better than standard text editor)
|
||||
9. In order to `.properties` to work in FFDec, all nonascii characters should be replaced with unicode escapes (like `\u1234`). IDE editors like Netbeans do this automatically. If you have classic text editor, you can skip this phase, I will do it later myself.
|
||||
10. Don't forget to place your name in `AboutDialog_xx.properties` file.
|
||||
11. Attach translated files to that issue.
|
||||
12. Goto [Issue #354] and look for new translated strings.
|
||||
12. Subscribe to [Issue #354] to be notified about new strings in the future.
|
||||
13. Wait for next release where your translation will be included.
|
||||
|
||||
[Issue #354]: https://www.free-decompiler.com/flash/issues/354-new-translations
|
||||
11. Create branch from `dev` and place .properties files to correct locations. TODO: specify what's correct location
|
||||
12. Create pull request
|
||||
|
||||
Reference in New Issue
Block a user