Hi
I have the same problem. Have you found any solution?
Thanks and regards.
On 15 ago, 17:18, fruity wrote:
> Hi everyone,
>
> This is not my code, but the code of washtub the liquidsoap controller
> made with django so for I've mailed both ML, django and liquidsoap
>
> I have a directory ful
Hi everyone,
This is not my code, but the code of washtub the liquidsoap controller
made with django so for I've mailed both ML, django and liquidsoap
I have a directory full of any kind of files, some of this filenames are
in latin1 and when I run my django app I get UnicodeDecodeError like t
Well...
I just restored my database from production dump... On prod I have correct
UTF-8
On Wed, May 20, 2009 at 4:49 PM, Karen Tracey wrote:
> On Wed, May 20, 2009 at 9:37 AM, Oleg Oltar wrote:
>
>> Hm... You're right...But I don't understand how it happened... I used sync
>> db to create thos
On Wed, May 20, 2009 at 9:37 AM, Oleg Oltar wrote:
> Hm... You're right...But I don't understand how it happened... I used sync
> db to create those table
>
syncdb doesn't specify a character set, it uses the database default. I
don't understand how some of your tables would have one value whil
Hm... You're right...But I don't understand how it happened... I used sync
db to create those table
mysql> show create table articleManager_categoty\G
*** 1. row ***
Table: articleManager_categoty
Create Table: CREATE TABLE `articleManager_cat
2009/5/20 Oleg Oltar
> [snip]Strange when I am adding an article with russian text or Section
> with russian name, everything is OK
> But when I a trying to add a new category via admin, and use name of it in
> russian I am getting this exception:
>
> Warning at /admin/articleManager/categoty/add
Hi!
I am creating a simple application for managing articles. It contains of
several entities:
1) categories
2) sections
3) articles
The code:
class Categoty(models.Model):
categoty = models.CharField(max_length=200)
name = models.CharField(max_length = 200, help_text="Имя категории")
Malcolm Tredinnick wrote:
> On Wed, 2007-08-29 at 14:58 +0100, Robin Becker wrote:
>> Hi, we're having some troubles with latest django that are caused by the
>> switch
>> to unicode string output. In particular since we were already carefully
>> handling
>> the conversion and encoding of the
On Wed, 2007-08-29 at 14:58 +0100, Robin Becker wrote:
> Hi, we're having some troubles with latest django that are caused by the
> switch
> to unicode string output. In particular since we were already carefully
> handling
> the conversion and encoding of the database values we are now gettin
On Wed, Aug 29, Robin Becker wrote:
>
> Hi, we're having some troubles with latest django that are caused by the
> switch
> to unicode string output. In particular since we were already carefully
> handling
> the conversion and encoding of the database values we are now getting errors
> bec
On Thu, 2007-08-30 at 00:52 +1000, Malcolm Tredinnick wrote:
> On Wed, 2007-08-29 at 14:58 +0100, Robin Becker wrote:
> > Hi, we're having some troubles with latest django that are caused by the
> > switch
> > to unicode string output. In particular since we were already carefully
> > handling
Hi, we're having some troubles with latest django that are caused by the switch
to unicode string output. In particular since we were already carefully
handling
the conversion and encoding of the database values we are now getting errors
because the data is in unicode. Is it possible to disabl
rgs:
'charset': 'cp1251'
These 2 patches allowed me to use newforms too (remember that
clean_data is in unicode by design)
I am sure everything works ok when unicode is used everywhere
(database, site, templates etc) but what about using django in national
non-unicode envir
Hello again
It seems like newforms library has a problem with non unicode charsets
yet.
For example, I use 'windows-1251' character set for my web apps and
MySQL 4.1 with 'cp1251' so actually all data is stored and shown in
cp1251.
And here's what I get when try to sa
Malcolm Tredinnick wrote:
>
> Although I have not used non-ISO-8859-1 storage much at all, I know that
> there are some people around who have been using it for a while now
> quite successfully, so almost all of the problems are easily solvable
> with current Django code. One day I hope to find t
On Tue, 2006-09-19 at 18:33 +, Pupeno wrote:
> On Tuesday 19 September 2006 02:58, Malcolm Tredinnick wrote:
> > That's true. We aren't using unicode universally at the moment. There is
> > work in progress to fix this, but it has no completion date at the
> > moment.
>
> So, I can't store Un
On Tuesday 19 September 2006 02:58, Malcolm Tredinnick wrote:
> That's true. We aren't using unicode universally at the moment. There is
> work in progress to fix this, but it has no completion date at the
> moment.
So, I can't store Unicode strings on PostgreSQL and expect it to work under
any c
On Tue, 2006-09-19 at 02:27 +, Pupeno wrote:
> Hello,
> I am using Django 0.95 and SimpleTAL for templating. SimpleTAL expects all
> the
> strings, it seems, to be unicode (something sane from my point of view). It
> seems that some data from PostgreSQL extracted using Django classes is not
Request URL:
http://127.0.0.1:8000/search/
Exception Type:
ContextContentException
Exception Value:
Found non-unicode string in Context!
Exception Location:
/usr/lib/python2.4/site-packages/simpletal/simpleTAL.py in expandInline, line
619
the traceback is:
Traceback (most recent call last
19 matches
Mail list logo
