Is there any good open source that actually work with web docx editing ?
Show HN: JavaScript-first, open-source WYSIWYG DOCX editor
41–46 of 46 posts
Re: Show HN: JavaScript-first, open-source WYSIWYG DOCX editor
#42Earlier quoted context omitted.
I feel your pain. PDF applications have the same problem. The thousand page PDF spec isn't actually the spec, Acrobat is the spec.
Acrobat at least hasn't been relevant for over a decade outside of niche concerns (like javascript-enabled pdfs, which I have seen exactly twice in the wild... these should be illegal by the way). You can't say the same about microsoft.
This is not true IME, because PDF and PostScript are so tightly coupled. If your PDF renderer doesn't tightly align with Acrobat, it's highly likely to not print correctly, hence Acrobat __is__ the spec.
Re: Show HN: JavaScript-first, open-source WYSIWYG DOCX editor
#43Ah these poor fools. Having built this exact product (OOXML compatible editor in React) before, it took all of two minutes to find a bug. The issue is that the OOXML spec is not in fact definitive - Word is, and trying to implement it from the spec will produce something that works maybe 80% of the time then fall over completely when you hit one of hundreds of minor, undocumented edge cases. Assuming of course that C…
When you built this exact product, how long did it take you to reach 80% compatibility?
>> how long did it take you to reach 80% compatibility?
Honest question: when the formal spec isn't really a spec how do you even measure "80% compatibility"?
Re: Show HN: JavaScript-first, open-source WYSIWYG DOCX editor
#44Someone has to do it: Please auto-ban any "We gave Claude/Gemini/Grok/OpenAO/Qwen/Mistral/WhateverLLMAI the spec and..." "and..." resolves to: - "and now we have this impressive result you won't believe!" 100% of the time this is attention seeking, live debugging - no value at all. Don't waste people's time. Any sound and reasonable story about results without misusing the public's eye is welcome, for example: - One…
At this point I agree, this is brogramming and its getting boring.
> brogramming
Is it back? I remember 2011 it had a high time in an ad agency I was working back then :-D
Re: Show HN: JavaScript-first, open-source WYSIWYG DOCX editor
#45Ah these poor fools. Having built this exact product (OOXML compatible editor in React) before, it took all of two minutes to find a bug. The issue is that the OOXML spec is not in fact definitive - Word is, and trying to implement it from the spec will produce something that works maybe 80% of the time then fall over completely when you hit one of hundreds of minor, undocumented edge cases. Assuming of course that C…
Arent there any commercial libraries available already?
Somehow this reminds me of PDF
Re: Show HN: JavaScript-first, open-source WYSIWYG DOCX editor
#46Someone has to do it: Please auto-ban any "We gave Claude/Gemini/Grok/OpenAO/Qwen/Mistral/WhateverLLMAI the spec and..." "and..." resolves to: - "and now we have this impressive result you won't believe!" 100% of the time this is attention seeking, live debugging - no value at all. Don't waste people's time. Any sound and reasonable story about results without misusing the public's eye is welcome, for example: - One…
I disagree that this submission has no value at all or that it should be auto-banned — there is a difference between thoughtless vibe-coding and spec-driven coding, guarded by tests. It seems from the next thread that this project is hopelessly outmatched by the sheer complexity of taking on something as the Docx spec, but this project has value, and for someone, it may be all that they need.
However, I do agree with your point about live debugging. In light of that, I prefer to treat this submission as a curiosity about current model capabilities, and let the authors keep improving this project if they find it worth their time.
Let's be more respectful to the differing goals of people