Woodstox

Provide API to access quote character

Details

  • Type: Improvement Improvement
  • Status: In Progress In Progress
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Currently, there is no way to determine how quoted values are actually quoted. They can either use single or double quotes, but this information is not exposed. I would propose to enhance the Woodstox implementation to make this information accessible.

With my use case, the event API is used to emit a document and I would therefore require enhanced event implementations (e.g. AttributeEventImpl, NamespaceEventImpl...) that record this information. The proposed refactoring for WSTX-130 might make such a change easy (at least easier than with the current code base).

As always, I'm prepared to hack the sources, but would welcome your feedback as to whether you think such support might make it into the official stream. Thanks.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tatu Saloranta added a comment -

Quick question: is this just to improve exact round-trippability of content? That is, to minimize any changes to exact look. Semantically the two are equivalent, similar to how white space between attributes is.

This information is of course internally available, and you are correct in that WSTX-130 refactoring would probably make it feasible to add this support.

Show
Tatu Saloranta added a comment - Quick question: is this just to improve exact round-trippability of content? That is, to minimize any changes to exact look. Semantically the two are equivalent, similar to how white space between attributes is. This information is of course internally available, and you are correct in that WSTX-130 refactoring would probably make it feasible to add this support.
Hide
Permalink
Marco Hunsicker added a comment -

Yes, keeping the current quoting style might be desirable, but that's something that is not currently possible with Woodstox. Personally, I have no problem with enforcing double-quotes, but needs differ and user's should have the choice. It's only an issue with user-created content. I can anticipate cases where users specifically use single quotes to avoid the need to escape double quotes within the value string.

As I know that you might plan to refactor the code base, I wanted to bring this issue to your attention so you might add it to the requirements. Thanks.

Show
Marco Hunsicker added a comment - Yes, keeping the current quoting style might be desirable, but that's something that is not currently possible with Woodstox. Personally, I have no problem with enforcing double-quotes, but needs differ and user's should have the choice. It's only an issue with user-created content. I can anticipate cases where users specifically use single quotes to avoid the need to escape double quotes within the value string. As I know that you might plan to refactor the code base, I wanted to bring this issue to your attention so you might add it to the requirements. Thanks.

People

  • Assignee:
    Tatu Saloranta
    Reporter:
    Marco Hunsicker
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: