last day (15 days later) » 

11:22 PM
1
A: 𝘜𝘯𝘪𝘤𝘰𝘥𝘦 𝗠𝗮𝗿𝗸𝗱𝗼𝘄𝗻 F̲o̲r̲m̲a̲t̲t̲e̲r̲ (*Unicode* **Markdown** __Formatter__)

recursiveStax, 75 73 bytes â¢6=°┐♦#Ü─·█╦τ←‼╞↓₧nÿ╔ycD▬∙ô/╖ë«ë{S╙≡º²s&┌√♫▒τáG☼║╫←╗╣∩₧ÄΔπ_╧Φ↔m;Θ╗á*T♦l╗ Run and debug it online The basic approach is store the 4 types of formatting in a bit field, and then get the correct character offset from a lookup using the integer value. Only 8 values are in the ...

 
pfg
It seems like monospace underline is using bold italic instead of monospace
 
My mistake. I thought that that was a disallowed combination. I'll see about addressing that.
 
pfg
I guess I should make it more clear in my post. Underlines combine with anything
 
@pfg Hm, I guess I don't understand the requirement. What styles are combine-able with mono? There's no font that combines bold or italic with mono, so what should the behavior be?
 
pfg
It's the opposite, mono is combineable with underline, underline is combineable with everything else
 
11:22 PM
__mark__down This is the test case we're talking about right? It has bold and mono nested. What's the correct behavior for that?
 
pfg
Yeah. __mark__down should make 𝚖̲𝚊̲𝚛̲𝚔̲𝚍𝚘𝚠𝚗
 
That's exactly what my program does.
 
pfg
is it? 1 sec
for me for `down` mark `__mark__ down` I get 𝙙̲𝙤̲𝙬̲𝙣̲ ̲𝚖̲𝚊̲𝚛̲𝚔̲ 𝙢̲𝙖̲𝙧̲𝙠̲ 𝚍𝚘𝚠𝚗
here actually for the original test case __mark__ down
 
I think I might see what you're saying. The markdown formatter in this chat is making it tough.
HOld on.
 
pfg
it gives 𝙢̲𝙖̲𝙧̲𝙠̲ 𝚍𝚘𝚠𝚗 instead of 𝚖̲𝚊̲𝚛̲𝚔̲𝚍𝚘𝚠𝚗
 
11:25 PM
Is this one right?
 
pfg
wait oh I see
 
I do see a mistake now.
 
pfg
your run and debug link wasn't updated
 
Ok, I'll clean up my answer.
 
pfg
you might want to use this run and debug
wait no idk how to use that
but it has the old program in the run/debug link
 
11:31 PM
My post was messed up. It was using a byte count from the wrong version too.
I repasted all the programs and links using an additional test case for that combination.
Thanks for helping me understand.
 

last day (15 days later) »