175100+ entries in 0.621s
mod6: when I do
the factorials in my head, i seem
to start with
the bigger end for some reason.
mod6: one
thing,
that i never really
thought about is going
the other direction; 1 * 2 * 3 ...
mod6: <+asciilifeform> also you forgot, in
the original,
to divide
the length of ffa by 64 (bits), yours will blow up instead of run, gcc by default does not give infinite stack << ah
thanks for making
the changes asciilifeform. bak now. will
try
this out...
phf: combining glyphs
to make national flags is yes yet another extension
erlehmann: phf unifont actually leaves out shitstains like arbitrarily combining glyphs
to make national flags.
phf: fwiw unifont is not even
the whole story. consider extensions like CTL, which allows you
to have special rendering for a sequence of glyphs. a completely separate
technology from ligatures and combining characters, but part of
the standard never
the less.
☟︎ erlehmann: it nicely complements what
they already have out of
the box
erlehmann: i suggest put
the following in your .XCompose if you use X11
erlehmann: e.g.
those who do not use ß / ẞ write “Der grosse Duden” instead of “Der große Duden”
erlehmann: in standard german, ß / ẞ / ss / SS are not ambiguous, but in german variants
that do not use ß / ẞ,
the ss / SS could be a digraph depending on context.
erlehmann: note
that postprocessing is always wrong.
☟︎ erlehmann: ch does not exist as unicode ligature, but as i understand distinguishing characters is one of
the problems unicode is at least intended
to solve. as soon as everyone uses Æ for “ AE”
the postprocessing is no longer needed.
jurov: they will just expect it
to work
erlehmann: instead of having
to postprocess ASCII
jurov: unicode has zillions if
these cases
jurov: erlehmann my language has such a delightful case of "ch" character. which is a "digraph" and
to be counted as one char.
erlehmann: also, comparing
two strings should be done bytewise, always. everything else is madness.
erlehmann: jurov converting case is locale-specific,
therefore better left undone.
☟︎ a111: Logged on 2017-03-23 18:21 mircea_popescu:
this notion
that i will support
the wintel FOR FREE is
the lolz of all
time.
jurov: "incorporating something in unicode does not increase processing complexity" orly? maybe unless you want
to do anything interesting with
the
text, like... count
the characters. or case convert. or detect whitespace. or compare
two strings. or...
erlehmann: in
those days, only ~21k characters were reserved for CJK
erlehmann: version 1 of unicode was designed
to keep under 16 bits
erlehmann: chinese, japanese, korean now share unihan, with all
the processing complexity and
technical debt incurred from
that
erlehmann: yes, but
this cost has already been incurred. unicode actually
tried
to prevent
too many new characters in
the past, leading
to misfeature han unification.
erlehmann: that
turns out
to be a problem with
the abysmally bad
TTF file format.
erlehmann: so if code does not care if
there exist 250 or 2500 or 250000 characters, why should i?
erlehmann: one point is
that incorporating something in unicode does not increase processing complexity by any means. i actually installed a new version of unifont on an old phone and instantly it could display all
the new characters.
erlehmann: asciilifeform i strongly suspect you do not distinguish between complexity and sheer numbers. i saw bloat always as referring
to needless complexity, size of something only as evidence, not as bloat itself.
erlehmann: some writing systems contain non-abstract symbols. all
the same
to me, as long as everything fits in 16×16 bits.
erlehmann: can it be
that your complaint is more with
the egyptian glyphs
than with unicode itself?
☟︎ erlehmann: also, for everyday communication i find E1, E2, E3, E4 etc. much better
than
trying
to pass around bitmaps
erlehmann: okay, but most of it. a special interest group (egyptologican geeks) used a glyph standard. unicode swallowed
that standard.
this is how it usually goes.
☟︎ erlehmann: what actually happened is
that people who wanted
to use hieroglyphs passed around codes such as A13 – a standard reference exists (gardiner's sign list)
that was incorporated into unicode
erlehmann: asciilifeform
the sole purpose of unicode is
to replace all other glyph standards. from
that follows all else, i.e. incorporation of wingdings, emoji, etc.
mod6: anyway, got some chores
to do, will have
to come back
to
this later.
mod6: ah,
that was used for some debugging
mod6: i dunno, just
the strict
types
thing.
mod6: ooh. for some reason, i didn't
think
that it could?
mod6: you want me
to post my code before I run
this again?
mod6: <+asciilifeform> which, btw, imho is intrinsically unsuitable for a fits-in-head rsatron, it is extremely gnarly and uses float approximations
that get magically unfudged back
to int, etc << ugh. right.
mod6: ok ima kill
this off
then
throw in some 1mb FZ
mod6: asciilifeform: entrenching
tool, aha.
mod6: sure, but perhaps, getting one close is good enough in
this case.
mod6: does
that have a name? ^
mod6: 1.326 + log(65536)/2*log(2) + (log(65536)/log(2) - 1.443)*65536 << during
this exercise, i started, very quickly
to see
this expansion pattern. was
thinking
there must be some square law
to predict
the probable size of
the outcome.
mod6: i'd rather have something sane
to read at
the end of
the journey.
a111: Logged on 2017-07-15 07:18 mod6:
this 65536 one is gonna run for a while i
think...
a111: Logged on 2017-07-15 07:26 mircea_popescu: btw, does asciilifeform know about
the right honorable
the lord brougham and vaux pc qc frs ?
jhvh1: asciilifeform:
The operation succeeded.