Multi-Language Version (English) #1255
Comments
|
The English version is being developed and scheduled. If you are interested, I hope you can contact me to talk about the common needs of international friends. |
|
of course, any help I can contribute in |
|
of course |
|
https://github.com/ip-rw/translate_code It's a little scrappy in places (Google translate likes to mix things up...) but as the number of Chinese people posting (some) really good code has exploded, I use it more and more. find -type f | grep 'go:' | python3 translate.py --proxy [some suitable proxy] --threads 10 YMMV, the Yakit build process I find punishing enough as it but once that was working the translation itself went without a hitch, save 5 mins worth of manual fixes. I will build one now and upload an AppImage. I will push OpenAI integration today, it doesn't appear to suffer from Google's quirks so you could do it in about 10 lines... |
|
The multilingual version needs to convert 'data' into 'i18n variables.' This requires developers to do it when the functionality is stable and they are not busy. Some internationalization operations can make drastic changes in feature development look strange. BTW, if u just want to build a pure English version for yourself, translating via some utils (metioned: translate_code) is pratical way. XD |
|
Pls share strings |
|
https://github.com/ip-rw/yakit_english I revisited this and threw my translator at it, how much of it still works remains to be seen but it IS very pretty and enlightening to see it in my own language :) You can download binaries (AppImage and untested exe) here: The source should compile without modification. I think I used node 18 but not sure. |
|
i18n is planned. During recent major component coding and optimization, there may be a synchronized effort to begin implementing "translation work" for some simple yet crucial pages. Translation is a task that requires developers' dedication, (as the workload lies not only in translating the content, considering I can also proficiently read and write English) but also in maintaining consistent and aesthetically pleasing styling when text changes. Users will be able to find a language switch button either in the global settings or in the "top-left/top-right" corner. Additionally, certain online resources (CDNs) need to ensure effectiveness for international users. Keep an eye on the status of this issue. If the i18n work begins, we will sync here. The strings will be placed in the source code, and those interested can help us improve the i18n work. |
|
For sure, this is just designed to let the less multilingual (like me) see the thing in context, because it's really cool. The chances of it working in any meaningful way are remarkably small. IIRC there a some parts of Yaklang itself that will need tweaking (but very very few), and I've not done that (although on a previous attempt I was able to get things basically working). I noticed this time the results were visually much more appealing and the translations didn't perturb the flow much at all - it's clear an effort has been made to prepare the application for i18n, particularly with the critical things like images. Yak itself is really the main event for me (and for all intents and purposes requires no translation), it would be wonderful to see a larger ecosystem start to evolve but for the time being Yakit is really the only practical example we have (though I've not looked in some months tbh). Once Yak reaches a wider audience and maybe a few examples of just how much cool stuff can be done with this thing without developing a Yakit I really can see it catching on in a big way. I'm surprised it's not already being utilized by the zillion different scanners out there by other Chinese authors. Yak has a beautiful codebase. The quality is superb, and (looks) totally original - so much so that you really do start to think "should I copy this? would it be easier to embed Yak?" The majority of what got translated were comments (kudos)... while plugins and user generated content would of course be nice to localize, one must be realistic and I can't think of any nice way to do this...the thing really isn't that far away (tsx upsets me greatly allowing unquoted quoting literals if they dont contain spaces, at times its distressing stuff) |
|
Actually, I am (personally) glad to hear some evaluations of the yaklang code repository itself; indeed, we have spent a significant amount of time building a comprehensive infra system for the development of security tools. As a developer and also a security professional, I deeply understand that many libraries and tools are designed with development in mind, and often do not adapt well to security capabilities. The implementation of the two high-frequency core modules in yaklang, lowhttp and mutate, really reflects this issue. Additionally, the mutate library’s operations on HTTP fuzz testing, packet transformation, and fuzztag are indeed hard to find similar implementations elsewhere. However, as you can see, the source code is obscure, especially the parts about the VM and the analysis of compiler extensions, which not only require a basic understanding of coding but also some knowledge of compiler theory. This might be a reason why people are reluctant to read the source code. (Personally, I would recommend looking into SSA-related technologies, which are excellent compiler practices disguised as ‘security domain’ techniques.) In fact, Yakit is used for tens of thousands of hours almost every working day, with users constantly validating Yaklang’s technical architecture and helping us refine the details of the yaklang core engine. Although other language communities are not very active, optimizations of technical details and engine bug fixes are not constrained by the user’s language. In recent versions, we have introduced AI assistance, and regarding the general English interpretation of plugins, this task can also be undertaken by AI, as language differences are not a barrier in this era. Yakit’s ‘Hot-Patch’ feature can be combined with Yaklang’s code completion to allow users to directly execute any Yaklang script to control the details of communication behavior during packet hijacking or replay. Users of this feature are generally advanced users of Yaklang. |
|
I've taken a very amateur interest in embedded langs for quite some time (I won't profess to know more about Yak than finding it exciting and have looked over the stdlib... there is a lot of original and unique stuff in thee) - it's already bridged the gap that would stop most people with an interest in security DSLs/langs from actually implementing something practical in their applications. Yakkit is a whole other thing :) one step at a time, there's a LOT there to take in...the maturity is what really comes across and yet had I not been looking for embedded security DSLs/langs I'd have never have encountered it! As I said, the work done in a month or so on i18n UI preparation alone is very visible 👍 Both are very cool projects - and unique. |
One could have some fun with these concepts. It's not a defensive framework is it ) but i love that it's not another boring C2 - this is way more interesting |
|
hello any progress here ? |
|
I am as well inquiring about the progress of yakit in an English or international translated release. It is easy to imagine my surprise and confusion, opening up yakit for the first time on a remote computer to not see a single character I was familiar with. |
Hello guys, I assume many have already asked this question!
is there an English version file for this program ?
sry to post it on Issue section
The text was updated successfully, but these errors were encountered: