Skip to content

Commit

Permalink
Fix Unicode
Browse files Browse the repository at this point in the history
  • Loading branch information
GlitchMr committed Dec 2, 2012
1 parent 0df6ae4 commit 555c1b7
Show file tree
Hide file tree
Showing 78 changed files with 207 additions and 206 deletions.
5 changes: 3 additions & 2 deletions source/archive/convert_pod2html.pl
Expand Up @@ -3,6 +3,7 @@
use File::Slurp;
use Pod::HtmlEasy;
use File::Find::Rule;
use Encode 'encode_utf8';

#####################
#
Expand Down Expand Up @@ -83,7 +84,7 @@
$html .= $podhtml->pod2html( $file, %pod_opts );

# Remove =encoding statement
$html =~ s/<pre>=encoding utf-?8<\/pre>//;
my $utf = $html =~ s/<pre>=encoding utf-?8<\/pre>//;

write_file( $html_file, $html );
write_file( $html_file, $utf ? $html : encode_utf8 $html );
}
2 changes: 1 addition & 1 deletion source/archive/faq.html
Expand Up @@ -71,7 +71,7 @@
specified using distinctive syntactic forms.</p>
<a name='Will people be able to develop in Perl 6 and release stand-alone executables, so as to protect their original code?'></a><h2>Will people be able to develop in Perl 6 and release stand-alone
executables, so as to protect their original code?</h2>
<p>Since Perl 6 is a language specification, the details will depend on the
<p>Since Perl 6 is a language specification, the details will depend on the
specific compilers.</p>
<p>Rakudo, a Perl 6 compiler based on Parrot, allows compilation to bytecode, and
a small wrapper exists that can pack up a bytecode file and parrot into a
Expand Down
Expand Up @@ -130,7 +130,7 @@
where he announced his proof of concept for loadable java
bytecodes. Dan encouraged him to keep up the good work.</p>
<a name='matrix design'></a><h2>matrix design</h2>
<p>Josef Höök posted a <a href='http://archive.develooper.com/perl6-internals@perl.org/msg10599.html' target='_blank'>archive.develooper.com</a>
<p>Josef Höök posted a <a href='http://archive.develooper.com/perl6-internals@perl.org/msg10599.html' target='_blank'>archive.develooper.com</a>
which opened something of a can of worms. People <a href='http://archive.develooper.com/perl6-internals@perl.org/msg10606.html' target='_blank'>archive.develooper.com</a>
for first class matrices (though Dan disagreed with them, pointing at
the PDL project.)</p>
Expand Down
Expand Up @@ -7,7 +7,7 @@
having fun with the Perl 6 grammar.</p>
<p>Let's see what they got up to this week...</p>
<a name='PerlArray strange behaviour'></a><h2>PerlArray strange behaviour</h2>
<p>At the end of last week, Josef Höök (the man whose name I have to cut
<p>At the end of last week, Josef Höök (the man whose name I have to cut
and paste...) found some peculiarities when using negative indices
with PerlArray objects in Parrot. Jeff (DrForr) explained that the
problem arose from Josef using partially deprecated
Expand Down
Expand Up @@ -196,7 +196,7 @@
<p>The misnamed coroutines thread continued, discussing the use of
coroutines as iterators in while and for loops, which then morphed
into a discussion of <code>&lt;&lt;</code>. You see, <code>&lt;&lt;...&gt;&gt;</code> is the ASCII
synonym for <code>«...»</code>, which is, in turn a (the?) new
synonym for <code>«...»</code>, which is, in turn a (the?) new
way of saying <code>qw/.../</code> (and for vectorizing an op). Ken Fox worried
that using <code>&lt;&lt;</code> in this way would mean you couldn't use it for
introducing a HERE doc, but Damian assured him that it wasn't a
Expand Down
28 changes: 14 additions & 14 deletions source/archive/list-summaries/2004/p6summary.2004-01-25.html
Expand Up @@ -174,7 +174,7 @@
<a name='Meanwhile in perl6-language'></a><h1>Meanwhile in perl6-language</h1>
<a name='Semantics of Vector operations'></a><h2>Semantics of Vector operations</h2>
<p>Determined to test everyone's Unicode readiness, Luke Palmer kicked
off a discussion of the semantics of <code>[1,2,3] »+«
off a discussion of the semantics of <code>[1,2,3] »+«
[4,5,6]</code>. At first glance it looks like the result should be
<code>[5,7,9]</code>, but Luke argued that actually, the code was trying to add
two lists, each containing a single scalar, that just happened to be
Expand All @@ -183,15 +183,15 @@
surprise'&quot;, before going on to surprise us all with 'lopsided' vector
ops, which would allow the programmer to specify when a value was
expected to be treated as a scalar:</p>
<pre> $a »+« $b # Treat $a and $b as lists
$x +« $y # Treat $x as a scalar and $b as a list
-« @bar # Return a list of every element of @bar, negated
@foo »+ @bar # Add the length of @bar to every element of @foo</pre>
<p>Then he scared me with <code>@foo »+= @foo</code>. He noted that it might take
some getting used to, but that it helped if you pronounce <code>»</code> and
<code>«</code> as 'each'. Austin Hastings didn't like it (from a syntax
<pre> $a »+« $b # Treat $a and $b as lists
$x +« $y # Treat $x as a scalar and $b as a list
-« @bar # Return a list of every element of @bar, negated
@foo »+ @bar # Add the length of @bar to every element of @foo</pre>
<p>Then he scared me with <code>@foo »+= @foo</code>. He noted that it might take
some getting used to, but that it helped if you pronounce <code>»</code> and
<code>«</code> as 'each'. Austin Hastings didn't like it (from a syntax
highlighting point of view), but he appeared to be outvoted. Larry
pointed out that <code>«»</code> etc were the least of a syntax highlighters
pointed out that <code>«»</code> etc were the least of a syntax highlighters
worries given that any <code>use</code>, <code>eval</code> or operator
declaration had the potential to morph any subsequent syntax. Piers
Cawley thought that truly accurate syntax highlighting would have
Expand All @@ -203,14 +203,14 @@
apparent that people seem to like this particular weirding of the
language, and it certainly allows the programmer to disambiguate
things rather neatly. Luke even pointed out that this new approach
allows for calling a method on a list of values: <code>@list ».method</code>,
and to call a list of methods on a value: <code>$value.« @methods</code>.</p>
<p>Then the fun began. The issue is that <code>»</code> and <code>«</code> can also be
allows for calling a method on a list of values: <code>@list ».method</code>,
and to call a list of methods on a value: <code>$value.« @methods</code>.</p>
<p>Then the fun began. The issue is that <code>»</code> and <code>«</code> can also be
written <code>&lt;&lt;</code> and <code>&gt;&gt;</code> (but your POD processor hates you
for it). This leads to ambiguities like
<code>&gt;&gt;+&lt;&lt;=&lt;&lt;</code> (which are even harder to type in
a Pod escape) which can be parsed as <code>»+&lt;&lt;=«</code> or
<code>»+«=«</code>. Larry wondered if the problem arose because of trying to
a Pod escape) which can be parsed as <code>»+&lt;&lt;=«</code> or
<code>»+«=«</code>. Larry wondered if the problem arose because of trying to
make the <code>&lt;<code>lt</code></code> and <code>&gt;&gt;</code> alternatives look too similar
to the Unicode glyphs.</p>
<p>You know, looking at that last paragraph I can see why people think
Expand Down
4 changes: 2 additions & 2 deletions source/archive/list-summaries/2004/p6summary.2004-02-01.html
Expand Up @@ -103,8 +103,8 @@
turned into a discussion of the meaning of 'vector' which has
different meanings depending on whether you're a mathematician or
Seymour Cray.</p>
<p>Another sub-thread discussed the possible ASCII alternatives for <code>«</code>
and <code>»</code>. I'm afraid I'm going to bottle out of attempting to
<p>Another sub-thread discussed the possible ASCII alternatives for <code>«</code>
and <code>»</code>. I'm afraid I'm going to bottle out of attempting to
summarize the various alternatives suggested, if only because I used
up all my POD escape-fu last week. It looks like the <code>&lt;&lt;</code> and
<code>&gt;&gt;</code> alternatives might be about to bite the dust in favour
Expand Down
Expand Up @@ -107,7 +107,7 @@
<p><a href='http://groups.google.com/groups?selm=4024E112.5030809@toetsch.at' target='_blank'>groups.google.com</a></p>
<a name='Meanwhile, in perl6-language'></a><h1>Meanwhile, in perl6-language</h1>
<a name='The Unicode argument again'></a><h2>The Unicode argument again</h2>
<p>Andy Wardley strongly advocated not making Unicode operators <code>«</code>, <code>»</code>
<p>Andy Wardley strongly advocated not making Unicode operators <code>«</code>, <code>»</code>
etc part of the core language. Larry disagreed, but proposed that any
Unicode declarations should also have an <code>is ASCII('!@#$')</code> trait to
specify the ASCII equivalent.</p>
Expand Down
6 changes: 3 additions & 3 deletions source/archive/list-summaries/2004/p6summary.2004-02-15.html
Expand Up @@ -20,7 +20,7 @@
Data::Dumper. Way to go Jens. People were impressed.</p>
<p><a href='http://groups.google.com/groups?selm=200402051301.35111.parrot@jensbeimsurfen.de' target='_blank'>groups.google.com</a></p>
<a name='Supporting simple PMCs as keys'></a><h2>Supporting simple PMCs as keys</h2>
<p>Stéphane Payrard posted a patch to support using simple PMCs instead of
<p>Stéphane Payrard posted a patch to support using simple PMCs instead of
full on key PMCs for simple lookups. He and Leo discussed it, but the
patch hasn't been accepted yet.</p>
<p><a href='http://groups.google.com/groups?selm=20040209192126.GB17703@stefp.dyndns.org' target='_blank'>groups.google.com</a></p>
Expand Down Expand Up @@ -75,7 +75,7 @@
<p><a href='http://groups.google.com/groups?selm=a06010204bc52aa01e263@' target='_blank'>groups.google.com</a>[172.24.18.98]</p>
<a name='Object spec'></a><h2>Object spec</h2>
<p>Dan noted that he'd checked in some major revisions to PDD15 (objects!)
and suggested that people take a look. Simon Glover, Leo Tötsch and LF
and suggested that people take a look. Simon Glover, Leo Tötsch and LF
had questions.</p>
<p><a href='http://groups.google.com/groups?selm=a0601020bbc52f88649a7@' target='_blank'>groups.google.com</a>[172.24.18.98]</p>
<a name='Meanwhile in perl6-language'></a><h1>Meanwhile in perl6-language</h1>
Expand All @@ -100,7 +100,7 @@
<p><a href='http://groups.google.com/groups?selm=20040212031134.GA16797@babylonia.flatirons.org' target='_blank'>groups.google.com</a></p>
<p><a href='http://groups.google.com/groups?selm=20040213041440.28310.qmail@web40802.mail.yahoo.com' target='_blank'>groups.google.com</a></p>
<p><a href='http://groups.google.com/groups?selm=402EA18A.40604@rodadams.net' target='_blank'>groups.google.com</a> -- Feel Rod's pain.</p>
<a name='Haven't I had this feeling of déja before?'></a><h2>Haven't I had this feeling of déja vù before?</h2>
<a name='Haven't I had this feeling of déja before?'></a><h2>Haven't I had this feeling of déja vù before?</h2>
<p>Dmitry Dorofeev pointed everyone at Scharli et al's paper on Smalltalk
Traits and proposed that Perl 6 use something similar. Which is what
Larry proposed a few weeks back, except he called Traits Roles and
Expand Down
8 changes: 4 additions & 4 deletions source/archive/list-summaries/2004/p6summary.2004-02-22.html
Expand Up @@ -5,7 +5,7 @@
just dive straight into perl6-internals</p>
<a name='Loading bytecode at runtime'></a><h2>Loading bytecode at runtime</h2>
<p>Last week Dan had specced out the rules for runtime loading of
bytecode. This week, Leo Tötsch started implementing it. There was a
bytecode. This week, Leo Tötsch started implementing it. There was a
certain amount of quibbling about syntax, but that was quickly sorted
out.</p>
<p><a href='http://groups.google.com/groups?selm=200402200842.i1K8g4F15344@thu8.leo.home' target='_blank'>groups.google.com</a></p>
Expand All @@ -14,7 +14,7 @@
niggles. Getting ahead of myself slightly, he finished it this week.</p>
<p><a href='http://groups.google.com/groups?selm=a06010208bc581095417f@' target='_blank'>groups.google.com</a>[172.24.18.98]</p>
<a name='Obfuscated Parrot'></a><h2>Obfuscated Parrot</h2>
<p>I reproduce this product of Leo Tötsch's warped brane without comment:</p>
<p>I reproduce this product of Leo Tötsch's warped brane without comment:</p>
<pre> bounds 1
trace 0
split P0, '', &quot;\nrekcaH torraP rehtona tsuJ&quot;
Expand Down Expand Up @@ -87,7 +87,7 @@
<p><a href='http://groups.google.com/groups?selm=1077166499.24310.78.camel@localhost' target='_blank'>groups.google.com</a></p>
<a name='Parrot Day at the Austrian Perl Workshop'></a><h2>Parrot Day at the Austrian Perl Workshop</h2>
<p>Thomas Klausner announced that this year's Austrian Perl Workshop would
have a Parrot Day, with a tutorial from Leo Tötsch and hopefully some
have a Parrot Day, with a tutorial from Leo Tötsch and hopefully some
other good stuff from Parrot luminaries. Thomas also asked for people
to submit talk ideas.</p>
<p><a href='http://groups.google.com/groups?selm=20040220015102.GL2974@zsi.at' target='_blank'>groups.google.com</a></p>
Expand All @@ -104,7 +104,7 @@
<p><a href='http://www.sebastian-bergmann.de/InterpretedLanguages2004/' target='_blank'>www.sebastian-bergmann.de</a></p>
<a name='Meanwhile, in perl6-languages'></a><h1>Meanwhile, in perl6-languages</h1>
<a name='Traits/Roles'></a><h2>Traits/Roles</h2>
<p>I know I've had this feeling of déjà vu before, but I've spelt it
<p>I know I've had this feeling of déjà vu before, but I've spelt it
right this time. Discussion of Roles continued this week. If I never
read another discussion of the difference between <code>Dog::bark</code> and
<code>Tree::bark</code> again, it'll be too soon.</p>
Expand Down
Expand Up @@ -35,7 +35,7 @@
<p><a href='http://groups.google.com/groups?selm=a06010202bc5fcbfaeb19@' target='_blank'>groups.google.com</a>[172.24.18.98]</p>
<p><a href='http://groups.google.com/groups?selm=a06010205bc5fd8fef7f7@' target='_blank'>groups.google.com</a>[172.24.18.98]</p>
<a name='Feature Freeze'></a><h2>Feature Freeze</h2>
<p>On Wednesday, Leo Tötsch announced a feature slush (patches to add OO
<p>On Wednesday, Leo Tötsch announced a feature slush (patches to add OO
features were still being accepted) in anticipation of a release. The
patch rate increased as people got on with fixing up failing tests on
various platforms, improving documentation, and improving OO
Expand Down
Expand Up @@ -50,7 +50,7 @@
implementation of the m4 macro language.</p>
<p><a href='http://groups.google.com/groups?selm=rt-3.0.8-27316-80413.12.8637727827157@perl.org' target='_blank'>groups.google.com</a></p>
<a name='Use vim?'></a><h2>Use vim?</h2>
<p>I don't use vim, but it seems that Leo Tötsch does. He's added some
<p>I don't use vim, but it seems that Leo Tötsch does. He's added some
handy dandy vim syntax files for IMC code. If you're a vim user you
might like to check it out. Leo points out that the syntax tables might
well be handy if you don't know all 1384 opcode variants by heart.</p>
Expand Down
8 changes: 4 additions & 4 deletions source/archive/list-summaries/2004/p6summary.2004-03-14.html
Expand Up @@ -41,7 +41,7 @@
<p>Dan has come to the view that we need an alternative, light weight,
calling convention for calling vtable opcode functions; the idea being
that this should speed up objects a tad. He asked for suggestions.</p>
<p>Leo Tötsch wasn't convinced that we really need special calling
<p>Leo Tötsch wasn't convinced that we really need special calling
conventions, arguing (with numbers) that it would be best to
concentrate on speeding up object instantiation by optimizing object
layout. Simon Glover agreed with him, noting that simply changing the
Expand All @@ -51,7 +51,7 @@
<a name='Summary Correction'></a><h2>Summary Correction</h2>
<p>Last week I said that we can't yet do delegated method calls for vtable
functions with objects. Leo pointed out that, actually, we can now. Leo
also disclaimed any responsibility for helping Brent Royal-Gordon (né
also disclaimed any responsibility for helping Brent Royal-Gordon (né
Dax?) fix up the support functions for Parrot::Config, though Brent
later claimed that he was merely the person doing the typing...</p>
<p>Jerome Quelin noted that <b><i>parrotbug</i></b> has already reached version 0.2.1
Expand Down Expand Up @@ -95,7 +95,7 @@
in, you can find it at <code>library/objecthacks.imc</code></p>
<p><a href='http://groups.google.com/groups?selm=200403091934.50795.parrot@jensbeimsurfen.de' target='_blank'>groups.google.com</a></p>
<a name='Implementing stat?'></a><h2>Implementing <code>stat</code>?</h2>
<p>Leo Tötsch proposed a <code>stat</code> opcode for finding out about things in the
<p>Leo Tötsch proposed a <code>stat</code> opcode for finding out about things in the
filesystem. He outlined a proposed interface. Dan agreed that we'd need
something, but that Leo's proposal was far too unix-centric to work for
a cross platform platform like Parrot. He suggested going back to first
Expand Down Expand Up @@ -218,7 +218,7 @@
to have a 'call class method' operation. Paolo Molaro pointed out that
most of this stuff only becomes a real issue when you have to deal with
objects implemented in one language calling methods on objects
implemented in a different one. Leo Tötsch explained Parrot's current
implemented in a different one. Leo Tötsch explained Parrot's current
(somewhat confusing to these eyes) hierarchy where:</p>
<ul>
<li><a name='A ParrotClass isa delegate PMC'></a>A ParrotClass isa delegate PMC</li>
Expand Down
14 changes: 7 additions & 7 deletions source/archive/list-summaries/2004/p6summary.2004-03-21.html
Expand Up @@ -50,7 +50,7 @@
<p><a href='http://groups.google.com/groups?selm=200403151648.i2FGm5A04234@vendian.org' target='_blank'>groups.google.com</a></p>
<a name='GC issues'></a><h2>GC issues</h2>
<p>Jens Rieks continues to stress the object stuff (he's working on writing
an EBNF parser). He posted a test to the list that led Leo Tötsch to
an EBNF parser). He posted a test to the list that led Leo Tötsch to
find and fix 3 bugs in the Garbage Collector's DOD phase.</p>
<p><a href='http://groups.google.com/groups?selm=200403151937.19883.parrot@jensbeimsurfen.de' target='_blank'>groups.google.com</a></p>
<a name='Will's questions'></a><h2>Will's questions</h2>
Expand Down Expand Up @@ -128,7 +128,7 @@
<p><a href='http://groups.google.com/groups?selm=FB17458A-783C-11D8-8121-000393A6B9DA@mac.com' target='_blank'>groups.google.com</a></p>
<a name='Continuation usage'></a><h2>Continuation usage</h2>
<p>Jens Rieks and Piers Cawley both had problems with continuations. Leo
Tötsch tried explain what they were doing wrong. There seemed to be a
Tötsch tried explain what they were doing wrong. There seemed to be a
fair amount of talking past each other going on (at least, that's how
it felt from my point of view) but I think communication has been
established now. Hopefully this will lead to a better set of tests for
Expand All @@ -150,14 +150,14 @@
<a name='Meanwhile, in perl6-language'></a><h1>Meanwhile, in perl6-language</h1>
<a name='Hash subscriptor'></a><h2>Hash subscriptor</h2>
<p>At the back end of the previous week, Larry introduced the idea of
subscripting hashes with <code>%hash«baz»</code> when you mean
subscripting hashes with <code>%hash«baz»</code> when you mean
<code>%hash{'baz'}</code>. This surprised John Williams (and others I'm sure, it
certainly surprised me, but it's one of those &quot;What? Oh... that makes a
lot of sense&quot; type surprises.) Larry explained his thinking on the
issue. Apparently it arose because <code>:foo('bar')</code> was too ugly to live,
but too useful to die, so <code>:foo«bar»</code> was invented, and once you have
that, it is but a short step to <code>%foo«bar»</code>. (If you've not read
Exegesis 7, you probably don't know that <code>:foo«bar»</code> is equivalent to
but too useful to die, so <code>:foo«bar»</code> was invented, and once you have
that, it is but a short step to <code>%foo«bar»</code>. (If you've not read
Exegesis 7, you probably don't know that <code>:foo«bar»</code> is equivalent to
<code>foo =&gt; 'bar'</code>, but you do now.) John wasn't convinced though. It
remains to be seen if he's convinced Larry.</p>
<p>Larry: unfortunately it's an unavoidable part of my job description to
Expand All @@ -179,7 +179,7 @@
'broken bar' glyph as an infix form of the <code>zip</code> operator. Which I
didn't quite realise as I skimmed the thread during the week because
courier doesn't seem to distinguish between the broken bar and the
standard bar. Larry later suggested using the yen (¥) symbol instead,
standard bar. Larry later suggested using the yen (¥) symbol instead,
which has the advantage of looking a little like a zipper. I really
hope that firms up from suggestion to design call.</p>
<p><a href='http://groups.google.com/groups?selm=200403200148.i2K1mJkG001378@ms-smtp-02-eri0.southeast.rr.com' target='_blank'>groups.google.com</a></p>
Expand Down

0 comments on commit 555c1b7

Please sign in to comment.