Re: HTML => ODT - almost identical conversion possible?

["wolfgang häfelinger" <whaefelinger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 2795 bytes --]

> Why would a recruiter make such requests? There's no reason for them to 
change your design, right?

Damned right you are. Of course they don't change my design. They just put 
*their* company logo on each page ;-)

> How about thinking outside the box.

I did that years ago where my base resume document has been odt/docx. Then 
I did some XPATH madness things
to translate into ASCIIDOC and from there to DOCBOOK 4 and then via dblatex 
to xelatex to (beautifull) PDF. 
ASCIIDOCTOR and PANDOC did not exist at that time.

> That way the docx/odt would look as you intended, but if someone 
copy-pastes its content, there's no formatting to screw something up. 
Win-win.

Hmm, good idea. Kind of "write protected" word document. However, the point 
is that they expect a "unprotected"  Word document (see above).

Perhaps I should do it this way:
Just expose a public service that renders my resume into a PDF. By default 
it renders my style. However, a interested recruiter an upload images and
(CSS) styles for customization. Voila. Who wants to receive a Word document 
anyway?


On Thursday, 15 April 2021 at 19:50:23 UTC+2 monk...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:

>
> > The idea is to generate ODT or DOCX out of such a resume cause DOCX is 
> > often required by some recruiters).
>
> How about thinking outside the box.
>
> Why would a recruiter make such requests? There's no reason for them to 
> change your design, right? So the only reason could be to get at your 
> raw data to input them into some system. They just don't have a simple 
> way to communicate that. (For anything else I'm assuming unreasonable 
> until proven innocent for now.)
>
> But if what they really need is raw data, asciidoc should be even 
> better. So… what if the docx/odt contained your plain asciidoc. And what 
> if this asciidoc was hidden behind pictures of the pdf/html. That way 
> the docx/odt would look as you intended, but if someone copy-pastes its 
> content, there's no formatting to screw something up. Win-win.
>
> So, I propose:
>
> 1. generate html/pdf from asciidoc via pandoc
>
> 2. turn each page of html/pdf into an image via unknown means
>
> 3. generate docx/odt from asciidoc plus images via pandoc plus a filter
>
> Why use a crowbar on pandoc if pandoc can be your crowbar ;)
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a075f737-75ea-42de-aa1f-ee965e05e92bn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3582 bytes --]