On Wed, Jul 12, 2017 at 6:32 AM, Benedikt Ritter wrote:
> Hello,
>
> > Am 11.07.2017 um 06:55 schrieb Simon Spero :
> >
> > Since it's an interface, I could change it to IHasACharset?
> >
> > Or If you prefer I could rename it to YouGiveLove? (Lucky Millenials-
> you
> > aren't headsonged)
>
>
Github user ameyjadiye commented on the issue:
https://github.com/apache/commons-text/pull/49
@arunvinudss , amend commit comment as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Thanks for great insights Mark.
On Wed, Jul 12, 2017, 9:28 PM Mark Thomas wrote:
> On 12 July 2017 16:33:01 CEST, Matt Sicker wrote:
> >Are there plans to require 1.7 for Tomcat anytime? Otherwise, it might
> >be
> >necessary to make a new major version of daemon eventually for Java 8
> >or 9.
On 12 July 2017 16:33:01 CEST, Matt Sicker wrote:
>Are there plans to require 1.7 for Tomcat anytime? Otherwise, it might
>be
>necessary to make a new major version of daemon eventually for Java 8
>or 9.
Tomcat major versions are aligned with Java EE versions which in turn have a
minimum Java ve
Are there plans to require 1.7 for Tomcat anytime? Otherwise, it might be
necessary to make a new major version of daemon eventually for Java 8 or 9.
Anyways, 1.6 minimum makes sense to me mainly due to Java 9's compiler not
supporting Java 5 targets anymore.
On 12 July 2017 at 09:19, Mark Thomas
On 11 July 2017 21:02:54 CEST, Amey Jadiye wrote:
>Hi Daemon Maintainers / All,
>
>Daemon seems to be still being maintained on svn, do we have any plan
>moving code base to git ?
No preference on this.
>As fact there is low activity in daemon no one thought of bumping
>version
>from 1.5 to 1.6
Hello,
> Am 11.07.2017 um 06:55 schrieb Simon Spero :
>
> Since it's an interface, I could change it to IHasACharset?
>
> Or If you prefer I could rename it to YouGiveLove? (Lucky Millenials- you
> aren't headsonged)
I recommend to leave this kind of irony out of mailing list communication. T
> Am 11.07.2017 um 21:45 schrieb Gary Gregory :
>
> Are they in sync now? Make sure you have you Maven settings set up just so.
> I think Maven has some docs on how to encrypted and save your passwords.
Maybe it is still syncing with the old svn mirror repository. We probably need
to create an
Github user ameyjadiye commented on the issue:
https://github.com/apache/commons-text/pull/49
For detailed explanation.
https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-e
Github user ecki commented on the issue:
https://github.com/apache/commons-text/pull/49
Not sure I understand the question, surrogate Pairs only exist in UTF-16.
UTF-8 uses a multi byte encoding for code points outside the BMP and UTF-32
uses 4 bytes (and skips the high/low surrogate
Github user arunvinudss commented on the issue:
https://github.com/apache/commons-text/pull/49
Okay I don't mind to change but what does UTF-16 with surrogate pairs
support? Why did we do this refactoring?
---
If your project is set up for it, you can reply to this email and have you
Github user ecki commented on the issue:
https://github.com/apache/commons-text/pull/49
It does not provide support for UTF-32 (which is a 4 byte encoding not
implemented in the patch) but it provides support for UTF-16 surrogate pairs
(1..2 x 2bytes). The both encodings are not compa
Github user ameyjadiye commented on the issue:
https://github.com/apache/commons-text/pull/49
probably just because utf-32 it could be confusing, @ecki can explain more.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user arunvinudss commented on the issue:
https://github.com/apache/commons-text/pull/49
Not sure why I should change the PR name? I never mentioned it provides
native support for UTF-32 and it clearly states support using surrogate pairs .
---
If your project is set up for it,
Github user ameyjadiye commented on the issue:
https://github.com/apache/commons-text/pull/49
@arunvinudss , can you please rename PR saying character processing
switched with codepoints and change commit comment as well, that you can do
with ```rebase``` or ```git commit --amend```
Github user asfgit closed the pull request at:
https://github.com/apache/commons-imaging/pull/26
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
16 matches
Mail list logo
