Comments (3)
That is expected behavior since only one of char/byte variants will ever provide actual information.
Type depends on input source itself: when given byte source like InputStream
, only byte offsets are available; when char source like Reader
, char offsets.
Async readers are always byte-based so only byte offsets are available.
The reason for this is because of costs involved in keeping accurate offsets -- native offset (byte or char) is needed for decoding, with little to no additional, but the "other" offset is either expensive to obtain (re-encoding to go from char
to byte
), or would need to be kept track on unit-by-unit basis (since decoding of char
from byte
is not separate step but integral part of processing from byte stream to tokens).
In case of async parsing, then, the only way to find character offsets would be for caller to keep track of buffers and then decode on as-needed basis.
from aalto-xml.
Thanks for your explanation. You are right, probably to costly to have that feature by default.
from aalto-xml.
@sco0ter Processing overhead is part of it, but keeping track would add a lot to complexity unfortunately. If there was a modular way to do it that'd be possible but... unfortunately no, at least the way implementation works.
from aalto-xml.
Related Issues (20)
- Support Latin-1 (ISO-8859-1) via Async parser HOT 5
- Allow for ignoring encoding or setting default encoding
- Source bundles have no Bundle-SymbolicName in Manifest HOT 4
- XML Escape is not working HOT 1
- Can't use ENTITY_REFERENCE event for resolution in an Attribute HOT 3
- Support disabling General Entity Reference replacement in attribute values HOT 6
- XMLReaderImpl.getAttributeValue(String, String) does not ignore namespace if null HOT 1
- Add Java 9+ module info using Moditect HOT 1
- Reading full elements
- `BufferRecycler` access not safe if readers/writers used from different threads
- Support disabling namespace awareness HOT 1
- java.lang.NoClassDefFoundError: javax/xml/stream/events/XMLEvent HOT 2
- getLocation() doesn't count xml prolog for non-utf8 documents
- Add support for JEP-185 (JAXP-1.5) properties named ACCESS_EXTERNAL_
- Async parsing turns " inside element content into apostrophe HOT 4
- DTD RootName only returned correctly if it consists of a multiple of 4 bytes HOT 1
- `Attributes.getValue(String qName)` sometimes returns values from previous elements HOT 4
- `DataUtil.growArrayBy(arr, more)` is vulnerable to break the service. HOT 1
- ` textAccumulator.addText(buf, start, end)` introduces security issue. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aalto-xml.