Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change of boundary character class in newer XeTeX and gloss-french #145

Open
eg9 opened this Issue May 4, 2016 · 16 comments

Comments

Projects
None yet
6 participants
@eg9
Copy link
Contributor

eg9 commented May 4, 2016

Due to the recent increase in the number of character classes, the boundary class is now 4095 instead of 255.

gloss-french.ldf contains four references to class 255, that should (conditionally) be changed. Probably the best place for the following code is polyglossia.sty

\@ifundefined{e@alloc@intercharclass@top}
  {\chardef\xpg@boundaryclass=\@cclv}
  {\let\xpg@boundaryclass=\e@alloc@intercharclass@top}

and then the four references to 255 in gloss-french.ldf should become \xpg@boundaryclass

The test above will return true (and the boundaryclass set to 255) if the LaTeX kernel is old; otherwise, the LaTeX kernel already takes care of setting the correct number based on the XeTeX version.

I didn't check the whole Polyglossia tree, the change might impact other language definition files.

Reference: http://tex.stackexchange.com/a/307672/4427 (the example file produces the expected result with TL 2015, but not with TL 2016/pretest)

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Jun 6, 2016

cf josephwright/csquotes#8

should it be possible to publish this change, which make french polyglossia incomptaible with TeXLive2016

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Jun 12, 2016

@eg9 In this MWE

\documentclass{article}
\begin{document}
\makeatletter
\meaning\e@alloc@intercharclass@top
\makeatother
\end{document}

\e@alloc@intercharclass@top is undefined. Are your sure of you?

@eg9

This comment has been minimized.

Copy link
Contributor Author

eg9 commented Jun 13, 2016

@maieul

Unfortunately, we have to wait until LaTeX2e <2016/03/31> Patch Level 1 is rolled in.

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Jun 13, 2016

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Jul 17, 2016

hi @reutenauer do you think that could be solved in next time? it is a major regression

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Aug 21, 2016

hi @reutenauer any new ?

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Sep 6, 2016

hi @reutenauer are your still available? this bug seems me importan, as it's break ascendant compatibility.

@reutenauer

This comment has been minimized.

Copy link
Owner

reutenauer commented Sep 6, 2016

I suppose I can release a quick-and-dirty fix, but you should know better than to push for this kind of things.

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Sep 7, 2016

ok, I will do a pull request

Le 7 sept. 2016 � 00:30, Arthur Reutenauer notifications@github.com a �crit :

I suppose I can release a quick-and-dirty fix, but you should know better than to push for this kind of things.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@aurelberra

This comment has been minimized.

Copy link

aurelberra commented Apr 5, 2017

Unless I have missed something, we still don't have a solution. The importance for LaTeX documents in French is obvious. Is it such a difficult problem to tackle?

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Apr 5, 2017

For now, I have adapted the code in my local repository. I was waiting for #141 before publishing it. I will open a pull request quickly.

@ArchangeGabriel

This comment has been minimized.

Copy link

ArchangeGabriel commented Apr 5, 2017

I’ve been using polyglossia when I switched to XeLaTeX from LaTeX, because it was advised to do so. But after some time and issues rising with polyglossia (like this one), I switched back to Babel which had added support for XeLaTeX during this time, and I have not found any issue with it.

Are there still reason to use polyglossia rather than Babel? Especially with the maintainer seemingly MIA? I know they are still reason to use it for RTL or non-latin script languages (which should even be fixed in 3.10, although this release is two years late now…), but everyone active here seems to be using it for french, so…

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Apr 6, 2017

@jfbu

This comment has been minimized.

Copy link

jfbu commented Dec 3, 2017

Any idea when merged #178 will make it into CTAN?

@maieul

This comment has been minimized.

Copy link
Contributor

maieul commented Dec 3, 2017

@jfbu

This comment has been minimized.

Copy link

jfbu commented Dec 3, 2017

@maieul Thanks. At first I did not realize #178 had fixed this issue #145 because the issue is still "Open".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.