Abdelrazak Younes wrote:
Hum, it seems that I was mis leaded by the slower debug version. In
release mode, the set construction is sensible with utf8 but that's not
all of it apparently...
Some numbers for updateSymbolList() obtained with the attached patch
with a document with 'utf8'
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
No, the problem lies is when we insert the symbols from the
unicodesymbols file. For utf8, we shouldn't do that because _all_
symbols are already in there. On each insertion, std::set() has to
search if the given symbols is not already present;
Abdelrazak Younes wrote:
Try and see what happens if you bypass the unicodesymbols part if
star_encodable_ == ucs4_max.
I saw in the UserGuide that only utf8-plain should never make use of
the 'unicodesymbols' file; is that what you mean?
No, I just meant: try it out. It might indeed
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
Try and see what happens if you bypass the unicodesymbols part if
star_encodable_ == ucs4_max.
I saw in the UserGuide that only utf8-plain should never make use of
the 'unicodesymbols' file; is that what you mean?
No, I just meant: try it
Abdelrazak Younes wrote:
Oh I did, and it improves things a bit indeed but see my other mail
instead.
I saw it. But I don't have time to look at it ATM.
Jürgen
Abdelrazak Younes wrote:
Hum, it seems that I was mis leaded by the slower debug version. In
release mode, the set construction is sensible with utf8 but that's not
all of it apparently...
Some numbers for updateSymbolList() obtained with the attached patch
with a document with 'utf8'
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
No, the problem lies is when we insert the symbols from the
unicodesymbols file. For utf8, we shouldn't do that because _all_
symbols are already in there. On each insertion, std::set() has to
search if the given symbols is not already present;
Abdelrazak Younes wrote:
> > Try and see what happens if you bypass the unicodesymbols part if
> > star_encodable_ == ucs4_max.
>
> I saw in the UserGuide that only "utf8-plain" should never make use of
> the 'unicodesymbols' file; is that what you mean?
No, I just meant: try it out. It might
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
Try and see what happens if you bypass the unicodesymbols part if
star_encodable_ == ucs4_max.
I saw in the UserGuide that only "utf8-plain" should never make use of
the 'unicodesymbols' file; is that what you mean?
No, I just meant: try it
Abdelrazak Younes wrote:
> Oh I did, and it improves things a bit indeed but see my other mail
> instead.
I saw it. But I don't have time to look at it ATM.
Jürgen
Juergen,
There is something fishy in this method.
setchar_type Encoding::getSymbolsList() const
{
// assure the used encoding is properly initialized
init();
// first all encodable characters
CharSet symbols = encodable_;
// add those below
On Fri, Feb 08, 2008 at 08:04:56PM +0100, Abdelrazak Younes wrote:
Juergen,
There is something fishy in this method.
setchar_type Encoding::getSymbolsList() const
{
// assure the used encoding is properly initialized
init();
// first all encodable characters
Abdelrazak Younes wrote:
Juergen,
There is something fishy in this method.
setchar_type Encoding::getSymbolsList() const
{
// assure the used encoding is properly initialized
init();
// first all encodable characters
CharSet symbols = encodable_;
// add those below
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Juergen,
There is something fishy in this method.
setchar_type Encoding::getSymbolsList() const
{
// assure the used encoding is properly initialized
init();
// first all encodable characters
CharSet symbols = encodable_;
Andre Poenitz wrote:
On Fri, Feb 08, 2008 at 08:04:56PM +0100, Abdelrazak Younes wrote:
Juergen,
There is something fishy in this method.
setchar_type Encoding::getSymbolsList() const
{
// assure the used encoding is properly initialized
init();
// first all encodable
Abdelrazak Younes wrote:
No, the problem lies is when we insert the symbols from the
unicodesymbols file. For utf8, we shouldn't do that because _all_
symbols are already in there. On each insertion, std::set() has to
search if the given symbols is not already present; as you have 1114112
Juergen,
There is something fishy in this method.
set Encoding::getSymbolsList() const
{
// assure the used encoding is properly initialized
init();
// first all encodable characters
CharSet symbols = encodable_;
// add those below start_encodable_
On Fri, Feb 08, 2008 at 08:04:56PM +0100, Abdelrazak Younes wrote:
> Juergen,
>
> There is something fishy in this method.
>
> set Encoding::getSymbolsList() const
> {
> // assure the used encoding is properly initialized
> init();
>
> // first all encodable characters
>
Abdelrazak Younes wrote:
Juergen,
There is something fishy in this method.
set Encoding::getSymbolsList() const
{
// assure the used encoding is properly initialized
init();
// first all encodable characters
CharSet symbols = encodable_;
// add those below start_encodable_
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Juergen,
There is something fishy in this method.
set Encoding::getSymbolsList() const
{
// assure the used encoding is properly initialized
init();
// first all encodable characters
CharSet symbols = encodable_;
// add
Andre Poenitz wrote:
On Fri, Feb 08, 2008 at 08:04:56PM +0100, Abdelrazak Younes wrote:
Juergen,
There is something fishy in this method.
set Encoding::getSymbolsList() const
{
// assure the used encoding is properly initialized
init();
// first all encodable
Abdelrazak Younes wrote:
> No, the problem lies is when we insert the symbols from the
> unicodesymbols file. For utf8, we shouldn't do that because _all_
> symbols are already in there. On each insertion, std::set() has to
> search if the given symbols is not already present; as you have 1114112
22 matches
Mail list logo
