Show HN: FlyCode – Git-Based Copy and Translations Editor for Web Apps

Re:Show HN: FlyCode – Git-Based Copy and Translations Editor... by Existenceblinks on Tuesday April 26, 2022 @01:03PM (#31170006)

A lot of green username here. Well, I'm building the same kind of product! If it's not javascript based, I'd immediately apply for the job. Not sure how the code scanning would evolve as projects evolve? Is FlyCode tracking the dynamic content holes, as the place it was currently edited would be moved around? There are other aspects I wonder for this approach.

[ Parent | on HN ]

Re:Show HN: FlyCode – Git-Based Copy and Translations Editor... by peekypeeky008 on Tuesday April 26, 2022 @01:15PM (#31170215)

Thanks for the feedback. We hire devs based on talent not language so feel free to apply. FlyCode is able to identify changes made in a commit and identify a text is the same according to the semantic structure of the code but of course it is not 100%. In many cases though texts stay in about the same place and when moved they change their meaning and should be treated differently

[ Parent | on HN ]

Re:Show HN: FlyCode – Git-Based Copy and Translations Editor... by Existenceblinks on Tuesday April 26, 2022 @01:40PM (#31170555)

I found some clue on the docs' TEXTS section.

> if the format is hardcoded, the name of the component in which the text resides would be the title

So it's component based tracking, though inside-component is hard to form context (e.g. line/column tracking won't work) even if you have AST of javascript. When code changes, AST changes (tree nodes tracking won't work either).

Interesting approach not to use hole like `{{ }}`.

[ Parent | on HN ]

Re:Show HN: FlyCode – Git-Based Copy and Translations Editor... by JakeVacovec on Tuesday April 26, 2022 @01:29PM (#31170403)

Btw - awesome to hear you're building a product in the same space. Happy to collaborate and exchange notes! jake[at]flycode.com

[ Parent | on HN ]