Just to follow up on Matt's note,
I'm sorry this never got updated. Some changes have been made and
are waiting to go out now. When I switched from working on the
Platform (formerly API) team to my focus on international I took over
this issue.
Once this current fix is deployed
On Wed, Sep 9, 2009 at 1:07 AM, Matt Sanford m...@twitter.com wrote:
I more than agree with the above statement that a character is a
character and Twitter shouldn't care. Data should be data. The main
issue with that is that some clients compose characters and some
don't. My common
2009/9/9 Matt Sanford m...@twitter.com
Hi There,
I'm sorry this never got updated. Some changes have been made and
are waiting to go out now. When I switched from working on the
Platform (formerly API) team to my focus on international I took over
this issue.
Once this current fix
It's been nearly 6 months. Has this question been answered? If so I missed it.
On Tue, Mar 24, 2009 at 9:36 PM, Alex Paynea...@twitter.com wrote:
Unfortunately, nothing definitive. We're still looking into this.
On Tue, Mar 24, 2009 at 07:56, Craig Hockenberry
craig.hockenbe...@gmail.com
Hi There,
I'm sorry this never got updated. Some changes have been made and
are waiting to go out now. When I switched from working on the
Platform (formerly API) team to my focus on international I took over
this issue.
Once this current fix is deployed (probably in a week or so since
Any news from the Service Team? I'd really like to get the counters
right in an upcoming release...
-ch
On Mar 6, 12:18 pm, Alex Payne a...@twitter.com wrote:
I'm taking this email to our Service Team, the folks who work on the
back-end of the service. The whole message body changing as it
Unfortunately, nothing definitive. We're still looking into this.
On Tue, Mar 24, 2009 at 07:56, Craig Hockenberry
craig.hockenbe...@gmail.com wrote:
Any news from the Service Team? I'd really like to get the counters
right in an upcoming release...
-ch
On Mar 6, 12:18 pm, Alex Payne
DO NOT ENCODE WITH HTML ENTITIES.
The only reason that and are encoded as lt; and gt; is because
these values are represented within an XML text element. This is
invalid XML:
textThis -- is a test/text
And this is valid XML:
textThis lt;-- is a test/text
If you use HTML entities, they will
On Mon, Mar 9, 2009 at 7:27 PM, atebits loren.brich...@gmail.com wrote:
Just to confirm: EXTREME prejudice as in 140 *bytes* as defined by
UTF-8 with HTML entity encoding only for special ( ) characters?
Just to interject: has not been specially encoded except for during
a brief time when
I'd reiterate that there's no need to encode as rt;
What about eacute; or agrav; ?? :)
Nic
I'd reiterate that there's no need to encode as rt;
What about eacute; or agrav; ?? :)
We consider the issue neither acute nor grave.
You were waiting all day for that, weren't you?
--
personal: http://www.cameronkaiser.com/ --
Cameron Kaiser *
On Tue, Mar 10, 2009 at 8:26 PM, Alex Payne a...@twitter.com wrote:
We consider the issue neither acute nor grave.
UNFOLLOW.
Oh, wait, crap.
All is such an inclusive term, isn't it? :-)
ONE OF US! ONE OF US!
Hey! I resemble that :)
But I fear we're somewhat West of the OT's question :)
And we still don't know what to do about encoding html entities used
for accents in languages such as French, Spanish, etc ;)
Nic
Just to keep the group updated: one of our engineers has claimed this
issue. It will be dealt with with EXTREME prejudice.
On Fri, Mar 6, 2009 at 12:47, Cameron Kaiser spec...@floodgap.com wrote:
2) 140 Unicode _multi-byte_ characters: http://twitter.com/atebits/
status/1286199010
What's
Just to confirm: EXTREME prejudice as in 140 *bytes* as defined by
UTF-8 with HTML entity encoding only for special ( ) characters?
So my tweet should *NOT* have worked?
http://twitter.com/atebits/status/1286199010
Would love to see some kind of official *this is how we determine how
long some
Once the guys on the backend team get back to me, I'll provide as much.
On Mon, Mar 9, 2009 at 16:27, atebits loren.brich...@gmail.com wrote:
Just to confirm: EXTREME prejudice as in 140 *bytes* as defined by
UTF-8 with HTML entity encoding only for special ( ) characters?
So my tweet
16 matches
Mail list logo
