This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 200508 - Encodingproblem
Summary: Encodingproblem
Status: RESOLVED DUPLICATE of bug 197609
Alias: None
Product: php
Classification: Unclassified
Component: Smarty (show other bugs)
Version: 7.0
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-29 08:50 UTC by bedomon
Modified: 2011-09-06 10:38 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bedomon 2011-07-29 08:50:00 UTC 
Product Version = NetBeans IDE 7.0 (Build 201104211303)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.6.0_22
Runtime = Java HotSpot(TM) Client VM 17.1-b03

There is a problem with the character encoding of a php projetc smarty.
The project encoding is iso-8859-1, and each time I open a file wich is in 88959-1 it convert it in utf-8.
I convert my file with notepad++ to put it in iso-8859-1 and when I reopen it ans save it with netbeans all the accent are transform into A@~ style.
Comment 1 David Strupl 2011-08-16 09:13:28 UTC 
Encoding is a per project property --> passing to the PHP project owners for evaluation.
Comment 2 Petr Pisl 2011-09-02 09:14:02 UTC 
Martin, does smarty do something special in encoding?
Comment 3 Martin Fousek 2011-09-02 11:20:10 UTC 
Yes, Smarty has it's own support for encoding (the same like html).
Anyway mentioned troubles are related to older versions of Smarty. Please download from PluginPortal the newest version 1.50.3.2 or use Development versions of netbeans where is smarty par of the build.

Feel free to reopen if your troubles happen again, but as I said, it's probably because of older version of your Smarty plugin. Thanks.

*** This bug has been marked as a duplicate of bug 197609 ***