[tex4ht] [bug #123] support fontspec

2016-12-10 Thread Karl Berry
Follow-up Comment #17, bug #123 (project tex4ht): committed to tl, r42672. yes, regression testing is desperately needed. ___ Reply to this item at: __

[tex4ht] [bug #123] support fontspec

2016-12-10 Thread Michal Hoftich
Follow-up Comment #16, bug #123 (project tex4ht): I've found some issues when I tried to compile my older document which uses minted for syntax highlighting - calc package failed to load correctly. It uses \@for\sometempvar:=...\do{} command, and as I've found, the : had wrong catcode, so it was s

[tex4ht] [bug #123] support fontspec

2016-12-09 Thread Karl Berry
Follow-up Comment #15, bug #123 (project tex4ht): it was my mistake. you did mention it in the first changelog entry, but i failed to check that. sorry. committed to tl, along with the new html4.4ht (42665, 42666) another excellent medium-term project would be to go through the diffs between tl a

[tex4ht] [bug #123] support fontspec

2016-12-09 Thread Michal Hoftich
Follow-up Comment #14, bug #123 (project tex4ht): Karl, I just updated TL and figured out that I didn't mention usepackage.4ht as a modified file in the changelog, so it wasn't updated - it patches Fontspec upon loading, it doesn't work without it. That was my mistake, sorry.

[tex4ht] [bug #123] support fontspec

2016-12-09 Thread Karl Berry
Follow-up Comment #13, bug #123 (project tex4ht): that's what i thought too, but doing a grep, i see that info4ht.4ht (tex4ht-info.tex) shows \input mktex4ht.4ht being used in an example template (nowhere else). should actually read that file sometime :).

[tex4ht] [bug #123] support fontspec

2016-12-09 Thread Michal Hoftich
Follow-up Comment #12, bug #123 (project tex4ht): Thanks Karl. mktex4ht.4ht is used for generating seeding .4ht files from the literate sources, so it probably doesn't need to be in TL. On the other hand, it already is in TL, some prehistoric version obviously, so it is probably good to make an up

[tex4ht] [bug #123] support fontspec

2016-12-08 Thread Karl Berry
Update of bug #123 (project tex4ht): Status: In Progress => Fixed Assigned to: cvr => michal_h21 Open/Closed:Open => Closed _

[tex4ht] [bug #123] support fontspec

2016-12-08 Thread Michal Hoftich
Follow-up Comment #10, bug #123 (project tex4ht): No problems on my computer in work ___ Reply to this item at: ___ Message sent via/by Puszcza http:

[tex4ht] [bug #123] support fontspec

2016-12-07 Thread Michal Hoftich
Follow-up Comment #9, bug #123 (project tex4ht): It compiles without problems on my machine, maybe a issue with some temp files? I will try it tomorrow on a different computer. ___ Reply to this item at:

[tex4ht] [bug #123] support fontspec

2016-12-07 Thread Karl Berry
Follow-up Comment #8, bug #123 (project tex4ht): sorry about the double inclusion. i didn't think i had changed anything but the word transposition in the filename. oh well. anyway, with current repo (rev 210), i get: ! Undefined control sequence. \at:startdoc ...f }\HtmlEnv \a:Preamble \a:PROLO

[tex4ht] [bug #123] support fontspec

2016-12-04 Thread Michal Hoftich
Follow-up Comment #7, bug #123 (project tex4ht): It was included twice after the change. I fixed that, also I've found that configuration hooks were included only for xetex. it should be fixed as well now. Finally, I moved luatex definitions to fontspec-luatex.4ht. ___

[tex4ht] [bug #123] support fontspec

2016-12-03 Thread Karl Berry
Follow-up Comment #6, bug #123 (project tex4ht): i felt the need to rename xetex-fontspec.4ht to fontspec-xetex.4ht (committed in r209 along with administrivia). michal, can you check that all is still working as intended before i commit to tl, please?

Re: [tex4ht] [bug #123] support fontspec

2016-11-27 Thread Deimantas Galcius
On Nov 27, 2016, at 1:56 AM, Michal Hoftich wrote: > I have an issue with the change to tex4ht-html4.tex, the configurations aren't > saved to html4.4ht. Hi, Michal, please add the following to mktex4ht-cfg.tex file: \AddFile{9}{fontspec} \AddFile{9}{xetex-fontspec} best regards, -- deimi

[tex4ht] [bug #123] support fontspec

2016-11-26 Thread Michal Hoftich
Follow-up Comment #5, bug #123 (project tex4ht): I've just pushed code to the repo. It works for both LuaTeX and XeTeX now. I've tried it with Latin, Greek, Cyrilics and Devanagari scripts, sample file is attached. I have an issue with the change to tex4ht-html4.tex, the configurations aren't sa

[tex4ht] [bug #123] support fontspec

2016-10-30 Thread Karl Berry
Follow-up Comment #4, bug #123 (project tex4ht): michal -- just thought i'd check in about updating ... ? tx. ___ Reply to this item at: ___ Message sen

[tex4ht] [bug #123] support fontspec

2016-10-16 Thread Michal Hoftich
Follow-up Comment #3, bug #123 (project tex4ht): No, this is just a proof of concept at the moment. I was busy last week, I will try to make some more testing in the near future and then update the sources if everything works nicely. Thanks to Deimi I was able to pass "new-accents" option direct

[tex4ht] [bug #123] support fontspec

2016-10-07 Thread Karl Berry
Follow-up Comment #2, bug #123 (project tex4ht): michal, do you want me to install anything in tl at this point? ___ Reply to this item at: ___ Message

[tex4ht] [bug #123] support fontspec

2016-10-07 Thread Michal Hoftich
Follow-up Comment #1, bug #123 (project tex4ht): As we recently found the way how to alter the package loading (using usepackage.4ht), I've created small configuration for the Fontspec package. Basically, what is needed is to prevent Fontspec from loading the EU1 or EU2 font encodings and to preve