Opened 9 years ago

Last modified 6 years ago

#2954 new defect

package.order encoded UTF-8 with Byte Order Mark (BOM) is not properly handled

Reported by: adrpo Owned by: somebody
Priority: high Milestone: Future
Component: Frontend Version: trunk
Keywords: Cc:

Description (last modified by adrpo)

When we read package.order encoded in UTF-8 with BOM the first class name is mangled, if is MassFlowRate then the name we read is: MassFlowRate which will make the library un-loadable.

Change History (10)

comment:1 Changed 9 years ago by adrpo

  • Component changed from Frontend to Parser
  • Description modified (diff)
  • Owner changed from somebody to sjoelund.se
  • Summary changed from Short class definition as stored definition are not loaded to package.order encoded UTF-8 with Byte Order Mark (BOM) is not properly handled

comment:2 Changed 9 years ago by sjoelund.se

What does this have to do with the parser? The parser never reads package.order.

comment:3 Changed 9 years ago by adrpo

  • Component changed from Parser to Frontend
  • Owner changed from sjoelund.se to somebody

Yeah, it should be class loader, so FrontEnd I guess?

comment:4 Changed 9 years ago by sjoelund.se

  • Milestone changed from 1.9.2 to 1.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:5 Changed 9 years ago by sjoelund.se

  • Milestone changed from 1.9.3 to 1.9.4

Moved to new milestone 1.9.4

comment:6 Changed 8 years ago by sjoelund.se

  • Milestone changed from 1.9.4 to 1.9.5

Milestone pushed to 1.9.5

comment:7 Changed 8 years ago by sjoelund.se

  • Milestone changed from 1.9.5 to 1.10.0

Milestone renamed

comment:8 Changed 7 years ago by sjoelund.se

  • Milestone changed from 1.10.0 to 1.11.0

Ticket retargeted after milestone closed

comment:9 Changed 7 years ago by sjoelund.se

  • Milestone changed from 1.11.0 to 1.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:10 Changed 6 years ago by casella

  • Milestone changed from 1.12.0 to Future

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.

Note: See TracTickets for help on using tickets.