As many web platform developer and Firefox users, I believe Mozilla’s mission is instrumental for a better Internet. In a recent Igalia’s chat about the Web Ecosystem Health, participants made the usual observation regarding this important role played by Mozilla on the one hand and the limited development resources and small Firefox’s usage share on the other hand. In this blog post, I’d like to explain an experimental idea we are launching at Igalia to try and make browser development better match the interest of the web developer and user community.
Igalia’s contribution to browser repositories
As mentioned in the past in this blog, Igalia has contributed to different part of Firefox such as multimedia (e.g. <video> support), layout (e.g. Stylo, WebRender, CSS, MathML), scripts (e.g. BigInt, WebAssembly) or accessibility (e.g. ARIA). But is it enough?
Although commit count is an imperfect metric it is also one of the easiest to obtain. Let’s take a look at how Igalia’s commits repositories of the Chromium (chromium, v8), Mozilla (mozilla-central, servo, servo-web-render) and WebKit projects were distributed last year:
Diagram showing, the distribution of Igalia's contributions to browser repositories in 2019 (~5200 commits). Chromium (~73%), Mozilla (~4%) and WebKit (~23%).
As you can see, in absolute value Igalia contributed roughly 3/4 to Chromium, 1/4 to WebKit, with a small remaining amount to Mozilla. This is not surprising since Igalia is a consulting company and our work depends on the importance of browsers in the market where Chromium dominates and WebKit is also quite good for iOS devices and embedded systems.
This suggests a different way to measure our contribution by considering, for each project, the percentage relative to the total amount of commits:
Diagram showing, for each project, the percentage of Igalia's commits in 2019 relative to the total amount of the project. From left to right:
Chromium (~3.96%), Mozilla (~0.43%) and WebKit (~10.92%).
In the WebKit project, where ~80% of the contributions were made by Apple, Igalia was second with ~10% of the total. In the Chromium project, the huge Google team made more than 90% of the contributions and many more companies are involved, but Igalia was second with about 4% of the total. In the Mozilla project, Mozilla is also doing ~90% of the contributions but Igalia only had ~0.5% of the total. Interestingly, the second contributing organization was… the community of unindentified gmail.com addresses! Of course, this shows the importance of volunteers in the Mozilla project where a great effort is done to encourage participation.
Open Prioritization
From the commit count, it’s clear Igalia is not contributing as much to the Mozilla project as to Chromium or WebKit projects. But this is expected and is just reflecting the priority set by large companies. The solid base of Firefox users as well as the large amount of volunteer contributors show that the Mozilla project is nevertheless still attractive for many people. Could we turn this into browser development that is not funded by advertising or selling devices?
Another related question is whether the internet can really be shaped by the global community as defended by the Mozilla’s mission? Is the web doomed to be controlled by big corporations doing technology’s “evangelism” or lobbying at standardization committees? Are there prioritization issues that can be addressed by moving to a more collective decision process?
At Igalia, we internally try and follow a more democratic organization and, at our level, intend to make the world a better place. Today, we are launching a new Open Prioritization experiment to verify whether crowdfunding could be a way to influence how browser development is prioritized. Below is a short (5 min) introductory video:
I strongly recommend you to take a look at the proposed projects and read the FAQ to understand how this is going to work. But remember this is an experiment so we are starting with a few ideas that we selected and tasks that are relatively small. We know there are tons of user reports in bug trackers and suggestions of standards, but we are not going to solve everything in one day !
If the process is successful, we can consider generalizing this approach, but we need to test it first, check what works and what doesn’t, consider whether it is worth pursuing, analyze how it can be improved, etc
As explained in the previous paragraph, we are starting with small tasks. For Firefox, we selected the following ones:
CSS lab() colors. This is about giving web developers a way to express colors using the CIELAB color space which approximates better the human perception. My colleague Brian Kardell wrote a blog with more details. Some investigations have been made by Apple and Google. Let’s see what we can do for Firefox !
SVG path d attribute. This is about expressing SVG path using the corresponding CSS syntax for example <path style="d: path('M0,0 L10,10,...')">. This will likely involve a refactoring to use the same parser for both SVG and CSS paths. It’s a small feature but part of a more general convergence effort between SVG and CSS that Igalia has been involved in.
Conclusion
Is this crowd-funded experiment going to work? Can this approach solve the prioritization problems or at least help a bit? How can we improve that idea in the future?…
There are many open questions but we will only be able to answer them if we have enough people participating. I’ll personally pledge for the two Firefox projects and I invite you to at least take a look and decide whether there is something there that is interesting for you. Let’s try and see!
Note: This blog post was co-authored by AMP and Igalia teams.
Web developers continue to face challenges with web interoperability issues and a lack of implementation of important features. As an open-source project, the AMP Project can help represent developers and aid in addressing these challenges. In the last few years, we have partnered with Igalia to collaborate on helping advance predictability and interoperability among browsers. Standards and the degree of interoperability that we want can be a long process. New features frequently require experimentation to get things rolling, course corrections along the way and then, ultimately as more implementations and users begin exploring the space, doing really interesting things and finding issues at the edges we continue to advance interoperability.
Both AMP and Igalia are very pleased to have been able to play important roles at all stages of this process and help drive things forward. During the first half of this year, here’s what we’ve been up to…
Default Aspect Ratio of Images
In our previous blog post we mentioned our experiment to implement the intrinsic size attribute in WebKit. Although this was a useful prototype for standardization discussions, at the end there was a consensus to switch to an alternative approach. This new approach addresses the same use case without the need of a new attribute. The idea is pretty simple: use specified width and height attributes of an image to determine the default aspect ratio. If additional CSS is used e.g. “width: 100%; height: auto;”, browsers can then compute the final size of the image, without waiting for it to be downloaded. This avoids any relayout that could cause bad user experience. This was implemented in Firefox and Chromium and we did the same in WebKit. We implemented this under a flag which is currently on by default in Safari Tech Preview and the latest iOS 14 beta.
Scrolling
We continued our efforts to enhance scroll features. In WebKit, we began with scroll-behavior, which provides the ability to do smooth scrolling. Based on our previous patch, it has landed and is guarded by an experimental flag “CSSOM View Smooth Scrolling” which is disabled by default. Smooth scrolling currently has a generic platform-independent implementation controlled by a timer in the web process, and we continue working on a more efficient alternative relying on the native iOS UI interfaces to perform scrolling.
We have also started to work on overscroll and overscroll customization, especially for the scrollend event. The scrollend event, as you might expect, is fired when the scroll is finished, but it lacked interoperability and required some additional tests. We added web platform tests for programmatic scroll and user scroll including scrollbar, dragging selection and keyboard scrolling. With these in place, we are now working on a patch in WebKit which supports scrollend for programmatic scroll and Mac user scroll.
On the Chrome side, we continue working on the standard scroll values in non-default writing modes. This is an interesting set of challenges surrounding the scroll API and how it works with writing modes which was previously not entirely interoperable or well defined. Gaining interoperability requires changes, and we have to be sure that those changes are safe. Our current changes are implemented and guarded by a runtime flag “CSSOM View Scroll Coordinates”. With the help of Google engineers, we are trying to collect user data to decide whether it is safe to enable it by default.
Another minor interoperability fix that we were involved in was to ensure that the scrolling attribute of frames recognizes values “noscroll” or “off”. That was already the case in Firefox and this is now the case in Chromium and WebKit too.
Intersection and Resize Observers
As mentioned in our previous blog post, we drove the implementation of IntersectionObserver (enabled in iOS 12.2) and ResizeObserver (enabled in iOS 14 beta) in WebKit. We have made a few enhancements to these useful developer APIs this year.
Users reported difficulties with observe root of inner iframe and the specification was modified to accept an explicit document as a root parameter. This was implemented in Chromium and we implemented the same change in WebKit and Firefox. It is currently available Safari Tech Preview, iOS 14 beta and Firefox 75.
Another thing that we have been concerned with is how we can give more control and power to authors to more effectively tell the browser how to manage the loading of resources and improve performance.
The lazy image loading implementation in WebKit therefore passes the related WPT tests and is functional and comparable to the Firefox and Chrome implementations. However, as you might expect, as we compare uses and implementation notes it becomes apparent that determining the moment when the lazy image load should start is not defined well enough. Before this can be enabled in releases some more work has to be done on improving that. The related frame lazy loading work has not started yet since the specification is not in place.
We also added an implementation for stale-while-revalidate. The stale-while-revalidate Cache-Control directive allows a grace period in which the browser is permitted to serve a stale asset while the browser is checking for a newer version. This is useful for non-critical resources where some degree of staleness is acceptable, like fonts. The feature has been enabled recently in WebKit trunk, but it is still disabled in the latest iOS 14 beta.
Contributions were made to improve prefetching in WebKit taking into account its cache partitioning mechanism. Before this work can be enabled some more patches have to be landed and possibly specified (for example, prenavigate) in more detail. Finally, various general Fetch improvements have been done, improving the fetch WPT score. Examples are:
There is still a lot to do in scrolling and resource loading improvements and we will continue to focus on the features mentioned such as scrollend event, overscroll behavior and scroll behavior, lazy loading, stale-while-revalidate and prefetching.
As a continuation of the work done for aspect ratio calculation of images, we will consider the more general CSS aspect-ratio property. Performance metrics such as the ones provided by the Web Vitals project is also critical for web developers to ensure that their websites provide a good user experience and we are willing to investigate support for these in Safari.
We love doing this work to improve the platform and we’re happy to be able to collaborate in ways that contribute to bettering the web commons for all of us.
In a previous blog post, I described an oscillating Zeno’s paradox, which can be formalized as follows. Atalanta moves on the real line. She leaves from 0 and at step she decides to move forward or backward by . If corresponds to the chosen direction then writing and
we obtain sequence of Atalatan’s position on the real line.
In the non-oscillating case ( for all ) then this just corresponds to a geometric series of common ration . converges to 1 by lower values, with remaining distance being . More generally, is just the partial sum of an absolutely convergent series and so is convergent to a destination . It is easy to see that , and . If additionally is chosen so that it is not ultimately constant (i.e. Atalatan’s position keeps oscillating) then this becomes a strict inequality .
In theory, it is possible to reach any destination using this approach. Just define if and only if (i.e. “move toward ”). It is easy to prove by recurrence that for all and so . However, this assumes we already know in order to decide the sequence of directions . Let’s see how to build sequences without knowing the destination.
Avoiding an at most countable subset
Suppose that is at most countable and let be a sequence of real numbers such that . We want to find a sequence such that .
Assuming additionally that it has infinitely many terms above and infinitely many terms below , then we obtain a non-ultimately-constant sequence by defining if and only if (i.e. “move away from ”). This is because so there are always infinitely many terms in front of and behind Atalanta.
Incidentally, with trivial enumeration shows a simple counter-example with no term below and ultimately constant . In that case, and and for . But .
To workaround that issue, we can alternatively define the sequence if and only if and . This still moves away from all once, keeps oscillating and does not require additional assumption on .
Whatever the decision chosen, we can show that . Otherwise, consider one such that is defined by moving away from . Then either and or . But in any case, we would have which contradicts our strict inequality for not ultimately constant .
As explained in the previous blog, this shows that (or any complete subspace containing ) is uncountable. Otherwise, we could use a sequence enumerating it to arrive to a contradiction.
Similarly, because is countable then we can find a sequence such that , which gives us an irrational number . If instead is the set of algebraic numbers (which is countable and contains ) then we obtain a transcendental .
An explicit computation
The big difference between the case of and the set of algebraic numbers is that it’s much easier to actually compute a list of that lists all the . For example, a simple way to enumerate the fractions without trying to avoid duplicate values is, for each to enumerate the integers and bounded by in the lexicographical order. One can similarly enumerate for each the non-constant polynomial of degree at most and integer coefficient bounded by but it’s not obvious how to actually compute their roots.
One can rely on root finding algorithm to estimate the roots in order to be able to calculate the sign and so determine . But in theory, can be arbitrary close to so it’s not clear how much precision to request.
Instead, let’s consider an enumeration of the non-constant polynomial with integer cofficients and define if and only if . With that new formula, can be calculated very easily in from the cofficients of using Horner’s method.
For any integer , let’s consider . Then its product with its derivative is . Its value at any has the same sign as and if it just . For any , we can find large enough such that and have not been enumerated yet. So is not ultimately constant. Alternatively, we could have used the trick from the previous section to force that property.
Now let’s prove that is still algebraic. If that’s not the case, let such that . We can choose such that is of minimal degree and so . Since has only finitely many roots, there is such that at maximum distance around , is the only root of and does not vanish. Let’s large enough such that the polynomial has not been enumerated before . Let’s such that .
In the considered neighbourhood of , has only one root , has the same sign as and its derivative has the same nonzero constant sign as . Analyzing each combination positive/negative and greater/smaller than , we verify that is chosen such that which is obviously also true if . This agains contradict our strict inequality. Q.E.D.
A simple variant of Zeno’s paradoxes can be described as follows. Atalanta wishes to walk to the end of a path. When she gets halfway, she still have to walk the remaining half of the path ; When she gets halfway of that remaining half, she still needs to walk the remaining quarter of the path ; When she gets halfway of that remaining quarter, she still needs to walk the remaining eight of the path ; and so on. Hence it seems she will never reach the end of the path, which is paradoxical.
Obviously, this is not true: Atalanta is going to reach the end of the path after a certain amount of time. The issue in the previous reasoning is that (assuming she walks at constant velocity) walking these subpaths also takes her respectively half, a quarter, a eight, etc of the total time she actually needs to arrive to her destination… and the observations are only done for a total time that is less than the one needed.
A modern variant
Now suppose the ground is an infinite real line, itself covered by an infinite treadmill on which Atalanta is walking. This treadmill brings Atalanta in the opposite direction by twice her velocity. She can decide to turn the treadmill on or off, but its state must remain the same during the whole walk of a subpath. In the following schema, the treadmill was enabled when she was on the second subpath:
After the total duration considered in the previous problem, Atalanta has walked exactly the same total distance on the treadmill. The conveyor belt also moves by summing up distances that are twice the distances on subpaths. Because the treadmill can be on or off, the conveyor’s belt position is not following a simple linear function of the time. Let’s admit for a while it still converges to a certain distance when getting closer to the total duration, I will come back to this at the end of the blog post.
With respect to the ground, Atalanta’s position is basically given by her departure position, moved backward by the distance of the conveyor belt with respect to the ground and moved forward by the distance she walked on the treadmill. As a consequence of the previous paragraph, Atalanta is also converging to a destination with respect to the ground.
Modern Zeno’s paradox (with a flaw)
Now consider an enumeration of all the points of the real line. At the beginning the treadmill is off. Before walking the first half of the path, Atalanta picks the first point in that enumeration and enables the treadmill if she can see that point in front of her. Before walking the next quarter of the path, she picks the second point and enables or disables the treadmill according to whether she can see that second point in front of her. She continues that way for each subpath and each point of the real line.
When a given point is picked there are two options. Either it is not in front of her and so she will just walk forward to a certain distance ; or otherwise the the treamill will additionnaly take her backward by twice that distance. In any case, with respect to the ground, she is moving away from the picked point by the distance she walks during that subpath.
At some step, the point of the real line corresponding to Atalanta’s destination will be picked and she will move away from that destination by a certain distance. But the remaining subpaths are half, a quarter, a eight, etc that distance. To have a chance to converge to the destination again she must now always keep the same direction. But so far, only finitely many points have been picked and so there is at least one point beyond the destination that has not been chosen yet (actually infinitely many). This means she will have to change her direction at least once in the future and so will never be able to reach her destination!
Uncountability of the real line
How to solve the paradox in this modern variant?
First, let’s go back to why the distance of the conveyor belt with respect to the ground is convergent. Consider the binary number whose digits describe the sequences of states of the treadmill: 0 if turned off and 1 if turned on. Place the binary point after the first digit to obtain a real number. Then one can check that the distance of the conveyor belt is given by that real number multiplied by Atalanta’s total distance on the treadmill. Of course, one must admit that such a binary number with infinitely many digits after the binary point is well defined!
For a rigorous proof, note that the conveyor belt is always going in the same direction and at most twice Atalanta’s total walking distance on the treadmill. So the convergence of the conveyor belt just comes from the monotone convergence theorem. This assumption was correct.
However, reading more carefully the argumentation, we actually assumed that there is a countable enumeration of all the points of the real line. But Cantor proved at the end of the 19th century that this is wrong, the real line is uncountable!
It is interesting to actually turn this modern Zeno’s paradox into an apparently “elementary” alternative of Cantor’s diagonal argument, in a way that involves only concepts understandable by the Ancient Greeks and no advanced mathematical formalisms. In particular, this is not mentioning explicitly the positional notation invented by Indian mathematicians. As a comparison, Cantor’s proof assumes that a decimal notation with infinitely many digits after the decimal point is well defined (similar to what we used for our proof with binary numbers) ; or it must deal with the edge case of a real number with two different decimal notations (e.g. 0.4999999… = 0.5).
It is also interesting to note that all the moves as well as Atalanta’s total distance on the treadmill are rational numbers. Since the rational numbers are countable, this modern Zeno’s paradox can also be performed by considering only rational points on the ground. In that case, the flaw is then in the assumption that the conveyor belt converges to a rational point: the set of rational numbers is not complete.
More generally, we can also applie this modern Zeno’s paradox to any ordered field since they include a subset isomorphic to the rational numbers. The conclusion becomes that if the field is Cauchy-complete then it is uncountable.
Update 2020/03/10: Added complexity analysis for S.substr(α, N)
In a previous blog post, I defined for each ordinal a string (made of the characters for the empty set, comma, opening brace and closing brace) that enumerates the element of . I gave a simple formulas to calculate the length of this string.
My colleague Ioanna was a bit disappointed that I didn’t provide a script for calculating the infinite strings. Obviously, the complexity would be “” but it is still possible to evaluate the string at a given position: Given , what is the character of at position ?
Since the initial segments of the strings are compatible, another way to express this is by introducing the class corresponding to a giant string enumerating the class of all ordinals. Given an ordinal , what is ?
A small generalization of this S.charAt(α) operation is S.substr(α, N) calculating the substring of length starting at .
Example
is "∅,{∅}", so
is the character ∅, is a comma,
is an opening brace and is a closing brace.
is made of
of an -concatenation of finite strings
(the character ∅, a comma,
surrounded by braces, a comma,
surrounded by braces, a comma,
surrounded by braces, a comma, etc), followed
by a comma, an opening brace, the same
-concatenation of finite strings and finally
a closing brace.
So is a comma,
is an opening brace,
is the character "∅"
and is a closing brace.
In the previous example, we have basically analyzed the string at a given successor ordinal, splitting it into two copies of , comma and braces. This suggests some easy values of :
Lemma
For any and , is:
A comma if can be written or
An opening brace if can be written or
A closing brace if can be written or
Proof: For any ordinal , by viewing the string
as a concatenation of , a comma, an opening fence, and
a closing fence, we deduce that:
is a comma.
is an opening brace.
is a successor ordinal and
is a closing brace.
The lemma follows immediately from the calculation of string lengths performed in the previous blog post. □
Warning: The rest of the blog post gives the solution to this puzzle, so you
might want to have fun solving it yourself first and then go back checking
my proposed solution later 😉...
More generally, the proof of the lemma can be extended by saying that if we find such that then is the index of in the second substring of and so .
Details will be provided in the theorem below but one can already write a simple JavaScript recursive program to evalute at finite ordinals:
Script for
The character of at position
is
The following intermediary step will be helpful to evaluate at infinite ordinal :
Proposition
Let is infinite and .
Let and be the quotient
and remainder of the euclidean division of by .
Let’s define:
Then is:
A comma if
An opening brace if
An closing brace if
otherwise where is the unique
ordinal such that
and .
Proof: First by construction we have .
If the first case of the definition of , so we always have .
If additionnaly is not a power then and so . Otherwise and and so again .
In the second case of the definition of , so . is a power of 2 and more precisely so we deduce the same way as in the previous case that . Moreover, so again .
We can thus view as a concatenation of , a comma, an opening brace, and
a closing brace. We assume that as the three other cases are handled by the lemma. Then is well-defined and is actually the index of in the second copy of so . □
We are now ready to give a nice way to evaluate at any ordinal :
Theorem
can be calculated inductively as follows:
If , is the character "∅".
If then and is equal to:
A comma if
An opening brace if
A closing brace if
otherwise where
.
Moreover compares against as follows:
and
If is infinite, let be the coefficient
in its Cantor normal form corresponding to the smallest infinite term
and be finite term if there is one, or zero otherwise.
Let be the exponent corresponding to the smallest nonzero
term in the binary decomposition of .
Then is equal to:
A closing brace if .
A comma if .
An opening brace if .
if .
Proof:
The case is clear. Suppose and let . By definition so . Let’s consider the case as the three other cases are already known from the Lemma. is made of the concatenation of , a comma and surrounded by braces. is actually the index of in the second copy of so . The first equality is straighforward:
Morever we have:
and so the second inequality follows from the fact that . Finally, the third inequality comes from:
Let’s consider the case of an infinite . For some , and and , we can write Cantor’s Normal form as:
With the notation of the proposition, we have , and
If , then is infinite and so and we are in the fouth bullet of the proposition. Moreover and we can write:
where is infinite and so cancels out the term. It follows that . Essentially, we have just removed from its term of highest exponent in its binary decomposition!
By repeated application of the theorem, we can remove each binary digit of the for going from to . When then arrive at :
With the notation of the proposition, we now have , and . If the binary decomposition of has more than one nonzero digit then so is not a power of 2. So although is now finite, we are still in the first case of the proposition and remains infinite. So we can remove all but the last digit of by repeated application of the proposition:
where is the exponent corresponding to the smallest nonzero term in the binary decomposition of .
Using the lemma, is a comma if , an opening brace if and a closing brace if .
If then and writing
we deduce from the proposition that .
Finally, if then and writing
we deduce from the proposition that
We have essentially decremented and we can repeat this until we reach the case for which we already said that the character is a closing brace. □
As an application of this theorem, here is a few simple exercises:
Let be an ordinal. Let be the coefficient in its Cantor normal form corresponding to the smallest infinite term if there is one, or zero otherwise. Let be its finite term if there is one, or zero otherwise. Then can be evaluated in:
elementary arithmetic operations and comparisons on integers.
Proof: First note that the “+ 2” is just to workaround for the edge cases or .
For the infinite case we need to calculate that is performing the find first set. A naive implementation can be done in steps by browsing the digits of to find the first nonzero for example by calculating the remainder modulo increasing power of 2. Each iteration requires only elementary integer operations %, * and comparisons. Then returning the result of moving to the finite case requires integer operations +, − and comparisons.
For the finite case and , first notice that we only require recursive calls given the inequality:
The case only requires one comparison. For the case , we need to calculate which is integer rounding of the binary logarithm or even just . As above, we can provide a naive implementation by calculating the quotient modulo increasing power of 2 in comparisons and elementary integer operations /, *. Then returning the result of moving to a requires only integer operations and comparisons. In total, complexity is .
Finally, this can be simplified if one calculates and by a simple leading/trailing zero counting (or similar) and by a bit shift. □
Script based on Cantor normal form
If the coefficients of Cantor normal form of corresponding the smallest infinite term and finite term are
=
=
Then the character of at position is
Once we have an algorithm for S.charAt(α), it is easy to get an algorithm of times that complexity for S.substr(α, N) calculating the substring of length starting at position by repeated calls to S.charAt(α). Let’s analyze a bit more carefully how we can make this recursive and more efficient:
Corollary 2: Algorithm for S.substr(α, N)
Let be an ordinal and . Then S.substr(α, N) can be calculated as follows:
If then it is the empty string.
If and then it is the character "∅".
If , let . We have and the result is obtained by concatenating the following strings:
If , the substring at offset and length .
If , a comma.
If , an opening brace.
If , the substring at offset and length .
If , a closing brace.
If is infinite, let be the coefficient
in its Cantor normal form corresponding to the smallest infinite term
and be finite term if there is one, or zero otherwise.
Let be the exponent corresponding to the smallest nonzero
term in the binary decomposition of . Then the result is obtained by a concatenating the following strings:
If , closing braces.
If , a comma.
If , an opening brace.
If , the substring at offset and length .
Moreover, this only adds compared to the complexity of evaluating to a single offset.
Proof: The algorithm is just direct application of the Theorem. For the case where , the only change is that we add at most characters before moving to the finite case. The case is essentially a divide-and-conquer algorithm and we have a relation of the form:
where and is or depending on available operations, but in any case . So from the master theorem, . In general, this bound is not as good as repeating calls to S.charAt!
However, we note that if we assume that then and so
We can easily discard the edge case where these start/end offsets point to a brace surrounding the right substring of the iterative step and so we get:
which means that the left substring is just empty and so the complexity is not changed compared to S.charAt. Finally, when the previous bound tells us that the steps are done in . □
Script for S.substr(α, N)
If the coefficients of Cantor normal form of corresponding the smallest infinite term and finite term are
=
=
Then the character of substring of length
=
and offset is