Am 21.01.2015 16:41, schrieb Hugo Osvaldo Barrera:
Hi,
I posted a message ending with the character "😄" on the AUR today, but
that
character got stripped.
Does AUR not have UTF-8 support? Have I bumped into a new issue?
Thanks,
The MySQL character encoding we use does not support such 4 by
On 2015-01-21 18:08, Lukas Fleischer wrote:
> On Wed, 21 Jan 2015 at 18:05:17, Bartłomiej Piotrowski wrote:
> > On Wed, 21 Jan 2015 12:41:53 -0300
> > Hugo Osvaldo Barrera wrote:
> > > Hi,
> > >
> > > I posted a message ending with the character "😄" on the AUR today,
> > > but that character got
* Bartłomiej Piotrowski [2015-01-21 18:05:17 +0100]:
> On Wed, 21 Jan 2015 12:41:53 -0300
> Hugo Osvaldo Barrera wrote:
> > Hi,
> >
> > I posted a message ending with the character "😄" on the AUR today,
> > but that character got stripped.
> >
> > Does AUR not have UTF-8 support? Have I bumped
On Wed, 21 Jan 2015 at 18:05:17, Bartłomiej Piotrowski wrote:
> On Wed, 21 Jan 2015 12:41:53 -0300
> Hugo Osvaldo Barrera wrote:
> > Hi,
> >
> > I posted a message ending with the character "😄" on the AUR today,
> > but that character got stripped.
> >
> > Does AUR not have UTF-8 support? Have I
On Wed, 21 Jan 2015 12:41:53 -0300
Hugo Osvaldo Barrera wrote:
> Hi,
>
> I posted a message ending with the character "😄" on the AUR today,
> but that character got stripped.
>
> Does AUR not have UTF-8 support? Have I bumped into a new issue?
>
> Thanks,
>
How is that an issue? Do you really
Hi,
I posted a message ending with the character "😄" on the AUR today, but that
character got stripped.
Does AUR not have UTF-8 support? Have I bumped into a new issue?
Thanks,
--
Hugo Osvaldo Barrera
A: Because we read from top to bottom, left to right.
Q: Why should I start my reply below th