Re: case-mapping part of a Unicode string

On 07/01/2009 02:04 AM, Bruno Haible wrote: size_t uppercased_part_3_4_len; uint8_t *uppercased_part_3_4 = u8_ct_toupper (pointer3, pointer4 - pointer3, pre, suf, iso639_language, NULL, NULL, &uppercased_part_3_4_len); pre = u8_casing_p

Re: case-mapping part of a Unicode string

size_t uppercased_part_3_4_len; uint8_t *uppercased_part_3_4 = u8_ct_toupper (pointer3, pointer4 - pointer3, u8_casing_prefix_context (s, pointer3 - s), u8_casing_suffix_context (pointer4, s_end - pointer4), iso639_language, NULL, NU

Re: git-merge-changelog question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 6/30/2009 2:28 PM: > Hi Eric, > >> git-merge-changelog either segfaults > > Ouch. It's written as defensively as possible, and checked with valgrind. > Therefore I thought that was impossible! I haven't been found a simp

Re: case-mapping part of a Unicode string

Paolo Bonzini wrote: > Regarding this part, how could I use the incremental context > computation? The most probable use-cases of these incremental functions are - when your data structure is not a single string, but a concatenation of strings, - when you cache many casing_prefix_context_

Re: [bug-libunistring] Re: case-mapping part of a Unicode string

Paolo Bonzini wrote: > It would be nice to have something in coreutils doing normalization... Bruno discussed adding a `unorm` util previously which we're considering: http://lists.gnu.org/archive/html/bug-coreutils/2009-02/threads.html#00224 The alternative existing `uconv` mentioned in that thr

Re: git-merge-changelog question

I've repeatedly encountered a situation where git-merge-changelog is a hindrance rather than a help. Any time I commit a patch on one branch, then want to run 'git cherry-pick' to copy it to another, git-merge-changelog either segfaults or goes into a super-long processing loop trying to resolv

Re: git-merge-changelog question

Hi Eric, > git-merge-changelog either segfaults Ouch. It's written as defensively as possible, and checked with valgrind. Therefore I thought that was impossible! > Any time I commit a patch on one branch, > then want to run 'git cherry-pick' to copy it to another, > git-merge-changelog either s

Re: mkstemps

On Tue, Jun 30, 2009 at 5:12 AM, Eric Blake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to Bruce Korb on 6/29/2009 2:55 PM: >> Silly me, I just have to ask (rhetorically):  Why is this nice, new >> interface cooked up and then left unfinished.  It needs "mkdtemps", too, y

git-merge-changelog question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've repeatedly encountered a situation where git-merge-changelog is a hindrance rather than a help. Any time I commit a patch on one branch, then want to run 'git cherry-pick' to copy it to another, git-merge-changelog either segfaults or goes into a

Re: mkstemps

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruce Korb on 6/29/2009 2:55 PM: > Silly me, I just have to ask (rhetorically): Why is this nice, new > interface cooked up and then left unfinished. It needs "mkdtemps", too, yes? > Just for symmetry, if nothing else Ask the BSD fo

Re: case-mapping part of a Unicode string

Paolo Bonzini wrote: > Can you show an example of case converting the 3rd, 6th and 7th > character of a string? First, you need the indices (in terms of units) of the 3rd, 4th, 6th, 8th character: const uint8_t *s = ...; const uint8_t *s_end = s + u8_strlen (s) + 1; const uint8_t *p = s;