Product CalendarTag on zope2.13.19
Hello! I'm running a zope2.13.19 instance on my mac. I intstalled the product Calendar version 1.0.19 I adjusted the file __init__.py Change the line: from ImageFile import ImageFile with: from App.ImageFile import ImageFile so far so good. Still, one problem is this type of error: SyntaxError: Non-ASCII character '\xf1' in file /Applications/zope21319/Products/Calendar/CalendarTag.py on line 139, but no encoding declared; Is pointing to lines containing non ASCII character such as this one: 'pl': ('StyczeÒ','Luty','Marzec','KwiecieÒ','Maj','Czerwiec','Lipiec','SierpieÒ','WrzesieÒ','Paºdziernik','Listopad','GrudzieÒ') What is the best way to take care of this issue? Of course, the fastest is to get rid of some languages... not good. It could be nice to release a complete working version of the product. Please give me some hints. Thank You, Giampiero
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/27/2013 11:44 AM, Giampiero Benvenuti wrote:
Hello!
I'm running a zope2.13.19 instance on my mac. I intstalled the product Calendar version 1.0.19
I adjusted the file __init__.py
Change the line:
from ImageFile import ImageFile
with:
from App.ImageFile import ImageFile
so far so good.
Still, one problem is this type of error:
SyntaxError: Non-ASCII character '\xf1' in file /Applications/zope21319/Products/Calendar/CalendarTag.py on line 139, but no encoding declared;
Is pointing to lines containing non ASCII character such as this one:
'pl': ('StyczeÒ','Luty','Marzec','KwiecieÒ','Maj','Czerwiec','Lipiec','SierpieÒ','WrzesieÒ','Paºdziernik','Listopad','GrudzieÒ')
What is the best way to take care of this issue? Of course, the fastest is to get rid of some languages... not good.
It could be nice to release a complete working version of the product.
Please give me some hints.
You could add the encoding at the top of the Python module. See PEP 263: http://www.python.org/dev/peps/pep-0263/ Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFTJMwACgkQ+gerLs4ltQ6sugCeNDKMadJOIa1IlmdoIvIImO+4 +FcAnAzX7dZrorjmoJCmSvBYV4U+a7mH =hmSL -----END PGP SIGNATURE-----
Thanks so much for your tips! I'm running out right now. I'll be testing and reporting tomorrow. Giampiero On Mar 27, 2013, at 17:56 44, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/27/2013 11:44 AM, Giampiero Benvenuti wrote:
Hello!
I'm running a zope2.13.19 instance on my mac. I intstalled the product Calendar version 1.0.19
I adjusted the file __init__.py
Change the line:
from ImageFile import ImageFile
with:
from App.ImageFile import ImageFile
so far so good.
Still, one problem is this type of error:
SyntaxError: Non-ASCII character '\xf1' in file /Applications/zope21319/Products/Calendar/CalendarTag.py on line 139, but no encoding declared;
Is pointing to lines containing non ASCII character such as this one:
'pl': ('StyczeÒ','Luty','Marzec','KwiecieÒ','Maj','Czerwiec','Lipiec','SierpieÒ','WrzesieÒ','Paºdziernik','Listopad','GrudzieÒ')
What is the best way to take care of this issue? Of course, the fastest is to get rid of some languages... not good.
It could be nice to release a complete working version of the product.
Please give me some hints.
You could add the encoding at the top of the Python module. See PEP 263:
http://www.python.org/dev/peps/pep-0263/
Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlFTJMwACgkQ+gerLs4ltQ6sugCeNDKMadJOIa1IlmdoIvIImO+4 +FcAnAzX7dZrorjmoJCmSvBYV4U+a7mH =hmSL -----END PGP SIGNATURE-----
_______________________________________________ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/27/2013 04:44 PM, Giampiero Benvenuti wrote:
Still, one problem is this type of error:
SyntaxError: Non-ASCII character '\xf1' in file /Applications/zope21319/Products/Calendar/CalendarTag.py on line 139, but no encoding declared; just place this line on top of the file:
# -*- coding: utf-8 -*- with this, you declare the encoding of the file to be utf-8, which is probably the encoding you need. http://www.python.org/dev/peps/pep-0263/ what you describe sounds as if the Calendar product is not actively maintained. what usecase do you want to solve? where did you get the Calendar product from? best, johannes raggam - -- programmatic web development di(fh) johannes raggam / thet python plone zope development mail: office@programmatic.pro web: http://programmatic.pro http://bluedynamics.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFTJo0ACgkQW4mNMQxDgAd1UACgrZPkmA6qECH9kqplNG3vAz2N MNIAn1corxQzogbnr5MHe38SlSSI2xCo =zNPb -----END PGP SIGNATURE-----
Thanks Johannes and Tres, the trick you both suggested works! I am forced to use this old product because I'll need to migrate a site (from zope2.10) that is using it. The Calendar product comes from here: http://old.zope.org/Members/teyc/CalendarTag/ Now, that the Calendar works, what should we do with it? Release it again with a new version number, or just forget about it? (It is old, indeed). regards, Giampiero On Mar 27, 2013, at 18:04 13, johannes raggam wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/27/2013 04:44 PM, Giampiero Benvenuti wrote:
Still, one problem is this type of error:
SyntaxError: Non-ASCII character '\xf1' in file /Applications/zope21319/Products/Calendar/CalendarTag.py on line 139, but no encoding declared; just place this line on top of the file:
# -*- coding: utf-8 -*-
with this, you declare the encoding of the file to be utf-8, which is probably the encoding you need. http://www.python.org/dev/peps/pep-0263/
what you describe sounds as if the Calendar product is not actively maintained. what usecase do you want to solve? where did you get the Calendar product from?
best, johannes raggam
- -- programmatic web development di(fh) johannes raggam / thet python plone zope development mail: office@programmatic.pro web: http://programmatic.pro http://bluedynamics.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlFTJo0ACgkQW4mNMQxDgAd1UACgrZPkmA6qECH9kqplNG3vAz2N MNIAn1corxQzogbnr5MHe38SlSSI2xCo =zNPb -----END PGP SIGNATURE-----
Really you need this? Maybeyou could use a calendar with javascript just one example http://javascriptcalendar.org/javascript-date-picker.php I'm sure that exists many more 2013/3/28 Giampiero Benvenuti <giampiero.benvenuti@chiaroscuro.com>
Thanks Johannes and Tres,
the trick you both suggested works!
I am forced to use this old product because I'll need to migrate a site (from zope2.10) that is using it. The Calendar product comes from here:
http://old.zope.org/Members/teyc/CalendarTag/
Now, that the Calendar works, what should we do with it? Release it again with a new version number, or just forget about it? (It is old, indeed).
regards,
Giampiero
On Mar 27, 2013, at 18:04 13, johannes raggam wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/27/2013 04:44 PM, Giampiero Benvenuti wrote:
Still, one problem is this type of error:
SyntaxError: Non-ASCII character '\xf1' in file /Applications/zope21319/Products/Calendar/CalendarTag.py on line 139, but no encoding declared; just place this line on top of the file:
# -*- coding: utf-8 -*-
with this, you declare the encoding of the file to be utf-8, which is probably the encoding you need. http://www.python.org/dev/peps/pep-0263/
what you describe sounds as if the Calendar product is not actively maintained. what usecase do you want to solve? where did you get the Calendar product from?
best, johannes raggam
- -- programmatic web development di(fh) johannes raggam / thet python plone zope development mail: office@programmatic.pro web: http://programmatic.pro http://bluedynamics.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlFTJo0ACgkQW4mNMQxDgAd1UACgrZPkmA6qECH9kqplNG3vAz2N MNIAn1corxQzogbnr5MHe38SlSSI2xCo =zNPb -----END PGP SIGNATURE-----
_______________________________________________ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
-- ________________________________________ Lo bueno de vivir un dia mas es saber que nos queda un dia menos de vida
I know Miguel, I see your point. And yes I use js calendars as well. As I said, I need this product in order to migrate a site... In any case this morning I got an email from someone asking for it. The Calendar-tag product is here: http://www.staticfiles.it/clients/chiaroscuro/zope/products/CalendarTag-1.0.... I change the version number from 1.0.19 to 1.0.20. I hope I did the right thing. Best, Giampiero On Apr 1, 2013, at 21:49 20, Miguel Beltran R. wrote:
Really you need this? Maybeyou could use a calendar with javascript just one example http://javascriptcalendar.org/javascript-date-picker.php I'm sure that exists many more
2013/3/28 Giampiero Benvenuti <giampiero.benvenuti@chiaroscuro.com> Thanks Johannes and Tres,
the trick you both suggested works!
I am forced to use this old product because I'll need to migrate a site (from zope2.10) that is using it. The Calendar product comes from here:
http://old.zope.org/Members/teyc/CalendarTag/
Now, that the Calendar works, what should we do with it? Release it again with a new version number, or just forget about it? (It is old, indeed).
regards,
Giampiero
On Mar 27, 2013, at 18:04 13, johannes raggam wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/27/2013 04:44 PM, Giampiero Benvenuti wrote:
Still, one problem is this type of error:
SyntaxError: Non-ASCII character '\xf1' in file /Applications/zope21319/Products/Calendar/CalendarTag.py on line 139, but no encoding declared; just place this line on top of the file:
# -*- coding: utf-8 -*-
with this, you declare the encoding of the file to be utf-8, which is probably the encoding you need. http://www.python.org/dev/peps/pep-0263/
what you describe sounds as if the Calendar product is not actively maintained. what usecase do you want to solve? where did you get the Calendar product from?
best, johannes raggam
- -- programmatic web development di(fh) johannes raggam / thet python plone zope development mail: office@programmatic.pro web: http://programmatic.pro http://bluedynamics.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlFTJo0ACgkQW4mNMQxDgAd1UACgrZPkmA6qECH9kqplNG3vAz2N MNIAn1corxQzogbnr5MHe38SlSSI2xCo =zNPb -----END PGP SIGNATURE-----
_______________________________________________ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
-- ________________________________________ Lo bueno de vivir un dia mas es saber que nos queda un dia menos de vida
participants (4)
-
Giampiero Benvenuti -
johannes raggam -
Miguel Beltran R. -
Tres Seaver