|
Revision 792
(checked in by chervol, 2 years ago)
|
initial import
|
- Property svn:eol-style set to
native
|
| Line | |
|---|
| 1 |
Plone4ArtistsAudioPatch |
|---|
| 2 |
|
|---|
| 3 |
Plone4ArtistsAudioPatch is small proof of concept patch for |
|---|
| 4 |
Plone4ArtistsAudio package. |
|---|
| 5 |
|
|---|
| 6 |
The problem which is addressed in this product is text |
|---|
| 7 |
encoding issues in mp3 audio tags. |
|---|
| 8 |
|
|---|
| 9 |
The case. |
|---|
| 10 |
|
|---|
| 11 |
If you edit your mp3 tags in your own language (non English) |
|---|
| 12 |
with Windows based mp3 tag editors (winamp for example). The |
|---|
| 13 |
result tags will be saved in Windows default encoding (for |
|---|
| 14 |
Cyrrilic it will be cp1251). The specifications of id3 tags |
|---|
| 15 |
as of version 2.4 define only three options for encoding |
|---|
| 16 |
'Default' (for Latin-1), 'UTF-8' and 'UTF-16'. This mean that |
|---|
| 17 |
if you populate your mp3 audio track id3 tags in non Cyrrilic |
|---|
| 18 |
windows or Linux or Web you in most cases will see some |
|---|
| 19 |
garbled symbols. |
|---|
| 20 |
|
|---|
| 21 |
With the product we give the website author, who uploads his mp3 |
|---|
| 22 |
track, option to guess the real text encoding of the mp3 tags |
|---|
| 23 |
and convert the strings into UTF. |
|---|
| 24 |
|
|---|
| 25 |
The product is not supposed to be used in production (will not be |
|---|
| 26 |
supported) it is published as proposal for Plone4ArtistsAudio |
|---|
| 27 |
authors to include the feature in the Plone4ArtistsAudio codebase. |
|---|
| 28 |
|
|---|
| 29 |
The Plone4ArtistsAudioPatch was tested with |
|---|
| 30 |
Plone4ArtistsAudio1.0-alpha1 |
|---|
| 31 |
|
|---|
| 32 |
AUTHORS |
|---|
| 33 |
|
|---|
| 34 |
Bogdan Koval mentored by Volodymyr Cherepanyak, Myroslav Opyr |
|---|
