UTF-8 for new documents
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2008 08:22 AM
Hello,
is it possible to define UTF-8 as default enconding (character set) for new documents?
When I create a new (TXT, HTML, XML) document with the web-interface, UTF-8 should be preselected in the list of encodings.
Is it possible to configure this behavior?
Thanks
Simon
is it possible to define UTF-8 as default enconding (character set) for new documents?
When I create a new (TXT, HTML, XML) document with the web-interface, UTF-8 should be preselected in the list of encodings.
Is it possible to configure this behavior?
Thanks
Simon
Labels:
- Labels:
-
Archive
6 REPLIES 6

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2008 12:55 PM
Yes. In your web-client-config-custom.xml add this section:
Kevin
<config evaluator="string-compare" condition="Content Wizards"> <!– default encoding when creating new inline content if not set then server default charset encoding will be used –> <default-encoding>UTF-8</default-encoding> </config>
Kevin

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2008 07:24 AM
Yes. In your web-client-config-custom.xml add this section:<config evaluator="string-compare" condition="Content Wizards"> <!– default encoding when creating new inline content if not set then server default charset encoding will be used –> <default-encoding>UTF-8</default-encoding> </config>
Kevin
Hello Kevin,
Alfresco 2.1 here. Added the above section in my web-client-config-custom.xml file but didnt work. Still preselects Big5.
Has this issue been fixed only on 2.9 or does it work on 2.1 and I'm doing smth wrong?
Paris

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2008 08:16 AM
Any news on that ?
Regards,
Paris Kapsouros
Regards,
Paris Kapsouros

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2008 07:31 AM
Works here on 2.9 - haven't tried it on 2.1 lately.
Kevin
Kevin

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2008 08:38 AM
Works here on 2.9 - haven't tried it on 2.1 lately.
Kevin
meh, i guess we should wait for the final 2.9 then and then upgrade. Till then I found a workaround on that with creating a script that changes the encoding of new content into UTF-8.
Anyways, thanks a lot for your input Kevin.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2008 01:03 PM
I checked those config modifications - work on r1672, and latest svn revision. And you were right - they don't work on 2.1.
