Re: Ligatures (was: [VOTE] Merge branch Temp_ComplexScripts into trunk)

[Glenn Adams]

They (latin ligatures) are already enabled, so no extra work is needed.
Though this could benefit by adding support for some of the more recent CSS3
font properties related to the use of AATs, e.g., see [1] for:

font-variant-alternates
font-variant-ligatures
font-feature-settings

[1] http://www.w3.org/TR/css3-fonts/

On Wed, Oct 26, 2011 at 2:40 AM, Christopher R. Maden wrote:

> On 10/25/2011 10:16 AM, Glenn Adams wrote:
> > Keep in mind that Latin (Roman), Cyrillic, and Greek scripts also
> > benefit from support when complex scripts are enabled, since in these
> > cases the advanced typographic tables (ATT) present in OpenType fonts
> > used with these scripts are enabled. For example, such tables enable
> > the correct placement of combining marks (e.g., diacritics and
> > accents) with base characters.
>
> Ooh, I hadn’t really thought of this before... how much work would it
> take to use this code to enable Latin ligatures (fi, fl, etc.) when the
> typeface supports them?  I currently handle this in XSLT and it’s a
> PITA, and also lacks information about actual typeface support for
> advanced ligatures (ffi, ct, etc.).
>
> ~Chris
> --
> Chris Maden, text nerd  http://crism.maden.org/ >
> “Be wary of great leaders.  Hope that there are many, many small
>  leaders.” — Pete Seeger
>

Ligatures (was: [VOTE] Merge branch Temp_ComplexScripts into trunk)

[Christopher R. Maden]

On 10/25/2011 10:16 AM, Glenn Adams wrote:
> Keep in mind that Latin (Roman), Cyrillic, and Greek scripts also
> benefit from support when complex scripts are enabled, since in these
> cases the advanced typographic tables (ATT) present in OpenType fonts
> used with these scripts are enabled. For example, such tables enable
> the correct placement of combining marks (e.g., diacritics and
> accents) with base characters.

Ooh, I hadn’t really thought of this before... how much work would it
take to use this code to enable Latin ligatures (fi, fl, etc.) when the
typeface supports them?  I currently handle this in XSLT and it’s a
PITA, and also lacks information about actual typeface support for
advanced ligatures (ffi, ct, etc.).

~Chris
-- 
Chris Maden, text nerd  http://crism.maden.org/ >
“Be wary of great leaders.  Hope that there are many, many small
 leaders.” — Pete Seeger

Re: [VOTE] Merge branch Temp_ComplexScripts into trunk

[Adrian Cumiskey]

+1 from me.  A lot of work, a great achievement.

On 25 October 2011 12:10, Simon Pepping  wrote:

> The vote runs for three days, and will end on Friday 28 October 2011
> at 18:00h UTC.
>
> Simon Pepping
>
> On Tue, Oct 25, 2011 at 10:31:43AM +0200, Simon Pepping wrote:
> >
> > Following this request, I herewith propose to merge the branch
> > Temp_ComplexScripts into trunk, and launch a formal vote.
> >
> > For the rules of voting about code commits, see the project charter,
> > article 11, http://wiki.apache.org/xmlgraphics/ProjectCharter.
>

Re: [VOTE] Merge branch Temp_ComplexScripts into trunk

[Simon Pepping]

The vote runs for three days, and will end on Friday 28 October 2011
at 18:00h UTC.

Simon Pepping

On Tue, Oct 25, 2011 at 10:31:43AM +0200, Simon Pepping wrote:
> 
> Following this request, I herewith propose to merge the branch
> Temp_ComplexScripts into trunk, and launch a formal vote.
> 
> For the rules of voting about code commits, see the project charter,
> article 11, http://wiki.apache.org/xmlgraphics/ProjectCharter.

Re: [VOTE] Merge branch Temp_ComplexScripts into trunk

[Glenn Adams]

The short answer is that if you do not wish to be affected by complex script
support, you can use the new "-nocs" command line option or you can specify
 in your FOP configuration file.

Keep in mind that Latin (Roman), Cyrillic, and Greek scripts also benefit
from support when complex scripts are enabled, since in these cases the
advanced typographic tables (ATT) present in OpenType fonts used with these
scripts are enabled. For example, such tables enable the correct placement
of combining marks (e.g., diacritics and accents) with base characters.

G.

On Tue, Oct 25, 2011 at 8:54 PM, The Web Maestro
wrote:

> > Following this request, I herewith propose to merge the branch
> > Temp_ComplexScripts into trunk, and launch a formal vote.
> >
> > I vote positive: +1
> >
> > For the rules of voting about code commits, see the project charter,
> > article 11, http://wiki.apache.org/xmlgraphics/ProjectCharter.
> >
> > Simon Pepping
>
> This sounds good to me, but I want to ask:
>
> Does this new feature have any impact on people not using Complex
> Scripts in their FOP process?
>
> Regards,
>
> The Web Maestro
> --
>  - 
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
>

Re: [VOTE] Merge branch Temp_ComplexScripts into trunk

[Clay Leeds]

Thanks Pascal! And thank you Glenn! Great work!

+1 from me!

"My religion is simple. My religion is kindness."
- HH The Dalai Lama of Tibet

On Oct 25, 2011, at 6:29 AM, Pascal Sancho  wrote:

> Hi,
> 
> There was a discussion about enabling it by default, with some
> performances tests.
> 
> see http://marc.info/?l=fop-dev&m=131108266423848&w=2
> 
> Le 25/10/2011 14:54, The Web Maestro a écrit :
>>> Following this request, I herewith propose to merge the branch
>>> Temp_ComplexScripts into trunk, and launch a formal vote.
>>> 
>>> I vote positive: +1
>>> 
>>> For the rules of voting about code commits, see the project charter,
>>> article 11, http://wiki.apache.org/xmlgraphics/ProjectCharter.
>>> 
>>> Simon Pepping
>> 
>> This sounds good to me, but I want to ask:
>> 
>> Does this new feature have any impact on people not using Complex
>> Scripts in their FOP process?
>> 
>> Regards,
>> 
>> The Web Maestro
>> --
>>  - 
>> My religion is simple. My religion is kindness.
>> - HH The 14th Dalai Lama of Tibet
>> 
> 
> -- 
> Pascal

Re: [VOTE] Merge branch Temp_ComplexScripts into trunk

[Pascal Sancho]

Hi,

There was a discussion about enabling it by default, with some
performances tests.

see http://marc.info/?l=fop-dev&m=131108266423848&w=2

Le 25/10/2011 14:54, The Web Maestro a écrit :
>> Following this request, I herewith propose to merge the branch
>> Temp_ComplexScripts into trunk, and launch a formal vote.
>>
>> I vote positive: +1
>>
>> For the rules of voting about code commits, see the project charter,
>> article 11, http://wiki.apache.org/xmlgraphics/ProjectCharter.
>>
>> Simon Pepping
> 
> This sounds good to me, but I want to ask:
> 
> Does this new feature have any impact on people not using Complex
> Scripts in their FOP process?
> 
> Regards,
> 
> The Web Maestro
> --
>  - 
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
> 

-- 
Pascal

Re: [VOTE] Merge branch Temp_ComplexScripts into trunk

[The Web Maestro]

> Following this request, I herewith propose to merge the branch
> Temp_ComplexScripts into trunk, and launch a formal vote.
>
> I vote positive: +1
>
> For the rules of voting about code commits, see the project charter,
> article 11, http://wiki.apache.org/xmlgraphics/ProjectCharter.
>
> Simon Pepping

This sounds good to me, but I want to ask:

Does this new feature have any impact on people not using Complex
Scripts in their FOP process?

Regards,

The Web Maestro
--
 - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: [VOTE] Merge branch Temp_ComplexScripts into trunk

[Chris Bowditch]

On 25/10/2011 09:31, Simon Pepping wrote:

With his latest patch, Glenn Adams wrote:


Hi All,



With this latest patch I am satisfied that there is sufficient testing and
stability in the CS branch to support its merger into trunk. Therefore, I
request that such a merge be accomplished after applying patch 5 to the CS
branch.


Although there are some concerns over certain technical aspects in the Complex 
Scripts branch Glenn has spent some time answering our concerns and has made 
some steps towards a compromise. Given the need for this feature in the 
community and the level of testing Glenn has conducted I am happy for the merge 
to proceed. Thanks for your hard work Glenn!






Following this request, I herewith propose to merge the branch
Temp_ComplexScripts into trunk, and launch a formal vote.

I vote positive: +1


+1



For the rules of voting about code commits, see the project charter,
article 11, http://wiki.apache.org/xmlgraphics/ProjectCharter.

Simon Pepping




Chris

Re: [VOTE] Merge branch Temp_ComplexScripts into trunk

[Pascal Sancho]

I vote positive too: +1

Le 25/10/2011 10:31, Simon Pepping a écrit :
> With his latest patch, Glenn Adams wrote:
> 
> With this latest patch I am satisfied that there is sufficient testing and
> stability in the CS branch to support its merger into trunk. Therefore, I
> request that such a merge be accomplished after applying patch 5 to the CS
> branch.
> 
> ... snip ...
> 
> Note that there remains work to be done on CS support, including adding
> support for:
> 
>- additional scripts
>- additional output formats
> 
> At present, support is provided for:
> 
>- Arabic, Hebrew, and Devanagari Scripts
>- PDF output format
> 
> I expect that additional support for other scripts and formats will be added
> over time, either by myself, or other members of the community. However, the
> absence of support for all complex scripts and all output formats should not
> be a deterrent to active use of the support already present. It is now a
> good time to broaden the user community of the CS features, and the best way
> to do that is to bring it into the trunk at this time.
> 
> End of quote
> 
> Following this request, I herewith propose to merge the branch
> Temp_ComplexScripts into trunk, and launch a formal vote.
> 
> I vote positive: +1
> 
> For the rules of voting about code commits, see the project charter,
> article 11, http://wiki.apache.org/xmlgraphics/ProjectCharter.
> 
> Simon Pepping
> 

-- 
Pascal

[VOTE] Merge branch Temp_ComplexScripts into trunk

[Simon Pepping]

With his latest patch, Glenn Adams wrote:

With this latest patch I am satisfied that there is sufficient testing and
stability in the CS branch to support its merger into trunk. Therefore, I
request that such a merge be accomplished after applying patch 5 to the CS
branch.

... snip ...

Note that there remains work to be done on CS support, including adding
support for:

   - additional scripts
   - additional output formats

At present, support is provided for:

   - Arabic, Hebrew, and Devanagari Scripts
   - PDF output format

I expect that additional support for other scripts and formats will be added
over time, either by myself, or other members of the community. However, the
absence of support for all complex scripts and all output formats should not
be a deterrent to active use of the support already present. It is now a
good time to broaden the user community of the CS features, and the best way
to do that is to bring it into the trunk at this time.

End of quote

Following this request, I herewith propose to merge the branch
Temp_ComplexScripts into trunk, and launch a formal vote.

I vote positive: +1

For the rules of voting about code commits, see the project charter,
article 11, http://wiki.apache.org/xmlgraphics/ProjectCharter.

Simon Pepping