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 122412 - I18N - add ability to select project encoding to project creation wizard
Summary: I18N - add ability to select project encoding to project creation wizard
Status: VERIFIED FIXED
Alias: None
Product: php
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Mysik
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2007-11-20 16:37 UTC by Andrew Korostelev
Modified: 2008-07-31 03:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Korostelev 2007-11-20 16:37:13 UTC
It is now possible to set project files encoding only after project is created.
Other NB modules are implemented in the same way.


But for PHP project it is requested to have encoding selection in project creation wizard.
Comment 1 Andrew Korostelev 2007-11-20 16:41:40 UTC
will fix after 6.0
Comment 2 Ken Frank 2007-12-13 15:46:22 UTC
added I18N to summary and I18N keyword, as is done for i18n related issues for
internal tracking.

please let me know if any other php issues on i18n so far and I can add that info
to them also.

question - if user changes project encoding after project creation,
will module handle that as to communication with php and changing
needed config files or properties ?

ken.frank@sun.com
Comment 3 Ken Frank 2008-02-10 17:50:09 UTC
do php files/language have an encoding attribute or property themselves ?
if so, should part of the feq implemenation for php have this attribute in the template,
like is done for jsp, html, xml files ?

if not, do they follow that of the program they are embedded in if its html, for example ?

ken.frank@sun.com
Comment 4 Ken Frank 2008-04-07 17:16:34 UTC
I see encoding property now but its not the default utf-8 encoding property
that is used by all other modules - assuming user has not changed that property
in another module.

I see on new php project wizard a choice for encoding but its seeded with
encoding of the locale user is in, ie x-euc-jp -- thus in that sense I can
see why project props has that value also.

But should user need to choose encoding at time of creating project - other nb projects
don't ask or require this ?

or perhaps if needed, the choice should be seeded with current global project
encoding - default is utf-8 ?

am making p2 since that is more accurate priority for encoding situations.

ken.frank@sun.com
Comment 5 Ken Frank 2008-05-21 18:41:30 UTC
please comment on this as to php for 6.5 -

- should encoding choice be in wizard of php project ? (its not for other nb projects)

- should encoding choice in wizard (or default encoding if not in wizard)
be that of utf-8, which is default for other nb projects vs the encoding of locale
user is in, which is how its done now for php project ?

ken.frank@sun.com
Comment 6 Petr Pisl 2008-06-18 14:43:32 UTC
This feature is already implemented.
Comment 7 Petr Pisl 2008-06-18 14:44:49 UTC
I'm marking as fixed.
Comment 8 Ken Frank 2008-06-18 16:21:10 UTC
the default choice for the encoding at project creation time
is encoding of the locale user is in, but netbeans default project
encoding is utf-8 -- should php wizard seed the choice with utf-8
or is it more common that php developers would not use utf-8
encoding ?

ken.frank@sun.com
Comment 9 Tomas Mysik 2008-06-18 21:19:57 UTC
UTF-8 is definitely the most widely used encoding in PHP applications IMHO.
Comment 10 Ken Frank 2008-07-28 20:40:53 UTC
verified, and also the seeded encoding is the value of the current
global project encoding, which seems to be right solution.

ken.frank@sun.com
Comment 11 Ken Frank 2008-07-31 03:47:49 UTC
verified.