On 05/11/07 18:56, VDR User wrote:
> On 5/11/07, Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
>> Well, at some point I'd have to deal with it, anyway, if it's supposed
>> to become part of the core VDR code. So I'd rather do it myself now.
>
> Sure, but if doing it yourself means not doing it prop
On 5/11/07, Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
Well, at some point I'd have to deal with it, anyway, if it's supposed
to become part of the core VDR code. So I'd rather do it myself now.
Sure, but if doing it yourself means not doing it properly, why not
let someone else who's willing
On 05/11/07 18:10, VDR User wrote:
> I think the best question to be asking concerning UTF-8 isn't if you
> personally like the idea but rather what's better in terms of design.
> That consideration should outweigh any other. You certainly don't
> want to create a situation where you're doing a lo
I think the best question to be asking concerning UTF-8 isn't if you
personally like the idea but rather what's better in terms of design.
That consideration should outweigh any other. You certainly don't
want to create a situation where you're doing a lot more work then
necessary in the long run
On 11 May 2007, at 15:54, Klaus Schmidinger wrote:
Please don't make same hacks such in my patch.
Change a type to wchar_t.
wchar_t is definitely *not* the way I'll go.
I feel so lucky working with Java when it comes to character encoding
issues. Our webapp uses UTF-8 exclusively, but we
It's simply short-sighted.
The best way in Open Source is fork of project.
If this happens, I will support this new project.
--
Alexander
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On 05/11/07 16:51, [EMAIL PROTECTED] wrote:
> Hi All,
> hi Klaus,
>
> i would like to say also my 0,02€ to it.
>
> My UTF-8 patch, which I wrote for 1.3 - 1.4 vdr is ugly hack.
> I have developed a patch from emergency !!!
>
> I must unfortunately with 3 languages go around and could not simpl
Hi All,
hi Klaus,
i would like to say also my 0,02€ to it.
My UTF-8 patch, which I wrote for 1.3 - 1.4 vdr is ugly hack.
I have developed a patch from emergency !!!
I must unfortunately with 3 languages go around and could not simply not
see that German words instead of üöä cyrillic characters
Hi Klaus,
in our devices (barcode reader) we use 16 bit characters and it works out
nice and easy and very similar to the old bytes.
It was not easy to convince my collegues (in the USA), but I managed to do
it.
IMHO this is much simpler than the UTF8, all the index into a string still
wor
Klaus Schmidinger wrote:
> On 05/11/2007 09:25 AM, Ludwig Nussel wrote:
> > What's wrong with vdr using UTF-8 internally if it makes the code simpler?
> > Offhand I could only imagine two places where using a different external
> > encoding would be required and that's file names and tty i/o. Stuff
On 05/11/2007 09:25 AM, Ludwig Nussel wrote:
> Klaus Schmidinger wrote:
>> On 05/10/07 20:04, Udo Richter wrote:
>>> ...
>>> VDR development would speed up, if Klaus would delegate more work to
>>> other talented coders, and doing more review instead of coding most of
>>> it himself.
>> Well, right
Klaus Schmidinger wrote:
> On 05/10/07 20:04, Udo Richter wrote:
> > ...
> > VDR development would speed up, if Klaus would delegate more work to
> > other talented coders, and doing more review instead of coding most of
> > it himself.
>
> Well, right now I'm dealing with the UTF-8 stuff, which i
On 05/10/07 20:04, Udo Richter wrote:
> ...
> VDR development would speed up, if Klaus would delegate more work to
> other talented coders, and doing more review instead of coding most of
> it himself.
Well, right now I'm dealing with the UTF-8 stuff, which is something
I myself don't need at all.
[EMAIL PROTECTED] wrote:
As you yourself said in the above/below statement, time is a limited
resource for this project and you can't spend all day developing
vdr (and you have a life besides vdr =). The way I see it, is a clear
roadmap could make the development more effective and avoid waste
o
On 05/09/07 18:37, VDR User wrote:
> ...
> I've been using vdr since 1.3.x also and most of the
> 'development' versions up until 1.5.2 have been very stable.
I personally always use the latest developer version in every day
operation, so I have every reason to make sure it runs stable ;-)
Klaus
On 5/9/07, Joerg Knitter <[EMAIL PROTECTED]> wrote:
During the development of version 1.3 I have been often a little
frustrated not to have seen a final version 1.4. There were a lot of
reasons that IMHO the usage of version 1.2 was quite outdated: No
automatic channel scan, updated Dolby Digital
On 9 May 2007, at 17:10, Klaus Schmidinger wrote:
As Clemens already stated, UTF-8 pretty much requires that.
However, I'm not sure, yet, whether this also immediately means
"font anitaliasing", because that's not necessarily something
required by UTF-8.
Well, it's prob not required, but it m
On 05/09/07 16:37, Torgeir Veimo wrote:
>
> On 9 May 2007, at 15:06, Klaus Schmidinger wrote:
>
>> On 05/09/2007 04:02 PM, Joerg Knitter wrote:
>>> ..
>>> P.S.: Great to see the UTF-8 support. I can remember some posts where
>>> kls said that he did not like it and thus did not want to implement
Torgeir Veimo <[EMAIL PROTECTED]> wrote:
> Does the UTF-8 support include the freetype font support?
> Antialiased fonts looks s much better.
UTF-8 makes no sense with a 7-bit ascii character set. so i guess, yes.
clemens
___
vdr mailing list
vdr@
On 9 May 2007, at 15:06, Klaus Schmidinger wrote:
On 05/09/2007 04:02 PM, Joerg Knitter wrote:
..
P.S.: Great to see the UTF-8 support. I can remember some posts where
kls said that he did not like it and thus did not want to
implement it :)
I still don't like it - and I won't be using it
On 05/09/2007 04:02 PM, Joerg Knitter wrote:
> ..
> P.S.: Great to see the UTF-8 support. I can remember some posts where
> kls said that he did not like it and thus did not want to implement it :)
I still don't like it - and I won't be using it myself either ;-)
Klaus
__
VDR User wrote:
> I can say I have no concern about the development of vdr unless Klaus
and the others tells us theres reason for it. I'm perfectly content
hearing "1.6 will be out when it's ready" as long as I know it's under
active development.
I have been a VDR user for nearly 5 years now,
I'll chime in... I've emailed Klaus on many occasions with what I
thought were potential bugs, new feature requests, or just general
inquiry. He's always replied (although sometimes not so quickly ;),
and what I've come to realize... or maybe remember is a better word
to use here.. What I've c
ONE LAST THING! =)
> As I've stated on several occasions: I don't like official
> roadmaps. They tend to become sort of binding, and if - for
> some reason - a new release actually doesn't contain a feature
> that was promised on the roadmap, all sorts of complaints
> might emerge. I do observe th
I hereby take back what I said about having time to reply =)
On Tue, May 08, 2007 at 11:43:59PM +0200, Klaus Schmidinger wrote:
> On 05/08/07 22:37, [EMAIL PROTECTED] wrote:
> > ...
> > The stable version of vdr (1.4.6.something at the time being afaik)
> > get's "older" all the time and only the
On 05/08/07 22:37, [EMAIL PROTECTED] wrote:
> ...
> The stable version of vdr (1.4.6.something at the time being afaik)
> get's "older" all the time and only the most vital parts
> from the devel-branch get backported.
Well, that's what a "stable" version is by definition ;-)
It gets actual bugs f
Hello!
I would like to share some of thoughts on what I have observed
over a short periode of time. I've been following the mailing
list, I don't have practically any knowledge in programming
so I won't even try to comment on the technical details of the
vdr project itself. I would also like to po
27 matches
Mail list logo
