12574 - [feature] character set support in xpinstall script

Status: RESOLVED WONTFIX

(Core Graveyard :: Installer: XPInstall Engine, defect)

Description

[Cathleen]

we need to support special character set, such as TM

Comment 1

[Daniel Veditz [:dveditz]]

Initial thoughts on this is to parse the first line of the install script
ourselves looking for a special comment line. // charset=foo, for example. we
must parse this before executing the file so we can tell the JS interpreter
what charset to expect. The charset values will most likely be whatever we used
in the manifest file for this in 4.5

Comment 2

[leger]

Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall
Engine

Comment 3

[Cathleen]

moving to m17, no need for beta 1

Comment 4

[Cathleen]

cut feature
putting on helpwanted.

Comment 5

[Daniel Veditz [:dveditz]]

Parcelling out Cathleen's bugs

Comment 6

[Daniel Veditz [:dveditz]]

Changing fictional "M30" to reality

Comment 7

[Daniel Veditz [:dveditz]]

Probably still a future feature, but resetting milestone for reconsideration.

Comment 8

[Daniel Veditz [:dveditz]]

This will have to wait. Meanwhile script authors can escape non-Latin-1 chars.

Comment 9

[Syd Logan]

Resetting milestone of all nsbeta1-bugs, only nsbeta1+ bugs should have a target
milestone.

Comment 10

[Syd Logan]

Resetting milestone, only nsbeta1+ bugs can have a milestone on them, these are
niminated, but not yet plussed.

Comment 11

[Jungshik Shin]

So, what character encoding is expected by the installer? Is it ISO-8859-1? It
seems like at least on Windows, the system default code page is assumed. The
other day, I tried to install a Korean version of firebird on Win2k (with the
default system locale set to Japanese). Instead of Korean characters, I got a
bunch of Japanese characters. When I switched my default system locale to Korean
and tried again, Korean characters showed up. 

I think it's better to make 'UTF-8' the default instead of adding 'charset=xxxx'
option. 

Please, let me know if I'm talking about a totally different issue here.
What I have observed may have more to do with bug 9589 than this. 

Comment 12

[Daniel Veditz [:dveditz]]

The xpinstall script engine has been removed from the trunk, bugs in it are obsolete.