Hi jkn! :D
Thanks for your interest and questions!
I've translated/transliterated (not sure which is appropriate!) about 99%
myself manually, and I've used chatGPT for small parts (e.g. some regular
expressions, some small quirky methods) which I would estimate to be 1% of
the code. (anyways - from 2021 to early 2023 chatGPT did not even exist!)
Even then, the parts translated with AI had to be manually inspected and
tested. (I've played a lot with chatGPT translations from python to
typescript and it does not account for subtle details in some "almost
identical" native functions, which inevitably break the intended behavior)
In fact, the more important and subtle a detail is, the more likely it is
that AI will ignore it. (which may even compile and run in normal cases,
but break in edge/extreme cases)
For example, regex (Leo uses those a lot in critical places) have subtle
differences in the usage of 'flags' such as 'm' or 'g' in python vs
javascript, which will totally fail if not taken into account.
So it's really risky to use AI for translation. (if not thoroughly
inspected and tested)
About the 'upstream' work on Leo - I did the oldest, less likely to change
code first. Also, I have not done the importers yet, nor the unl support,
which happen to be re-written or changed in the last few weeks.... hehe !
For other stuff that changed, I try to keep up by collaborating with
Edward to change Leojs & match Leo's changes as quickly as possible, as to
not fall to much behind.
I look in the commit history and diffs with tools in gitlens (vscode
extension) to keep up with the changes and modify leojs as much as possible.
I usually work on implementing stuff for 2-3 weeks ,and then spend a week
to catch up with what was updated by Edward (if it happens to be on stuff
already in leojs).
Thanks for your support and curiosity! Best to you - Hope you'll be testing
& reporting bugs when I release the first beta in a few days (or weeks)! ;)
Félix
On Monday, June 26, 2023 at 10:09:17 AM UTC-4 jkn wrote:
> Hi Felix - something I've missed in the exciting mentions re. leojs here.
> Is the 'transliteration' done manually ('after coding for a few years'...)
> or via some (semi'?)-automated process?
>
> If the former, I'm wondering how 'upstream' work on Leo gets incorporated.
> If the latter, I'm curious about the process...
>
> Thanks & Regards, J^n
>
>
> On Sunday, June 25, 2023 at 7:47:30 PM UTC+1 Félix wrote:
>
>> Thanks Arjan!!
>>
>> Simple encouragements and feedback means a lot to me!
>>
>> Félix
>>
>> On Sunday, June 25, 2023 at 9:03:39 AM UTC-4 Arjan wrote:
>>
>>> > After coding for a few years
>>>
>>> Awesome perseverance. I've just continued using regular Leo because I'm
>>> used to the workflow, but I hope to find some time to play with the newer
>>> developments. Good luck!
>>>
>>> On Thursday, June 22, 2023 at 1:08:48 PM UTC+2 Edward K. Ream wrote:
>>>
>>>> > ...So anywhere from a week or two, or a month or two, hard to say,
>>>> but it's going to be this summer! :D
>>>>
>>>> Assuming vs-code allows it, I encourage you to release an alpha version
>>>> asap. There is nothing wrong with a list of known bugs.
>>>>
>>>> Edward
>>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/e5a888a6-326c-4f3b-aba9-233a5c78e9e9n%40googlegroups.com.
