thought

Translation somewhat of the ming on cover
whawngokenjunyutdoyunwan

More likely via other ming interpretations: How I see spring moon many human lotuses

Comments


Holmes says
The only one I don’t see coming out is whawngokenjunyutdoyunwan and your implementation has a space at the front, is that allowed?

Holmes says
Probably an issue for Seth. I have barely touched that stuff and don’t own it and if any are working then what I did is not broken.

Mark de LA says
seth 2016-01-18 11:06:03 [item 19697#42653]
seth 2016-01-18 11:10:29 [item 19697#42660]
like
like

Seth says
dA 2016-01-18 11:08:28 [item 19697#42656]
Well anyway, the current tag parser has issues with ambiguous recursion … but I don’t see anything ambiguous in these.
Mark 2016-01-18 11:10:09 [item 19697#42659]
this has been the ming dictionary protocol for a very long time – tag parser?
Mark 2016-01-18 11:11:03 [item 19697#42661]
It is sporatic – sometimes works & sometimes doesn’t – the [ ] seems broken
probably got something to do with copy paste carrying markup that you are not seeing.  click on the source button and examine what actually ends up between the [ ].  frequently what i have been doing is when a commmand is not working, i edit the comment and click source and manually strip out the markup.  so there is a work around untill tigger get’s a chance to fix the parser.  it may not be just an easy fix.   

Holmes says
dA 2016-01-18 11:08:28 [item 19697#42656]
Well anyway, the current tag parser has issues with ambiguous recursion … but I don’t see anything ambiguous in these.
Mark 2016-01-18 11:10:09 [item 19697#42659]
this has been the ming dictionary protocol for a very long time – tag parser?
dA 2016-01-18 11:13:02 [item 19697#42663]
Why do you write that as a challenge with a question mark? You know what tags are. You know that anything that interprets text like that is a parser. If you want to talk about something based on what we know, then do so. Stop baiting arguments and challenges.
Mark 2016-01-18 11:19:17 [item 19697#42667]
the ming dictionary is not a tag – maybe a different protocol
Nope. It’s a tag. Just looked. Here’s the code. Right in there with the rest of the tags.
            switch ($w) {
            case "group":
                $type=$w;
                break;
            case "tag":
                $type=$w;
                break;
            case "tags":
                $type="tag";
                break;
            case "title":
                $type=$w;
                break;
            case "search":
                $type = $w;
                break;
            case "item":
            case "tho":
                $type=$w;
                break;
            case "permalink":
                $type="item";
                break;
            case "google":
                $type=$w;
                break;
            case "uri":
                $type=$w;
                break;
            case "url":
                $type='uri';
                break;
            case "ming":
                $type='ming';
                break;
            case "mingchar":
                $type='mingchar';
                break;


 

Seth says
seth 2016-01-18 11:20:31 [item 19697#42668]
whawngokenjuntutdoyunwansum … should work … just make sure you don’t hit more than just one space before you start typing ming.

Seth says
seth 2016-01-18 11:20:31 [item 19697#42668]
Mark 2016-01-18 11:23:23 [item 19697#42671]
yes like i say if it doesn't not work … just look at the source code … and it should be obvious.

Seth says
like

Mark de LA says
Mark 2016-01-18 11:38:31 [item 19697#42687]
it is putting a space in that I am not . I have to put a space between the word mingchar and the first ming word. That’s the protocol for most bracketed expressions.  I have even occasionaly used a label like [this: mingchar sum]
which seems now to work at least for single characters.

Mark de LA says

Mark de LA says
Mark 2016-01-18 11:38:31 [item 19697#42687]
it is putting a space in that I am not . I have to put a space between the word mingchar and the first ming word. That’s the protocol for most bracketed expressions.  I have even occasionaly used a label like [this: mingchar sum]
seth 2016-01-18 11:41:36 [item 19697#42690]
like

Mark de LA says
chaychun this is ff , previous is opera & i started with chrome

Mark de LA says
whawngokenjuntutdoyunwansum

Seth says
Mark 2016-01-18 11:54:31 [item 19697#42700]
wtf is going on the word m i n g c h a r seems poisonous & moves the cursor in FF
Mark 2016-01-18 11:54:58 [item 19697#42702]
try it
 
mingchar … or m i n g c h a r … looks good so far … and i am in FF. 

Seth says
yeah keyboard still doing it … do you have a spare that you could try?

Seth says
seth 2016-01-18 11:54:45 [item 19697#42701]
there are two work arounds proposed here ..
  1. nathans – just click <source> and type in your mingchar directly into the source code
  2. mine – type it in, i have found it usuallly works,  if it does not, click <source> and strip out the obvious garblely gook betwee [ and ]. 
Come on now … this is an alpha dev area … don’t be a gweebe!
seth 2016-01-18 12:01:30 [item 19697#42707]
like
seth 2016-01-18 12:01:36 [item 19697#42708]
like
dA 2016-01-18 12:06:53 [item 19697#42710]
Well frankly, the tag parser should sanitize the string for html characters. But just sticking that in one place could break it in others right now because the same code loops over itself and some places already have character stripping and unencasing. The whole tag area needs a rethink and then a rewrite and a test battery to go with it. With it being so simple to input ming’s with the source view I don’t see that touching the code right now is worth the possible problems.
like

Holmes says
The editor uses completely different modules for FF, Chrome, etc. So I am not surprised there is a difference between browsers. A &nbsp; is valid anywhere in HTML so the editor can put one in anytime it things it needs one based on all kinds of things, length of the line, etc. The easy solution is to use the source view. That should work flawlessly and easily every time. A solution down the road can be a rewrite of the tag parser.

As to cursor jumping around … I have been using FF a lot more lately and noticed that happening in FF only sometimes. It seems to be a bug in the spell checker for FF. If it is happening on you, just turn off the spell checker until you are done with the posting.  i.e. On the ABC tool button, disable SCAYT. Maybe a fix will come out for the spell check plugin for FF soon.

Seth says
seth 2016-01-18 12:16:57 [item 19697#42717]

there are two work arounds proposed here ..

  1. nathans – just click <source> and type in your mingchar directly into the source code
  2. mine – type it in, i have found it usuallly works,  if it does not, click <source> and strip out the obvious garblely gook betwee [ and ]. 
like

Seth says
seth 2016-01-18 11:47:22 [item 19697#42695]
you got … reading off the <source> code … so somthing happend differently there between mingchar and chay … and also between chun and sum… but not between chay and chun.   go figure …

anyway you now know the work around … ok?
Mark 2016-01-18 11:50:09 [item 19697#42697]
Mark 2016-01-18 11:51:02 [item 19697#42698]
[ cmingchar sum
Mark 2016-01-18 11:53:42 [item 19697#42699]
when I type the word  the cursor moves to in front of it. mingchar

 
seth 2016-01-18 11:57:56 [item 19697#42703]
wierd shit happens … you might want to go wash your hands … laugh
Mark 2016-01-18 12:27:35 [item 19697#42722]
I lick my fingers instead (or wipe them on the dog) –  is that not OK? laughing
like

Seth says
dA 2016-01-18 11:45:32 [item 19697#42693]
Why don’t you simply always put your ming characters in using the source view? Then they will work like you expect.
Mark 2016-01-18 12:25:40 [item 19697#42720]
seth 2016-01-18 12:26:41 [item 19697#42721]
yes
Mark 2016-01-18 12:32:36 [item 19697#42724]
like

Seth says
dA 2016-01-18 11:45:32 [item 19697#42693]
Why don’t you simply always put your ming characters in using the source view? Then they will work like you expect.
Mark 2016-01-18 12:25:40 [item 19697#42720]
seth 2016-01-18 12:26:41 [item 19697#42721]
yes
Mark 2016-01-18 12:32:36 [item 19697#42724]
 
Mark 2016-01-18 12:34:31 [item 19697#42726]
ok that worked . Still want it to work like any other protocol like google HTML sucks laugh
it will … it will … it will … tips gladly accepted … takes lots of people to lift a heavy stone. 

Seth says
dA 2016-01-18 11:45:32 [item 19697#42693]
Why don’t you simply always put your ming characters in using the source view? Then they will work like you expect.
Mark 2016-01-18 12:25:40 [item 19697#42720]
seth 2016-01-18 12:26:41 [item 19697#42721]
yes
Mark 2016-01-18 12:32:36 [item 19697#42724]
 
Mark 2016-01-18 12:34:31 [item 19697#42726]
ok that worked . Still want it to work like any other protocol like google HTML sucks laugh
Mark 2016-01-18 12:36:22 [item 19697#42728]
hmmm… that doesn’t work either.
Maybe s google poodle does
hmmm … google html sucks … no stickey fingers here … well we will see.

or google HTML sucks ….

Seth says
oh wait … you wanted the command spec …

[string COMMAND argument]   … is it not just that

Commands that i remember are

group
tag
title
item
google
mingchar
search

let me see if search works search commands

 

Seth says
dA 2016-01-18 11:45:32 [item 19697#42693]
Why don’t you simply always put your ming characters in using the source view? Then they will work like you expect.
Mark 2016-01-18 12:25:40 [item 19697#42720]
seth 2016-01-18 12:26:41 [item 19697#42721]
yes
Mark 2016-01-18 12:32:36 [item 19697#42724]
 
Mark 2016-01-18 12:34:31 [item 19697#42726]
ok that worked . Still want it to work like any other protocol like google HTML sucks laugh
Mark 2016-01-18 12:36:22 [item 19697#42728]
hmmm… that doesn’t work either.
Maybe s google poodle does
Mark 2016-01-18 12:37:32 [item 19697#42730]
pondering got a group river does not exist but it looks parsed.
seth 2016-01-18 12:40:29 [item 19697#42732]
?
dA 2016-01-18 12:44:41 [item 19697#42734]
I really don’t know what the full tag spec is, so I don’t know what to even try to fix if there is a problem with the code and not Mark’s usage. Normally I can figure out spec by reading code, but the tag parser is a recurring loop of double switch cases followed by another switch case from the results of the first. You practically have to mentograph it just to figure out what one tag does.

So anyway, could we get some tag spec written or found please?
seth 2016-01-18 12:54:19 [item 19697#42735]
well, or course i forgot more about that area than i ever knew laugh.

but i don’t see the mystery … it is just which URLs we are supporting … ok let me think out loud …

domain/ →  going to be the front page HTML presentation
domain/group →  group home page
domain/group/tag/TAG  → group tag room
domain/tag/TAG → river tag room
domain/item/NUMBER → a permalink
domain/user → the news
domain/cartoons → directly to the meme writer

there are not really many more …

is that what you wanted?
dA 2016-01-18 13:06:23 [item 19697#42738]
That’s a start, but the top level swtich case says there are quite a few more. I don’t know what they all do after the top. There are google and uri and url and the ming stuff etc.

See 19700 and you can edit it directly. I won’t be.
like ok i’ll check the ones we are not really using … and/or are alterntives … and edit that thought … when tuit

Mark de LA says
seth 2016-01-18 13:03:16 [item 19697#42737]
does this work [see also tag commands] ?
seth 2016-01-18 13:11:11 [item 19697#42740]
as opposed to … see also commands ?
I think the syntax I have been using is [see also: tag commands]

Mark de LA says
seth 2016-01-18 12:16:08 [item 19697#42715]
mark … are you reading what others are saying here?   why not use one of the work arounds that we are proposing?  …. ??????? …..
Mark 2016-01-18 13:15:50 [item 19697#42742]
I tried them & my workaround is to link directly to the ming dictionary & bypass the problem.
seth 2016-01-18 13:17:57 [item 19697#42744]
like
Mark 2016-01-18 13:41:51 [item 19697#42747]
Workaround on character size as well – just a big pain:
seth 2016-01-18 13:46:45 [item 19697#42750]
well i don’t see why Tigger cannot put in my suggested size change search size mingchar

ok found it in the search … http://www.fastblogit.com/item/19495#41728
Mark 2016-01-18 13:57:10 [item 19697#42755]
Just seems to be another way to screw up the fragile parsers.
Can also make them bigger this way.
seth 2016-01-18 14:10:22 [item 19697#42767]
come on now … we are trying to make this work for you … did you not notice?
like

Seth says
seth 2016-01-18 12:16:08 [item 19697#42715]
mark … are you reading what others are saying here?   why not use one of the work arounds that we are proposing?  …. ??????? …..
Mark 2016-01-18 13:15:50 [item 19697#42742]
I tried them & my workaround is to link directly to the ming dictionary & bypass the problem.
seth 2016-01-18 13:17:57 [item 19697#42744]
like
Mark 2016-01-18 13:41:51 [item 19697#42747]
Workaround on character size as well – just a big pain:
seth 2016-01-18 13:46:45 [item 19697#42750]
well i don’t see why Tigger cannot put in my suggested size change search size mingchar

ok found it in the search … http://www.fastblogit.com/item/19495#41728
dA 2016-01-18 13:56:19 [item 19697#42754]
I looked at your suggested fix below. It does not seem the right way. Rather, a class should be added at that spot for ming characters and all explicit styling removed. Then the class can be changed in the stylesheet to match with any display context including possible changes on mobile devices. As a general rule, one should never use style= direclty in generated html if there is any way to avoid it.

well it is rediculously easy to do

 $s=$s . sprintf('<img src="https://icybermind.net/media/ming/%s" alt="%s"  border="0" />',$i,$chr,$char);

just insert a height:60px in the img tag above in common.php

seth 2016-01-18 14:14:00 [item 19697#42770]
like
dA 2016-01-18 14:27:08 [item 19697#42774]
Done. Height 60px. Will only apply to new ones made after now.
seth 2016-01-18 14:28:43 [item 19697#42775]
dA 2016-01-18 14:32:13 [item 19697#42776]
Also put this hack in to convert &nbsp; at point of final use, which seems safe enough. But let me know if there are side effects.

            $mings = explode(' ', preg_replace('/&nbsp;/', ' ', $object));

 
OMG

Holmes says
Mark 2016-01-18 17:19:30 [item 19697#42805]
Mark 2016-01-18 17:22:17 [item 19697#42806]
Mark 2016-01-18 17:23:18 [item 19697#42807]
They all look good!

Holmes says
Mark 2016-01-18 17:19:30 [item 19697#42805]
Mark 2016-01-18 17:22:17 [item 19697#42806]
Mark 2016-01-18 17:23:18 [item 19697#42807]
Mark 2016-01-18 17:25:53 [item 19697#42809]
What size do you want them? In pixels? They are 60px right now.

Mark de LA says
 this is about 45 for the picture

Seth says
like

Mark de LA says
Mark 2016-01-18 17:19:30 [item 19697#42805]
Mark 2016-01-18 17:22:17 [item 19697#42806]
Mark 2016-01-18 17:23:18 [item 19697#42807]
Mark 2016-01-18 17:25:53 [item 19697#42809]
seth 2016-01-18 17:28:09 [item 19697#42811]
now the characters show smaller on the screen … did you not notice that?
like

Seth says
dA 2016-01-18 17:48:06 [item 19697#42820]
Final hack $m = explode(' ', trim(preg_replace('/(&nbsp;|\s+)/', ' ', $x)));
Hurray for regular expressions! The ultimate hack too!
seth 2016-01-18 19:41:38 [item 19697#42825]
yes i have heard of it’s praise smug 

what does this particular one do for us?
dA 2016-01-18 19:48:12 [item 19697#42827]
Um, what this is all about in this thought. Made  mings work. Got rid of &nbsp;’s and extra spaces too that were mucking up the explode.
yes ironic