<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gf-core.git/src/runtime/haskell/PGF/Lexing.hs, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.adelon.net/gf-core.git/atom?h=master</id>
<link rel='self' href='https://git.adelon.net/gf-core.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/'/>
<updated>2017-09-04T09:43:37+00:00</updated>
<entry>
<title>eliminate modules PGF.Lexing, PGF.LexingAGreek. Make PGF.Utilities an internal module in the runtime. These are not really part of the core runtime.</title>
<updated>2017-09-04T09:43:37+00:00</updated>
<author>
<name>Krasimir Angelov</name>
<email>kr.angelov@gmail.com</email>
</author>
<published>2017-09-04T09:43:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=1f908fa7bf65f51540ccb2b70ca2bd00d9b3dedf'/>
<id>urn:sha1:1f908fa7bf65f51540ccb2b70ca2bd00d9b3dedf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>handling combination of &amp;+ and &amp;|</title>
<updated>2017-06-02T06:11:44+00:00</updated>
<author>
<name>aarne</name>
<email>aarne@chalmers.se</email>
</author>
<published>2017-06-02T06:11:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=9e206496a7f226ec7166874153e348381c37154e'/>
<id>urn:sha1:9e206496a7f226ec7166874153e348381c37154e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>handling capitalization (&amp;|) in unlexer -bind</title>
<updated>2017-06-02T06:06:57+00:00</updated>
<author>
<name>aarne</name>
<email>aarne@chalmers.se</email>
</author>
<published>2017-06-02T06:06:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=d1eb0aa657e05f035d3679555e1b45401f1e3a25'/>
<id>urn:sha1:d1eb0aa657e05f035d3679555e1b45401f1e3a25</id>
<content type='text'>
</content>
</entry>
<entry>
<title>(un)lexmixed: added the other math environments than $ used in latex</title>
<updated>2014-10-19T17:43:39+00:00</updated>
<author>
<name>aarne</name>
<email>aarne@chalmers.se</email>
</author>
<published>2014-10-19T17:43:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=84bce336fd2acc5b18e0e8792a82b682dacaab37'/>
<id>urn:sha1:84bce336fd2acc5b18e0e8792a82b682dacaab37</id>
<content type='text'>
</content>
</entry>
<entry>
<title>one general case in dealing with backslash in latex lexing is enough</title>
<updated>2014-10-17T15:49:23+00:00</updated>
<author>
<name>aarne</name>
<email>aarne@chalmers.se</email>
</author>
<published>2014-10-17T15:49:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=5c862a3c7bda63886426a785357bad03b839dfa9'/>
<id>urn:sha1:5c862a3c7bda63886426a785357bad03b839dfa9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>unlexing latex code: no space between closing $ and punctuation</title>
<updated>2014-10-17T07:04:50+00:00</updated>
<author>
<name>aarne</name>
<email>aarne@chalmers.se</email>
</author>
<published>2014-10-17T07:04:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=2caf6fa125f7f91a7a78b7f0699a43c2d922e687'/>
<id>urn:sha1:2caf6fa125f7f91a7a78b7f0699a43c2d922e687</id>
<content type='text'>
</content>
</entry>
<entry>
<title>lexer for latex code: don't separate backslash from the macro name that it marks</title>
<updated>2014-10-17T06:40:06+00:00</updated>
<author>
<name>aarne</name>
<email>aarne@chalmers.se</email>
</author>
<published>2014-10-17T06:40:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=42cfacbf867184ae5bc495a247fa6fbeb8c90639'/>
<id>urn:sha1:42cfacbf867184ae5bc495a247fa6fbeb8c90639</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Change the type of PGF.Lexing.bindTok to [String] -&gt; [String]</title>
<updated>2014-04-09T17:39:21+00:00</updated>
<author>
<name>hallgren</name>
<email>hallgren@chalmers.se</email>
</author>
<published>2014-04-09T17:39:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=50ea3d265c35b677b60aa6a465eb19bcd66d25ad'/>
<id>urn:sha1:50ea3d265c35b677b60aa6a465eb19bcd66d25ad</id>
<content type='text'>
The old type was [String] -&gt; String. This function was only used
in GF.Text.Lexing.stringOp, which now uses (unwords . bindTok) instead,
with no change in behaviour.
</content>
</entry>
<entry>
<title>Unlexers: move capitalization of first word from GF.Text.Lexing to PGF.Lexing</title>
<updated>2014-04-09T17:26:23+00:00</updated>
<author>
<name>hallgren</name>
<email>hallgren@chalmers.se</email>
</author>
<published>2014-04-09T17:26:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=677d849840e3a5b8f69044ef43151908b0f6737b'/>
<id>urn:sha1:677d849840e3a5b8f69044ef43151908b0f6737b</id>
<content type='text'>
The capitalization of the first word was done in GF.Text.Lexing.stringOp,
but is now done in the functions unlexText and unlexMixed in PGF.Lexing.
These functions are only used in stringOp and in PGFService (where the change
is needed), so the subtle change in behaviour should not cause any bugs.
</content>
</entry>
<entry>
<title>PGF Service: a bit more clever lexer=text</title>
<updated>2014-04-09T14:13:18+00:00</updated>
<author>
<name>hallgren</name>
<email>hallgren@chalmers.se</email>
</author>
<published>2014-04-09T14:13:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=04a6260eeaf626cf4774d087d8810d438f554b46'/>
<id>urn:sha1:04a6260eeaf626cf4774d087d8810d438f554b46</id>
<content type='text'>
Only change the first word to lowercase if the original input is not found in
the grammar's morphology. This allows parsing of sentenses starting with "I" in 
English, nouns in German and proper names in other languages, but it can make
the wrong choice for multi-words.
</content>
</entry>
</feed>
