[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] fenfire/docs/pegboard/src_utf8--tjl peg.rst
From: |
Tuomas J. Lukka |
Subject: |
[Gzz-commits] fenfire/docs/pegboard/src_utf8--tjl peg.rst |
Date: |
Fri, 16 May 2003 08:19:54 -0400 |
CVSROOT: /cvsroot/fenfire
Module name: fenfire
Changes by: Tuomas J. Lukka <address@hidden> 03/05/16 08:19:54
Modified files:
docs/pegboard/src_utf8--tjl: peg.rst
Log message:
current
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/docs/pegboard/src_utf8--tjl/peg.rst.diff?tr1=1.1&tr2=1.2&r1=text&r2=text
Patches:
Index: fenfire/docs/pegboard/src_utf8--tjl/peg.rst
diff -u fenfire/docs/pegboard/src_utf8--tjl/peg.rst:1.1
fenfire/docs/pegboard/src_utf8--tjl/peg.rst:1.2
--- fenfire/docs/pegboard/src_utf8--tjl/peg.rst:1.1 Wed May 14 04:08:11 2003
+++ fenfire/docs/pegboard/src_utf8--tjl/peg.rst Fri May 16 08:19:53 2003
@@ -3,9 +3,9 @@
=============================================================
:Author: Tuomas J. Lukka
-:Last-Modified: $Date: 2003/05/14 08:08:11 $
-:Revision: $Revision: 1.1 $
-:Status: Incomplete
+:Last-Modified: $Date: 2003/05/16 12:19:53 $
+:Revision: $Revision: 1.2 $
+:Status: Current
We are having lots of issues with docutils because we use
Latin-1 encoding in our files to write e.g. "Jyväskylä".
@@ -22,12 +22,12 @@
- Will this be a problem with email? E.g. posting PEGs...
- RESOLVED: Maybe, but not an important one. It's
- easy enough to read the few garbled symbols if there are any,
+ RESOLVED: Maybe, but not an important one.
+
+ Many mail clients do already support UTF8. If yours does not, it's
+ still easy enough to read the few garbled symbols if there are any,
and the important thing is that in CVS, things will work.
- This OTOH gives some incentive to start thinking about UTF-8
- mail.
- Isn't UTF8 difficult to edit?
@@ -36,22 +36,19 @@
- Can we use UTF-8 with TeX? If not, what do we do?
- RESOLVED: Doesn't seem to be possible, but we can use
- the TeX escapes::
-
- \"a, \"o ...
-
- to handle this without breaking the high-bit rule.
- Besides, our use of TeX directly is on the way out.
+ RESOLVED: Yes. There are two packages: utf8 inputencoding,
+ and omega. So far, we've tried utf8, and will probably
+ start using omega if it seems functional.
-- Are you serious about using smiley faces or other special
- unicode characters in identifiers?
+- Are you serious about using special unicode characters in identifiers?
RESOLVED: Yes, occasionally, if they can help. However,
much care is needed; never choose a character that looks
like some other one. For instance, 2133 (SCRIPT CAPITAL M)
is useless here.
+
+
Changes
=======
@@ -61,8 +58,6 @@
Explain this in README, along with instructions for the most
popular editors on how what to do.
-
-Start using smiley faces as characters in Java identifiers ;)
Create a grep script which sniffs out Latin-1 ä, ö, Ä, Ö from new files.