WOProject/WOLips

Default enconding in WOComponent template file (*.woo)

Details

  • Description:
    Hide
    I hope changing default encoding in WOComponent *.woo template file to UTF-8 (NSUTF8StringEncoding) like the following:

    (wocomponent/wocomponent.woo.vm)
    {
            "WebObjects Release" = "WebObjects 5.0";
            encoding = NSUTF8StringEncoding;
    }

    Current default encoding is NSMacOSRomanStringEncoding. We must edit encodings to write in multi-byte languages for each components. We will happy if the default encoding is changed to NSUTF8StringEncoding.
    Show
    I hope changing default encoding in WOComponent *.woo template file to UTF-8 (NSUTF8StringEncoding) like the following: (wocomponent/wocomponent.woo.vm) {         "WebObjects Release" = "WebObjects 5.0";         encoding = NSUTF8StringEncoding; } Current default encoding is NSMacOSRomanStringEncoding. We must edit encodings to write in multi-byte languages for each components. We will happy if the default encoding is changed to NSUTF8StringEncoding.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Denis Frolov added a comment - 25/Feb/07 7:32 AM
Would be really nice have this one implemented and also have UTF-8 as a default encoding for new WOComponents.
Show
Denis Frolov added a comment - 25/Feb/07 7:32 AM Would be really nice have this one implemented and also have UTF-8 as a default encoding for new WOComponents.
Hide
Permalink
Logi Helgu added a comment - 01/Mar/07 6:24 AM
This is a must have, at least a way to change the default encoding in the WOLips settings, then everyone could set up their own default settings.
Show
Logi Helgu added a comment - 01/Mar/07 6:24 AM This is a must have, at least a way to change the default encoding in the WOLips settings, then everyone could set up their own default settings.
Hide
Permalink
Hugi Thordarson added a comment - 01/Mar/07 6:39 AM
+1.
No, sorry.
+1000000!

:-)
Show
Hugi Thordarson added a comment - 01/Mar/07 6:39 AM +1. No, sorry. +1000000! :-)
Hide
Permalink
Anjo Krank added a comment - 10/Sep/07 3:40 AM
Doesn't the new template system address this? Wouldn't it be better to have people be able to edit their own set of templates instead of a UI feature?
Show
Anjo Krank added a comment - 10/Sep/07 3:40 AM Doesn't the new template system address this? Wouldn't it be better to have people be able to edit their own set of templates instead of a UI feature?
Hide
Permalink
Denis Frolov added a comment - 10/Sep/07 8:54 AM
I though that template system is for new projects - not new components. Does it also allow editing component templates? Anyway, UTF-8 seems to be a reasonable default encoding for new components...
Show
Denis Frolov added a comment - 10/Sep/07 8:54 AM I though that template system is for new projects - not new components. Does it also allow editing component templates? Anyway, UTF-8 seems to be a reasonable default encoding for new components...
Hide
Permalink
Mike Schrag added a comment - 10/Sep/07 9:41 AM
Yes, the new template system is for projects only right now, though we could (and should) extend it to support all of the template types.
Show
Mike Schrag added a comment - 10/Sep/07 9:41 AM Yes, the new template system is for projects only right now, though we could (and should) extend it to support all of the template types.
Hide
Permalink
Daryl Lee added a comment - 22/Oct/07 5:21 PM
I extended the old template system to support this. I'll take a look at the new template system.
Show
Daryl Lee added a comment - 22/Oct/07 5:21 PM I extended the old template system to support this. I'll take a look at the new template system.
Hide
Permalink
Denis Frolov added a comment - 29/Nov/07 3:52 AM
This case seems to be resolved in the latest builds with the new component wizard. The only thing left to be added is an option to choose an encoding for component's .html file (or probably .wo folder). It is MacRoman by default and so I end up doing the "Change encoding to UTF-8 - close component - open component" thing for each new component.
Show
Denis Frolov added a comment - 29/Nov/07 3:52 AM This case seems to be resolved in the latest builds with the new component wizard. The only thing left to be added is an option to choose an encoding for component's .html file (or probably .wo folder). It is MacRoman by default and so I end up doing the "Change encoding to UTF-8 - close component - open component" thing for each new component.
Hide
Permalink
Quinton Dolan added a comment - 12/Apr/08 10:44 PM
This should be resolved from revision 5090
Show
Quinton Dolan added a comment - 12/Apr/08 10:44 PM This should be resolved from revision 5090

People

Dates

  • Created:
    05/Oct/06 10:02 AM
    Updated:
    12/Apr/08 10:44 PM
    Resolved:
    12/Apr/08 10:44 PM
Atlassian JIRA (v4.1.1#522) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for ObjectStyle. Try JIRA - bug tracking software for your team.