GNU TeXmacs - Bugs: bug #37422, current windows version does not...
You are not allowed to post comments on this tracker with your current authentication level.
bug #37422: current windows version does not hyphenate
Submitter: | Philippe Joyez <pjoyez> | ||
Submitted: | Sat 22 Sep 2012 07:44:06 AM UTC | ||
Category: | Windows port | Priority: | 5 - Normal |
Item Group: | Error | Status: | Fixed |
Privacy: | Public | Assigned to: | _86389 |
Originator Name: | Giovanni (Josh-186) | Open/Closed: | Closed |
Release: | None | Release: | |
Fixed Release: | None | Fixed Release: | |
Keywords: | hyphenation |
Fri 21 Nov 2014 06:52:19 PM UTC, comment #1: |
Philippe Joyez <pjoyez> |
Sat 22 Sep 2012 07:44:06 AM UTC, original submission:
|
Philippe Joyez <pjoyez> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-11-21 | pjoyez | Status | Confirmed | Fixed | |
Open/Closed | Open | Closed | |||
2012-11-10 | fpoulain | Assigned to | None | _86389 |
Powered by Savane 3.13-f8d8.
Corresponding source code
The problem is still present in the latest windows version downloadable from the website... But next version should be OK!
I have finally understood what causes the problem: it's subversion! Believe it or not, when you checkout, svn translates on-the-fly the line termination characters (CRLF vs LF) according to the destination platform! Hence, the texmacs source files are different under windows and other platforms. And AFAICT yout can't simply fix this by setting an option for co.
In particular, the hyphenation files have their entries terminated by CRLF in windows vs LF in linux or MacOS, and that causes the hyphenation patterns not to load properly in windows.
I've committed a fix for this in rev. 8812.