LinguaNow

some of yallasked hows it so fast, well its a collection of many things

1 theres 2 google translate api providers and s couple more which are usually dead. So, i batch each api with 50 parallel requests per provider so its 100 for each.
other than this, it sends it paragraph by paragraph with the previous paragraph as context so theres no quality drop.
also, a semantic matcher saves usual phrases in sqlite and runs a separate instance for it.

other than this, if any paragraph fails, it fallsback to the local dictionary on system for it.
when all of this is done,

it stores every sigle coordinate of each paragraph and table and formatting and rebuilds it the exact same way.
i didnt test the normal translation to a huge extent because my focus was on building the document translator as it was more important to me but i think it should be alr

anyways, ciao yall. and pls vote me i want a polaroid ;)

Life was so much simpler before i started coding

I’ve been fighting with PDF table preservation for 6 hours. Translating the text is easy, but keeping the coordinate mapping for complex nested tables was breaking every export. I finally wrote a custom block-level mapper that respects the original document bounds during the reconstruction phase.
I believe it’s perfect now

Oh fudge, the services went down or rotated, I’ll have to figure out smth local based or a more permanent service, maybe full focus on Google Translate Api? They got a super advanced dictionary for translation, wouldn’t need to retrain, and I’ll js work on the accurate reconstruction parallel batching.
Will see how this goes

Made this super fast live translation app which can translate entire 600+pages pdf in under a min and the entire file is just one single html. even tho it is over 3k lines of code and very difficult to manage (mind u very little ai i used) but not even google or paid platforms can achieve such speeds.