Re: [tex-hyphen] Names of files in OFFO

On Thu, Mar 17, 2016 at 02:20:02PM -0400, Barbara Beeton wrote: > okay. then there *are* two entries for > every possibility Yes, indeed. I never said anything to the contrary. There can even be more than two entries if there are several characters with oxia-tonos in the pattern (rare). We

Re: [tex-hyphen] Names of files in OFFO

On Thu, Mar 17, 2016 at 01:55:27PM -0400, Barbara Beeton wrote: > that's all very well, and i understand > how *unicode* works. what i'd really > like to see is how this equivalence > is determined in a (la)tex source file. In the case of Greek hyphenation, by making as many copies of the

Re: [tex-hyphen] Names of files in OFFO

On Wed, Mar 16, 2016 at 09:07:50PM +0100, Ulrike Fischer wrote: > A bit of-topic: On tex.sx there was some time ago a question about > how to combine modern and classic greek in one document with babel > and I saw that there is no simple way to do it. Wouldn't Ancient Greek hyphenation work

Re: [tex-hyphen] Names of files in OFFO

On Thu, Mar 17, 2016 at 06:42:41PM +, Arthur Reutenauer wrote: > > I did moot the idea of enhancing the hyphenation algorithm with an > equivalence table (I came across several use cases that would benefit > from that), but someone would need to work on it, of course. This idea, probably

Re: [tex-hyphen] Names of files in OFFO

On Thu, Mar 17, 2016 at 10:58:22PM +, Philip Taylor wrote: > That "ancient Greek is not a true superset [of modern Greek]; modern > Greek contains where ancient Greek would contain > , or character>" > because "tonos and oxia /look/ the same; search a file for >

Re: [tex-hyphen] Names of files in OFFO

On Thu, Mar 17, 2016 at 01:35:04PM -0400, Barbara Beeton wrote: > where and how is canonical equivalence > defined? (pointer to reference?) Section 2.12 of the Unicode Standard for the general presentation and 3.7 for the formal definition (definition D70). Best,

Re: [tex-hyphen] Names of files in OFFO

Am Fri, 11 Mar 2016 19:55:59 +0100 schrieb Claudio Beccari: [latin hyphenation variants] A bit of-topic: On tex.sx there was some time ago a question about how to combine modern and classic greek in one document with babel and I saw that there is no simple way to do it. How is the situation

Re: [tex-hyphen] Names of files in OFFO

Am Thu, 17 Mar 2016 00:41:23 +0100 schrieb Claudio Beccari: >> [latin hyphenation variants] >> >> A bit of-topic: On tex.sx there was some time ago a question about >> how to combine modern and classic greek in one document with babel >> and I saw that there is no simple way to do it. >> >> How

Re: [tex-hyphen] Names of files in OFFO

On Thu, 17 Mar 2016, Arthur Reutenauer wrote: On Thu, Mar 17, 2016 at 02:20:02PM -0400, Barbara Beeton wrote: > okay. then there *are* two entries for > every possibility Yes, indeed. I never said anything to the contrary. There can even be more than two entries if there

Re: [tex-hyphen] Names of files in OFFO

On Thu, Mar 17, 2016 at 01:55:27PM -0400, Barbara Beeton wrote: > that's all very well, and i understand > how *unicode* works. what i'd really > like to see is how this equivalence > is determined in a (la)tex source file. In the case of Greek hyphenation, by making as

Re: [tex-hyphen] Names of files in OFFO

Arthur Reutenauer wrote: > Wouldn't Ancient Greek hyphenation work for that? The character > repertoire should be a superset of the one of Modern Greek, and the > linebreaks (mostly) consistent. No, ancient Greek is not a true superset; modern Greek contains where ancient Greek would contain

Re: [tex-hyphen] Names of files in OFFO

On Thu, Mar 17, 2016 at 01:35:04PM -0400, Barbara Beeton wrote: > where and how is canonical equivalence > defined? (pointer to reference?) Section 2.12 of the Unicode Standard for the general presentation and 3.7 for the formal definition (definition D70). that's all very

Re: [tex-hyphen] Names of files in OFFO

Am Thu, 17 Mar 2016 15:11:31 +0100 schrieb Javier Bezos: > > The babel code certainly push to think in this way. But imho nothing > > prevents a language.ldf author to setup internally three > > (independant) languages, e.g. classiclatin, medievallatin, > > modernlatin, > > In fact, german,

Re: [tex-hyphen] Names of files in OFFO

On Thu, Mar 17, 2016 at 03:44:50PM +, Philip Taylor wrote: > No, ancient Greek is not a true superset; modern Greek contains > where ancient Greek would contain , > or character>. Tonos and oxia are the same character. Arthur

Re: [tex-hyphen] Names of files in OFFO

Arthur Reutenauer wrote: > Tonos and oxia are the same character. Tonos and oxia /look/ the same; search a file for character+oxia when the file has been created with character+tonos and the former will not be found. Philip Taylor

Re: [tex-hyphen] Names of files in OFFO

Arthur Reutenauer wrote: > On Thu, Mar 17, 2016 at 05:26:35PM +, Philip Taylor wrote: >> Tonos and oxia /look/ the same; search a file for character+oxia when >> the file has been created with character+tonos and the former will not >> be found. > > They will if your editor takes

Re: [tex-hyphen] Names of files in OFFO

Arthur Reutenauer wrote: > On Thu, Mar 17, 2016 at 10:58:22PM +, Philip Taylor wrote: >> That "ancient Greek is not a true superset [of modern Greek]; modern >> Greek contains where ancient Greek would contain >> , or character>" >> because "tonos and oxia

Re: [tex-hyphen] Names of files in OFFO

On Thu, Mar 17, 2016 at 05:26:35PM +, Philip Taylor wrote: > Tonos and oxia /look/ the same; search a file for character+oxia when > the file has been created with character+tonos and the former will not > be found. They will if your editor takes canonical equivalence into account.

Re: [tex-hyphen] Names of files in OFFO

Arthur Reutenauer wrote: > That's not a very good point, then. Thank you for your opinion, Arthur.

Re: [tex-hyphen] Names of files in OFFO

The example of greek is a good one, but for qwhat concerns the TeXSystem it is a bad one. When unicode/utf8 engines are used the unicode encoded patterns are available because Apostolos Syropoulos created the several years ago (since these engine have been available) and I suppose they are

Re: [tex-hyphen] Names of files in OFFO

Arthur Reutenauer wrote: > On Thu, Mar 17, 2016 at 05:32:55PM +, Philip Taylor wrote: >> Which many (perhaps most) search utilities and editors do not. > > If you say so. What's your point? That "ancient Greek is not a true superset [of modern Greek]; modern Greek contains where ancient

Re: [tex-hyphen] Names of files in OFFO

On Thu, 17 Mar 2016, Arthur Reutenauer wrote: On Thu, Mar 17, 2016 at 03:44:50PM +, Philip Taylor wrote: > No, ancient Greek is not a true superset; modern Greek contains > where ancient Greek would contain , > or character>. Tonos and oxia

Re: [tex-hyphen] Names of files in OFFO

Am Thu, 17 Mar 2016 17:00:22 + schrieb Arthur Reutenauer: > On Thu, Mar 17, 2016 at 05:48:26PM +0100, Ulrike Fischer wrote: >> I think (but I don't know anything about greek) that it wasn't only >> a question of hyphenation but also other settings, like >> accents/words etc, which are

Re: [tex-hyphen] Names of files in OFFO

I never tried to mix modern and classic latin, but I suppose that with polyglossia it might be possible, thanks to the possibility of changing settings with \PolyglossiaSetup, and/or to specify the same secondary (other) language with different options again and again. As far as I know babel,