<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thank you Ken for posting.</p>
<p>So if anybody wonders "why is it that some nameless person at the
Trademark Office pulled this case from pub on October 10?" the
answer seems likely to be "Ken told them about it for the second
or third or fourth time on October 7 and they finally sort of paid
attention to it". Except whoever was doing the "paying attention"
did not really pay attention. Because that person then released
the case back into pub without actually correcting the Trademark
Office mistake.</p>
<p>This particular problem falls into a very easy-to-spell-out
general category, namely "applications that have a standard
character claim but where the mark contains at least one character
that is not a standard character".</p>
<p>It is decades ago that I did my first computer programming (in
Fortran). Since then I have done lots more computer programming
in several programming languages. </p>
<p>For a couple of years now I only sort of vaguely knew of the
existence of Unicode, but Ken's postings within the past year or
so prompted me to gain some familiarity with Unicode. <br>
</p>
<p>I'd guess there are at least a dozen members of this listserv
(including myself) who, given developer-level access within the
Trademark Office, could write a simple report generator computer
program in any of half a dozen programming languages that would
instantly generate a report listing every case in this general
category. What I know with absolute certainty is that there is no
way the Trademark Office would ever accept such help, even if
provided free of charge, for the simple reason that it would be
too close to admitting error and too close to admitting that
anyone outside the Trademark Office could do something better than
those within the Trademark Office.</p>
<p>The report generator, if only it were to be allowed to come into
existence (probably free of charge), could then be run once a week
or even once a month, and the nameless-pull-from-pub-person could
be handed the list and told to keep trying until they would make
it so that the cases on the list did not show up on the next
report.</p>
<p>This is the sort of thing that computers are supposed to be good
at, given the opportunity.</p>
<p>Carl</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 10/12/2025 5:15 AM, Ken Boone wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DS0PR07MB103548BD3FEBFE092CF1D5C9CD5EDA@DS0PR07MB10354.namprd07.prod.outlook.com">
<div class="elementToProof">
As it happens, I also have been keeping an eye on 99181596
OMMISIMQIST\u200b. Following is an October 7th
<b><i>alert </i></b>that I provided to the USPTO, where
99181596 OMMISIMQIST is the 3rd trademark on the list. (I see
some evidence of activity to correct 3 of the 20 trademarks
listed. For example, the 1st trademark 99264792 LA FRANCÉ LF is
no longer a standard character mark. BTW, the search <span><b>WD:(
*\u200b* )</b></span><b>
</b>with that ZWSP between the asterisks now retrieves 3
trademarks: 99283545 \u200b<b>RAPIDREST</b>, 99181596
<b>OMMISIMQIST</b>\u200b, and 98111449 <b>KY\u016a\u200b\u200b\u200b\u200b\u200b\u200b\u200bR</b>.</div>
<div class="elementToProof">
<br>
</div>
<hr>
<div class="elementToProof" id="divRplyFwdMsg">
<div class="elementToProof">
<b>From:</b> Ken Boone <a class="moz-txt-link-rfc2396E" href="mailto:boondogles@hotmail.com"><boondogles@hotmail.com></a><br>
<b>Sent:</b> Tuesday, October 7, 2025 9:38 AM<br>
<b>To:</b> TMFeedback <a class="moz-txt-link-rfc2396E" href="mailto:tmfeedback@uspto.gov"><tmfeedback@uspto.gov></a><br>
<b>Subject:</b> Challenging Trademarks In The Publication
Queue</div>
<div class="elementToProof">
</div>
</div>
<div class="elementToProof">
By my checks, 5 of the 16 challenging trademarks that I reported
on September 26th have been addressed. </div>
<div class="elementToProof">
<br>
</div>
<div class="elementToProof">
Today's list includes the 11 challenging trademarks that were
not addressed plus 9 new challenging trademarks (20 total
trademarks), though one trademark has registered since initially
reported.</div>
<div class="elementToProof">
<br>
</div>
<table id="table_0">
<tbody>
<tr>
<td>
<div class="elementToProof">
<span>#</span></div>
</td>
<td>
<div class="elementToProof">
<span>SN</span></div>
</td>
<td>
<div class="elementToProof">
<span>Wordmark</span></div>
</td>
<td>
<div class="elementToProof">
<span>Drawing</span></div>
</td>
<td>
<div class="elementToProof">
<span>Comment</span></div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
1</div>
</td>
<td>
<div class="elementToProof">
99264792</div>
</td>
<td>
<div class="elementToProof">
LA FRANCÉ LF</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 99264792" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The drawing and description of mark [The mark consists
of The mark consists of the mark "LAFRANCE" in a
stylized font, with an accent above the letter "E". The
stylized abbreviation \u201cLF\u201d is superimposed above the
word \u201cLAFRANCE.\u201d.] contradict the standard character
mark claim. Also, correct the repetition of "The mark
consists of" in the description of mark.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
2</div>
</td>
<td>
<div class="elementToProof">
99194118</div>
</td>
<td>
<div class="elementToProof">
O\u041a</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 99194118" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The letter \u041a is the Unicode character with decimal value
1050 (Cyrillic Capital Letter Ka), not the standard
character K. I doubt the applicant was aware of the
presence of the unusual Cyrillic letter \u041a. Substitute
the ordinary K for the Cyrillic letter \u041a; else, add the
appropriate design code for Cyrillic letters.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
3</div>
</td>
<td>
<div class="elementToProof">
99181596</div>
</td>
<td>
<div class="elementToProof">
OMMISIMQIST\u200b</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 99181596" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
How many characters do you see in the wordmark? Just
11? Actually, there are 12. There is an unusual
Unicode character with decimal value 8203 ( the ZERO
WIDTH SPACE, a non-printing character that can be used
to indicate a potential line break opportunity within a
word or phrase, without introducing a visible space or
hyphen) appended to the wordmark. Since the ZERO WIDTH
SPACE is not included in the standard character set,
delete this ZERO WIDTH SPACE from the wordmark.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
4</div>
</td>
<td>
<div class="elementToProof">
99154626</div>
</td>
<td>
<div class="elementToProof">
S&DENT</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 99154626" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The drawing is poorly cropped, plus the description of
mark [The mark consists of the stylized wording
"S&DENT".] indicates this is stylized text, not a
standard character mark.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
5</div>
</td>
<td>
<div class="elementToProof">
99145834</div>
</td>
<td>
<div class="elementToProof">
DAPHOO FORCE</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 99145834" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
Tthe drawing and description of mark [The mark consists
of the words "DAPHOO FORCE" in stylized letters below a
lotus flower. Going across the lotus flower is an EKG
heartbeat line which turns into a running stick
figure.] contradict the standard character mark claim.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
6</div>
</td>
<td>
<div class="elementToProof">
99108096</div>
</td>
<td>
<div class="elementToProof">
GOCAN</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 99108096" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The contradictory and obsolete description of mark [The
mark consists of the stylized wording "GOCAN" with a
design of a circular pattern featuring stylized
depictions of a mountain landscape, full moon, and
roadway in front of the wording.] for this standard
character mark should be deleted.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
7</div>
</td>
<td>
<div class="elementToProof">
99097553</div>
</td>
<td>
<div class="elementToProof">
SPµ</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 99097553" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The wordmark (SPµ) is inconsistent with the description
of mark (The mark consists of the stylized wording
"SP\u03c0".). </div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
8</div>
</td>
<td>
<div class="elementToProof">
99027509</div>
</td>
<td>
<div class="elementToProof">
MS MARSHEIK</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 99027509" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The drawing and description of mark [The mark consists
of the stylized letters "MS" in a handwritten, cursive
font, where the letters are interconnected. Below the
letters, there is a horizontal line, beneath which
appears the stylized wording "MARSHEIK".] contradict
the standard character mark claim.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
9</div>
</td>
<td>
<div class="elementToProof">
98931863</div>
</td>
<td>
<div class="elementToProof">
PALE TRADING CO.</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 98931863" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The description of mark [The mark consists of standard
characters without claim to any particular font style,
size, or color.] indicates this text & design
application is really a standard character mark. Change
the mark drawing code to standard character mark and
delete the obsolete 26.09.21 design code.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
10</div>
</td>
<td>
<div class="elementToProof">
98912015</div>
</td>
<td>
<div class="elementToProof">
HAVEN</div>
</td>
<td>
<div class="elementToProof">
<br>
<img height="347" width="268" id="x_markImage"
alt="Trademark image" moz-do-not-send="true"></div>
<div class="elementToProof">
</div>
</td>
<td>
<div class="elementToProof">
Published 9/16/2025 as a typed drawing mark, except the
era for typed drawings ended 1 November 2003, so this
should have been a standard character mark when
published, except there is a design element in the
drawing. Also, the drawing has excess blank space above
and below the mark that could be cropped out.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
11</div>
</td>
<td>
<div class="elementToProof">
98875872</div>
</td>
<td>
<div class="elementToProof">
W.E.L.L. NEWS \u2015 WELLNESS, EATING, LIVING, &
LEARNING.</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 98875872" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The \u2015 character is the Unicode character with the
decimal value 8213, a Horizontal Bar character, but
since it is not a standard character, shouldn't the
USPTO substitute a similar valid standard character?</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
12</div>
</td>
<td>
<div class="elementToProof">
98790010</div>
</td>
<td>
<div class="elementToProof">
SINCE 1968 BUGANGOK A PREMIUM SUNDAEGUK PASSED DOWN
THROUGH GENERATIONS</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 98790010" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The drawing and description of mark [The mark consists
of the stylized Chinese character meaning wealth in a
circle all in black with slightly extended horizontal
lines on both the left and right sides with the words
SINCE 1968 in black underneath; the word BUGANGOK in
black and the stylized Korean characters meaning a
nation located in the east, each Korean character in
white and being arranged in a column direction on a red
square background next to the word BUGANGOK, both of
which are placed underneath the words SINCE 1968; the
phrase "A premium sundaeguk passed down through
generations" in black is underneath BUGANGOK and the
Korean characters.] contradict the standard character
mark claim.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
13</div>
</td>
<td>
<div class="elementToProof">
98015467</div>
</td>
<td>
<div class="elementToProof">
CARWELL</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 98015467" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The obsolete design code [07.11.07 - Highways with lines
or dividers; intersections (roads) with lines or
dividers; Roads with lines or dividers; Streets with
lines or dividers] should be deleted for this standard
character mark.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
14</div>
</td>
<td>
<div class="elementToProof">
88463388</div>
</td>
<td>
<div class="elementToProof">
NUTREETION</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 88463388" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The obsolete description of mark [The mark consists of
"NUTREETION" in white font encased in Circle filled with
Green color.] should be deleted for this standard
character mark.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
15</div>
</td>
<td>
<div class="elementToProof">
79418788</div>
</td>
<td>
<div class="elementToProof">
\u0391\u039c\u039f\u0399</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 79418788" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The search CM:amoi does NOT retrieve this trademark.
Why? There are Unicode Greek characters (that look like
A-Z standard characters) in the wordmark. Without the
Greek characters design code, the current wordmark is
deceptive and could impact searching for this STYLIZED
TEXT mark.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
16</div>
</td>
<td>
<div class="elementToProof">
79416509</div>
</td>
<td>
<div class="elementToProof">
GX\uff65SONIC STREAM</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 79416509" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
Substitute the standard character · for \u2022 ( the
Unicode character with decimal value 65381 [Halfwidth
Katakana Middle Dot?] that is NOT in the Standard
Character Set) in the wordmark for this Standard
Character Mark?</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
17</div>
</td>
<td>
<div class="elementToProof">
79408569</div>
</td>
<td>
<div class="elementToProof">
RILASTIL</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 79408569" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The drawing and description of mark [The mark consists
of standard characters without claim to any particular
font style, size, or color.] contradict the current
STYLIZED TEXT mark drawing code.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
18</div>
</td>
<td>
<div class="elementToProof">
79408087</div>
</td>
<td>
<div class="elementToProof">
FREEZETECH \u0391</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 79408087" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
Scheduled for publication, considering the in the
drawing and the description of mark [The mark consists
of the stylized wording FREEZETECH A with the lower case
letter "A" taking the form of the Greek letter alpha.],
isn't the design code 28.01.05 - Alpha (Greek letter)
appropriate for this STYLIZED TEXT application?</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
19</div>
</td>
<td>
<div class="elementToProof">
79404822</div>
</td>
<td>
<div class="elementToProof">
KOOKA\u0407</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 79404822" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The final letter \u0407 is the Unicode character with the
decimal value 1031 , the CYRILLIC CAPITAL LETTER YI. The
search WD:*\u0407* AND MD:4 using this CYRILLIC CAPITAL
LETTER YI retrieves only this KOOKA\u0407 trademark, while
the WD:*Ï* AND MD:4 search using the standard character
Ï retrieves over 3.7 million trademarks. Revise the
wordmark for this pending trademark to use the standard
character Ï; else, add the Cyrillic characters design
code.</div>
</td>
</tr>
<tr>
<td>
<div class="elementToProof">
20</div>
</td>
<td>
<div class="elementToProof">
79337527</div>
</td>
<td>
<div class="elementToProof">
ZIGZAG</div>
</td>
<td>
<div class="elementToProof">
<img alt="Image for 79337527" moz-do-not-send="true"> </div>
</td>
<td>
<div class="elementToProof">
The drawing and description of mark [The mark consists
of the stylized wording "ZIGZAG."] contradict the
standard character mark claim.</div>
</td>
</tr>
</tbody>
</table>
<div class="elementToProof">
<br>
</div>
<div class="elementToProof">
The search SN:( 99264792 99194118 99181596 99154626 99145834
99108096 99097553 99027509 98931863 98912015 98875872 98790010
98015467 88463388 79418788 79416509 79408569 79408087 79404822
79337527 ) retrieves these 20 challenging trademarks.</div>
<div class="elementToProof">
<br>
</div>
<div class="elementToProof">
<br>
</div>
<div class="elementToProof" id="x_Signature">
<div class="elementToProof">
Hope this helps,</div>
<div class="elementToProof">
Ken Boone, USPTO IT Specialist (Retired)</div>
</div>
<div class="elementToProof">
<br>
</div>
<div class="elementToProof">
<br>
</div>
<div class="elementToProof">
<br>
</div>
<hr>
<div id="divRplyFwdMsg">
<div>
<b>From:</b> Carl Oppedahl <a class="moz-txt-link-rfc2396E" href="mailto:carl@oppedahl.com"><carl@oppedahl.com></a><br>
<b>Sent:</b> Sunday, October 12, 2025 4:57 AM<br>
<b>To:</b> For trademark practitioners. This is not for
laypersons to seek legal advice.
<a class="moz-txt-link-rfc2396E" href="mailto:e-trademarks@oppedahl-lists.com"><e-trademarks@oppedahl-lists.com></a><br>
<b>Subject:</b> The ZWSP mistake at the Trademark Office</div>
<div> </div>
</div>
<div>On 5/24/2025 11:15 AM, Ken Boone via E-trademarks wrote:</div>
<blockquote>
<div>PS - Do you notice anything unusual about 99181596, the
trademark <u>OMMISIMQIST\u200b</u> in standard characters. The
search WD:( *\u200b* ) with that</div>
<div><u><img id="x_image_0"
alt="Image for 99181596, select for more details"
moz-do-not-send="true"></u></div>
<div><br>
</div>
<div>It's another case of counting the letters in the wordmark.
It looks like there are only 11 characters in the wordmark,
but there are actually 12. The final letter is the Unicode
character with decimal value 8203, the
<i>zero-width space (rendered: \u200b ; HTML entity:
&ZeroWidthSpace; or &#8203; ), abbreviated ZWSP, is
a non-printing character used in computerized typesetting to
indicate where the word boundaries are, without actually
displaying a visible space in the rendered text</i>. The
search <b>WD:( *\u200b* ) </b>with that <i>zero-width space</i> character
between the two * wildcard operators retrieves only this
OMMISIMQIST\u200b trademark. The similar search
<b>CM:( *\u200b* )</b> retrieves 6 live trademarks, including 2
registrations. Go figure.</div>
<div><br>
</div>
</blockquote>
<p>Hello fellow listserv members.</p>
<p>It will be recalled that on May 24, Ken found this application
number 99181596 which is supposedly a standard-character mark,
except that from the day it was filed it contained Unicode 8203
at the end. This is a zero-width space or ZWSP character.</p>
<p>I plugged it into my IP Badger.</p>
<p>I figured that one or another of the many Trademark Office
lurkers would have quietly flagged the case to correct this
Trademark Office mistake.</p>
<p>On September 25, the case reached the desk of the Examining
Attorney. The EA approved it for publication the next day.</p>
<p>On October 10, this happened:</p>
<blockquote>
<p>692 - WITHDRAWN BEFORE PUBLICATION</p>
</blockquote>
<blockquote>
<p>10/10/2025 ON HOLD - ELECTRONIC RECORD REVIEW REQUI\u2026</p>
</blockquote>
<p>I assumed this must surely mean that somebody at the Trademark
Office was paying attention to the failure on the part of the
Trademark Office to have noticed until now the non-standard
character contained in this supposedly standard-character mark.</p>
<p>But now on October 12, whoever the nameless person was who
pulled the case before publication has quietly let go of it.
Now it is back in the publication workflow. The Trademark
Office has selected October 28 as the day it plans to publish
this application. And (I am not making this up) the ZWSP is
still in the mark.</p>
<p>Carl</p>
<p><br>
</p>
<p><br>
</p>
</blockquote>
</body>
</html>