16
1
I remember people saying that code size should be measured in bytes, and not in characters, because it's possible to store information with weird Unicode characters, which have no visual meaning.
How bad can it be?
In this challenge, you should output the following Lorem Ipsum text, taken from Wikipedia:
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Please specify the number of characters (not bytes) in your code. Code with the minimal number of characters wins.
Your code should only contain valid Unicode characters, as described here, that is:
- Code points up to U+10FFFF
- No surrogates (the range D800–DBFF is forbidden)
- No characters FFFE and FFFF
- No null characters (code 0)
If your code cannot be displayed, provide a version with offending characters redacted, and a hexdump.
Some notes:
- The output must be one long line (445 characters). If your system cannot do that (e.g. you're printing it on paper), output a closest approximation. Trailing linebreaks don't matter.
- Built-in functions that generate Lorem Ipsum text are not allowed
- Please specify a valid text encoding for your code, if relevant
2Sadly
=lorem()
in MS Word doesn't output the right version – BlackCap – 2016-09-08T16:18:17.67343 answers so far specifying bytes. Methinks some people may not have read the challenge – Robert Fraser – 2016-09-08T16:57:15.080
@RobertFraser: In my case it makes no difference as 1 byte = 1 char, so I might as well specify bytes as that's the standard. If I had earned any by using chars I would have specified thus :) Pretty sure the same is true for the other answers. – Emigna – 2016-09-08T16:59:49.307
From what ive seen many of the "golf" languages use their own encoding so the can already display most charecters they use as 1 byte. – gtwebb – 2016-09-08T17:46:20.377
1Is it permitted to make an http request? – Master_ex – 2016-09-08T18:05:05.510
If it's something like this, then no
– anatolyg – 2016-09-08T18:13:01.310@anatolyg: I thought so. I have to read the standard loopholes :-) – Master_ex – 2016-09-08T18:15:44.807
2
This feels like a dupe of the this challenge as there aren't any patterns in the text?
– FryAmTheEggman – 2016-09-08T19:05:55.187It's close, but this one has fewer restrictions. If I were to invent a great answer to this challenge, and it were closed as duplicate, could I post it as an answer on that challenge? I guess the answer is "maybe". I'll leave it it to the community to decide whether this one is a duplicate. – anatolyg – 2016-09-08T19:17:50.677
Is a trailing space in the output permitted? – ETHproductions – 2016-09-08T19:19:13.420
@ETHproductions I guess it would be unfair to existing answers to allow trailing space. So no, only trailing linebreaks are OK. – anatolyg – 2016-09-08T19:21:37.987
Is it allowed to run alert($('blockquote')[0].innerText) . It works only if the URL belongs to https://en.wikipedia.org/wiki/Lorem_ipsum
– Jörg Hülsermann – 2016-09-08T22:09:14.763To whoever marked this challenge as a duplicate - it's certainly not a duplicate of that challenge! It's not code-golf (see text for details), so the best solution will be different. – anatolyg – 2016-09-09T10:05:12.227
@anatolyg It's tagged as [code-golf]. If it's not, then remove that tag. – mbomb007 – 2016-09-09T15:01:26.593
[tag:code-golf] also covers shortest code by characters (see point 7 in the requirements list of the tag info). This is code golf, and thus it's still a dupe, since there aren't any patterns to exploit. – Mego – 2017-01-17T16:25:57.597