Skip to main content

This patch product is for downloaded filename become strange ascii code in muluti-byte languages on Plone

Project description

Introduction

This patch product is for downloaded filename become strange ascii code in muluti-byte languages on Plone

  • When downloading file with Japanese name, downloaded file has some strange ascii coded name.

  • I think we should get file name that shows in Plone page.

  • This happens on all Plone version. I think if the file is named with multi byte code, this strange ascii name shows up.

  • Please, look at attached file to fix this problem for IE and Firefox. Other browsers, we are still working on it.

requirement

Plone 3.x (Tested by Plone 3.3.1 on MaxOS X 10.5)

Changelog

1.0b5 (2018-03-01)

  • Support Edge and IE11 [terapyon]

  • Drop support IE8 [terapyon]

1.0b4 (2017-10-06)

  • Modify for blob bug fix [terapyon]

1.0b3 (2013-06-19)

  • Missing packaging, forgot including docs

1.0b2 (2013-06-19)

  • Adding special notify for c2.app.zipdownload

1.0b1 (2012-08-10)

  • Modify for Firefox Ver 8

  • Adding auto include plone zcml

1.0a5 (2010-07-08)

  • remove ja.py (don’t need file)

1.0a4 (2010-02-24)

  • bug fix for blob field

1.0a3 (2010-02-24)

  • bug fix for blob field

1.0a2 (2010-02-19)

  • Support blob field(plone.app.blob)

1.0a1 (2010-01-08)

  • Initial release

c2.patch.filenamenormalizer Installation

  • When you’re reading this you have probably already run easy_install c2.patch.filenamenormalizer. Find out how to install setuptools (and EasyInstall) here: http://peak.telecommunity.com/DevCenter/EasyInstall

  • Get pythonproducts and install it via:

    python setup.py install --home /path/to/instance

    into your Zope instance.

  • Create a file called c2.patch.filenamenormalizer-configure.zcml in the /path/to/instance/etc/package-includes directory. The file should only contain this:

    <include package="c2.patch.filenamenormalizer" />

Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, you can do this:

  • Add c2.patch.filenamenormalizer to the list of eggs to install, e.g.:

    [buildout]
    ...
    eggs =
        ...
        c2.patch.filenamenormalizer
  • Tell the plone.recipe.zope2instance recipe to install a ZCML slug:

    [instance]
    recipe = plone.recipe.zope2instance
    ...
    zcml =
        c2.patch.filenamenormalizer
  • Re-run buildout, e.g. with:

    $ ./bin/buildout

You can skip the ZCML slug if you are going to explicitly include the package from another package’s configure.zcml file.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

c2.patch.filenamenormalizer-1.0b5.tar.gz (12.1 kB view details)

Uploaded Source

File details

Details for the file c2.patch.filenamenormalizer-1.0b5.tar.gz.

File metadata

File hashes

Hashes for c2.patch.filenamenormalizer-1.0b5.tar.gz
Algorithm Hash digest
SHA256 4e8a04b0ea6e3b63d5515c835e397d405a3c79cd7b962aa8f0f4cd695f14f222
MD5 8421b43a2a63ad19ddb5237a1cbbb817
BLAKE2b-256 c0ea94816a161c42bab8e167304e1645c0f8bb816273dfd745ab788f97774080

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page