Re: [VOTE] Release XML Graphics FOP 2.9

[Clay Leeds]

+1 from me!

Clay Leeds

> On Aug 14, 2023, at 6:47 AM, Simon Steiner  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP 2.9.
> 
> Artifacts can be found there:
> https://people.apache.org/~ssteiner/fop-2.9/
> 
> The release is signed with the key:
> https://people.apache.org/~ssteiner/KEYS
> 
> The vote will end on 21/8/2023
> 
> +1 from me.
> 
> Thanks
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEXJow/yKywC8wJhwwW5Px33zbbeoFAmTaMDUACgkQW5Px33zb
> beo5WA//Xh846bSX9JBf7WZd5MCnZCwxOFhtZw62tCreRNVUzOng1MHbz0rdsPgQ
> lZi9ZGybSjYmgd8x1ewhwc8hwfI/j71WfJIA4H9vWOPGZ6sbnp5EVWOg1mEnn7PL
> dW5RSiqwMDrOiByPcuLUHOMG1iQ7FTE4s7FfmOUyv0r4CjYM1XIKrPVEZZDZb+uW
> s1V85MfGN/vD8kEzgtIUotMrdVPtfquz37G2J83Y5DUVrLDaJQM7C4yWcWWv9itp
> +shY4ZOWIdR16oCy0IeOriN7IR1fZby3q2uHgEJJUwo2sWSTpYZLrjRhtaHi0pl3
> ixVybQvbSdRz11exu6Y/24PBAR2lhCaKKAgOkqqTQPC8e8v9BjY+6W2BcqHjjonH
> aImiM3os5hda+qbqhDruepb7OQ35iicIvtYQCbNhh7eBj0iaYLxmokoI4lG/zsh+
> omJKZJc5FZEOg2hkWiyt2S6s+BHYcZuPAnPEa5zxfhJ6G/cgjU3nh1eIdJHcQtW6
> EqHKL1Zb5/NwK00NDRpvHVV/wH78bhTrN4pxFDdryZP0SbF8vbDmLvZNCfLz5Dlu
> vw5S0LgkrxOeU0J/2gVX92UgVy0PaXz9fnhFUsNphanWFH8td9ARsH2+EbeH4Px3
> 27LMTgBPPjXJ1H1MnxtO2V04j8xRjXA+9Nl6vbICgiQRX0Lzeho=
> =lRVq
> -END PGP SIGNATURE-
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 

Re: [VOTE] Release XML Graphics FOP 2.7

[Clay Leeds]

+1

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

> On Jan 12, 2022, at 5:47 AM, Simon Steiner  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP 2.7.
> 
> Artifacts can be found there:
> http://people.apache.org/~ssteiner/fop-2.7/
> 
> The release is signed with the key:
> https://people.apache.org/~ssteiner/KEYS
> 
> The vote will end on 19/1/2021
> 
> +1 from me.
> 
> Thanks
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEXJow/yKywC8wJhwwW5Px33zbbeoFAmHe2+QACgkQW5Px33zb
> beoj7RAAmFjuUM983LECrg01iP0P5uxJxjjHj1h8C8/4NFGUMB4hV6/S1gCegrN7
> Y7tz417LAaa1A1K5QT44sBenfASfL649D/UNIPoI2BSYlyx7RRQBXnd9JOg6IUMo
> 1qXvZ1FYZ+hkAvTbs2+NJ2othcXqszPZxqwgUunuQETgSqNVKGTTaV8KMsnGqZ4J
> 0v+gx6Lq9mF76f9LmvCD/ES7u13s/5uNXbI3BZTqsXyLWNo9A1t/WqdzaqBbCtQ2
> 7WtMcHm+RRdomjfjSwmWsxtKT7zfQL4js9TiZgU+U6dz6lJ1RqugqsEm8m52Tpbn
> GMKwFGmlHZFLdA233kWVjAplsP+u9YbfvjROuLk/U4V4neEBdgIhJdrpcd4TEG2U
> UwjS5L6t3wtcROGeZdDiPnrovssm1gFUPTuJ7vaNMzfcjJd21Uz+WRO7TNUBU1RC
> qeXprhz5ePbGwskDCVj9VfOo5kFbt5fjePbieLDNEiiaYv0AAPVBz3THzsIenhAE
> N9IN2TtSBsLMehfZHUS5XEdXMHfKQNXqmEbmPohvp1o6C0DN5C4d6aZtC/BCKY9s
> 14ogZswlbB94/xqO4KuFD6iIJ9pl1vEixhCROt+kv7GyA4wToh4rYpi3NZ48HHxC
> dbJe/AHsdUVZAz1PeyQdA1vfVOVrc/10SeT4b9252znmzkCXnWE=
> =Vr4X
> -END PGP SIGNATURE-
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 

Re: [VOTE] Release XML Graphics FOP PDF Images 2.7

[Clay Leeds]

+1 

Thanks Simon!

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

> On Jan 12, 2022, at 5:48 AM, Simon Steiner  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP PDF Images 2.7.
> 
> Artifacts can be found there:
> https://people.apache.org/~ssteiner/fop-pdf-images-2.7/
> 
> The release is signed with the key:
> https://people.apache.org/~ssteiner/KEYS
> 
> The vote will end on 19/1/2021
> 
> +1 from me.
> 
> Thanks
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEXJow/yKywC8wJhwwW5Px33zbbeoFAmHe3CcACgkQW5Px33zb
> bep7sw/7BpBEAYWM2Fjg1d75v9Xx+DRAfRtbCDxupnSqg63NwwLkVKD5t6XPVG0i
> Z9pEN2ESAtr59wyHfxqBI8s/NA17j1ehklXI4TfWf7BsSzJTsfYcwfO0F/7uHS4x
> Iiz8ijy7QHW8wfAMJN3B9ahJFHiYqt+Nh/dOwZs1Z92mjymQnY1Mm2rwtyh/cM7u
> KFtlr2603J6uDvmLyNw+IOlXe81jGj6JPPnYiaS78eJoTKtU1L+dJPrGkSRQtjth
> HcdKMU9lBxpms5QdDInGC3ER1gvsCjcTMs14CtoyBmzIS7u7KbcZSnGM0fsQefZT
> YmwOeyqOasTEcqVnnv81Z8oLIMhpS2Kmny090ErjFgi9A6uDM4eNR2mVgVaImEoP
> 9LmhFzkiCypATaEfwyqD/mz7RrxFPQY1+GmnG96qRGDlTiHOem1VxflSacwKl5fd
> w/MHvxx7qwlSvvyGDm4KYL7DO4uHL4pVexgcvZB5FggOyVWZpbYhxO8LYcCTufl0
> qcma7CZpeeHvEwT10FdaN5nRrF6PUMq5yPhJ5oNFKfdS7rEttvN4Mrp79SkSpgZT
> cfUJMVOmwnIm4ENR5KpA7Vzcz2x0wV7ihNpeLRS5VkR6ZgTk3gez34qOnhIvs/eQ
> QSpw/AfI6kvq4MVmeyHH12R0++As0ywoMcY0qVQcBfdUn12ElOA=
> =8QpJ
> -END PGP SIGNATURE-
> 

Re: [VOTE RESULT] Release XML Graphics FOP PDF Images 2.6

[Clay Leeds]

Thanks again Simon!

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

> On Jan 20, 2021, at 6:35 AM, Simon Steiner  wrote:
> 
> Hi,
> 
> 4+1s, I will make a release
> 
> Thanks
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 

Re: [VOTE RESULT] Release XML Graphics FOP PDF 2.6

[Clay Leeds]

Thanks Simon!

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

> On Jan 20, 2021, at 6:36 AM, Simon Steiner  wrote:
> 
> Hi,
> 
> 4+1s, I will make a release
> 
> Thanks
> 
> 
> 
> 

Re: [VOTE] Release XML Graphics FOP PDF Images 2.6

[Clay Leeds]

+1 from me

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

> On Jan 12, 2021, at 6:45 AM, Simon Steiner  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP PDF Images 2.6.
> 
> Artifacts can be found there:
> https://people.apache.org/~ssteiner/fop-pdf-images-2.6/
> 
> The release is signed with the key:
> https://people.apache.org/~ssteiner/KEYS
> 
> The vote will end on 19/1/2021
> 
> +1 from me.
> 
> Thanks
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEXJow/yKywC8wJhwwW5Px33zbbeoFAl/9te0ACgkQW5Px33zb
> beofMxAAs3g2A+d8MejZQubgoyhfEchioWhGA6FR4NVZd0bLg2oyoaBEcabxj3gw
> Ch0ehWtMV34KZZ1hkghoI827hDOBXKboyO2e/t9+1feYQp+q18yw9+SjdDt9l3ls
> hiOFHe84vMX2c3qJu6ziU8n5SzKgFD2p6qvVykW7pGBwZ9sguoMDsRFOTyosmHpe
> pIm2T8JAx9pHsn7i9nXQxhZWPqTWcV3zfyCnYkxUcH9oP+MvjjbsP5l/nbFAt1jr
> yTy6IHXBnA9lU3SdLMushAR5tj13ZpkiPm0ynt7eirKgo1B96YF/fPAZxezeTBdz
> h+APkRaD435yqJSJBpdwyBLG3y/ANbiwz8gAFDeDhqMbAcvkwnsi7tSDZWJ8w3Dv
> nCkZ4+Ajl6cBFMP8HsiAB+KO9Wj7hrBLiIYk8C206wAw5VZ34o5HX6kPQ0RikMjc
> jLByiqxdd4i4PhJIW5SLJLygH6GQYs2a2smBhWTmDqjznOUs8f+oTOcLsStodjWf
> 9Uy/EZP8a3vH5KAx+bynoUjSRrLU1Ndyxg9K0kSZmHiFxMna/NjkAhEWP6fI4hQT
> TfQEcLGI4v53fIWKcuEKiJwhH4I4HuqFSu5whLkBSwV5Td3Do1URvJVqyY35J5Zr
> Pb2H/+Wcgkjgj8nq1pfZx1RDQc3OA4ryi/WW2TM5wna3G6ms0Ic=
> =7bfs
> -END PGP SIGNATURE-
> 

Re: [VOTE RESULT] Release XML Graphics FOP PDF Images 2.5

[Clay Leeds]

Thank you Simon!

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

> On May 13, 2020, at 12:08 AM, Simon Steiner  
> wrote:
> 
> Hi,
> 
> 3+1s, I will make a release
> 
> Thanks
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 

Re: [VOTE] Release XML Graphics FOP 2.5

[Clay Leeds]

+1 

Thank you for your hard work!

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

> On May 5, 2020, at 7:12 AM, Simon Steiner  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP 2.5.
> 
> Artifacts can be found there:
> http://people.apache.org/~ssteiner/fop-2.5/
> 
> The release is signed with the key:
> https://people.apache.org/~ssteiner/KEYS
> 
> The vote will end on 12/5/2020
> 
> +1 from me.
> 
> Thanks
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEXJow/yKywC8wJhwwW5Px33zbbeoFAl6xdBoACgkQW5Px33zb
> bepcqg/+Pe+MO2KImDxlh2BpDH08/r8uctB1oiFzZ0AWzqAO/cnbNPY9SfIVwMyU
> Dy7fMLxpONJ2GEvn2kbDvvZuRfwjIvw6U7dqv+LJWEZyk0FonfFvFBBdPlsSW66E
> Y7tNdeGd92Qji/SL1IoFN3MnFF73Y1xTsu45hJIUheFnoIf0dsFDnTac7uucFiPq
> +unVqy9u9r5ZLtdOZg6ewmcP5p529aj/cHn5Go14U43xxv9LQvKwxZhszZpVxIH5
> 22oUfjj/tBtGY0O3+yYXtWojXlp2pCgXtjXiEmYkHw7u4hovejMAEpzXC3eJz06z
> PF0RMRT342N2wuntqSvEsYI0Zi1xwEs/6PU/EMLS6f6D+bLp3O/EUrUMImEeynF6
> TB+cqCTFXlYxvmK6ct59E12SPxpcvJdtxBCqVH+jyVJ/a0EwUzZNDIAFKi2pfeft
> ZI8ZikoHfRlrDh5Loo8In2DF6j86rDH4e06k7Ny1wXAoB2odZXqypgAS0w5jkcYq
> cr8ydGsoN5nZIcJuIRyLbjZf79/Vzn/Ob00PCssUCqm0zXHNtZ7HT+D+a+BH+7j+
> cySuN7Ktg3EPfbyvWi63Pwy8iUN+MAIHRRU4fEDszIDS+aW/7P9HwlvUdcWZaRzC
> QMw+FRxPWHvVYT2ZLGZu5b4FYxlu39mtx3wE+lwmlVazorQUQX8=
> =MSk1
> -END PGP SIGNATURE-
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 

Re: [VOTE] Release XML Graphics FOP PDF Images 2.5

[Clay Leeds]

+1 from me!

Thanks for all your hard work!

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

> On May 5, 2020, at 7:14 AM, Simon Steiner  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP PDF Images 2.5.
> 
> Artifacts can be found there:
> https://people.apache.org/~ssteiner/fop-pdf-images-2.5/
> 
> The release is signed with the key:
> https://people.apache.org/~ssteiner/KEYS
> 
> The vote will end on 12/5/2020
> 
> +1 from me.
> 
> Thanks
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEXJow/yKywC8wJhwwW5Px33zbbeoFAl6xdH8ACgkQW5Px33zb
> bep3MBAAmqTrD00KZlTtqAWZDP6s6jGinQB3xEDOTLHLpMTimRZ3ufc41GCZcYVL
> PJ+1fGGYXLQOkfPlUnaWzOzQD9s6Ls56YSixHvCctilC6J0g0XOEP9TcHemZAqfp
> OEJfw2nlTc54JV4+dWrO6uxwSSOhRV7l4E8vlXrUzKSYuM1mHagKRQTHmZo9p/cH
> a/D8GVTyQOgDjyPlEtfOVDzz2TugOSMPZparG1yuCawBwnF6JHh0fAH9dDuw9MB7
> 60ovP05rUABM6WCwgDpKZsGz9HAE//cSzB77LL0M71+8g2aiOjDoXwTGg2Ro+kUx
> 99G1iNLFqfEWiUg+qLA6CXj52QCDa+WSSVS0qNk0oiU9R6ip0I1f2ou+gWPyGz0O
> KshitdNCZjl0/q+29cdNUuP5xOPVeAN8Xl0G7RopWBsXgV0O3z53GA3+YIR46aWe
> DBP0uTPvzP5ZsosJjN584DRM6MQrC+9H7DTSK4LGKuYs3sKGyQRLNMC14XY1JfZj
> I6x+uWCmpu9g8PkbwtqZBimQY9iAV1JBaGVj9DcajgWEqdPFvSo6iYfZ53+tnnny
> u/e3eR6ey0sjYpQixnMXZaEQIuSHdYKL8zoBRg8mF8VZjmZqJCi69kNcrHMA1oBz
> J/kTe38uT31h27KUB4X0g0tCMAwdDJO0edVf01yfx7pcIkWl+Eg=
> =iB9D
> -END PGP SIGNATURE-
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 

Apache Community Survey 2019

[Clay Leeds]

Hello everyone, 

If you have an apache.org email, you should have received an email with an 
invitation to take the 2020 ASF Community Survey. Please take 15 minutes to 
complete it.

If you do not have an apache.orgemail address or you didn’t receive a link, 
please follow this link to the survey:
https://communitysurvey.limequery.org/454363

This survey is important because it will provide us with scientific information 
about our community, and shed some light on how we can collaborate better and 
become more diverse. Our last survey of this kind was implemented in 2016, 
which means that our existing data about Apache communities is outdated. The 
deadline to complete the survey is January 4th, 2020. You can find information 
about privacy on the survey’s Confluence page [1].

Your participation is paramount to the success of this project! Please consider 
filling out the survey, and share this news with your fellow Apache 
contributors. As individuals form the Apache community, your opinion matters: 
we want to hear your voice. 

If you have any questions about the survey or otherwise, please reach out to us!

Kindly, 
ASF Diversity & Inclusion
https://diversity.apache.org/

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

Re: Compliance page for 2.4

[Clay Leeds]

Thank you very much Jan & Simon!

This is great progress (pun intended! ;-)

Great work!

Clay

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

> On Nov 7, 2019, at 12:24 AM, Simon Steiner  wrote:
> 
> Hi,
> 
> I will try to update this page.
> 
> Thanks
> 
> -Original Message-
> From: Jan Tosovsky  
> Sent: 06 November 2019 22:56
> To: fop-dev@xmlgraphics.apache.org
> Subject: Compliance page for 2.4
> 
> Dear All,
> 
> together with releasing change bar support we can switch several rows in
> compliance page to green. I would replace entire 2.3 column with 2.4.
> https://xmlgraphics.apache.org/fop/compliance.html
> https://issues.apache.org/jira/browse/FOP-1760
> 
> Green candidates:
> 
> §6.13.2change-bar-begin
> §6.13.3change-bar-end
> 
> §7.30.1change-bar-class
> §7.30.2change-bar-color
> §7.30.3change-bar-offset
> §7.30.4change-bar-placement
> §7.30.5change-bar-style
> §7.30.6change-bar-width
> 
> Thanks,
> 
> Jan
> 
> 
> 
> 

Re: [VOTE RESULT] Release XML Graphics FOP PDF Images 2.4

[Clay Leeds]

Thank you Simon!

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

> On Nov 5, 2019, at 5:31 AM, Simon Steiner  wrote:
> 
> Hi,
> 
> 4+1s, I will make a release.
> 
> Thanks
> 
> 

Re: [VOTE RESULT] Release XML Graphics FOP 2.4

[Clay Leeds]

Yippee!

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

> On Nov 5, 2019, at 5:31 AM, Simon Steiner  wrote:
> 
> Hi,
> 
> 4+1s, I will make a release.
> 
> Thanks
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 

Re: [VOTE] Release XML Graphics FOP 2.4

[Clay Leeds]

Thank you Simon!

+1

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

> On Oct 25, 2019, at 5:00 AM, Simon Steiner  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP 2.4.
> 
> Artifacts can be found there:
> http://people.apache.org/~ssteiner/fop-2.4/
> 
> The release is signed with the key:
> https://people.apache.org/~ssteiner/KEYS
> 
> The vote will end on 1/11/2019
> 
> +1 from me.
> 
> Thanks
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEXJow/yKywC8wJhwwW5Px33zbbeoFAl2y464ACgkQW5Px33zb
> bepmSA/9EOeWxNJyz3yA3INF2TI8y6dw4EAEs4jLrly50K6THV3Nv8NzBLTir2Dd
> CiAi3Q4RtY8xJOdbMu4YRG/R9aFneEOh4dSnjWwI+Lq0fGt8oduZjLhhoCDA50Bq
> G200PLxCDavHvmfdk8JsSpqqXFFEfkneZ2lQ5AW9y/Ee1FWw29Qj3WMtrhr43E+T
> ji5awLnfQ1xOPmi5tBLgEJDwCUU1YJjs5ZILRjp5CxaJB0d6MFbddaGGSHH83e/R
> x4NqgzmtrxrZEb0Blb6Zxgiy/8W7IJQUhZDZS9YnYnIblXbmXyGuJVfcU+PmjaUX
> Gb1DOZn4Ydj/PawDLeb4tc8uzDH2SFUOQ5bBclUzUELYhwnfB4ASRYNm/jEqI5CF
> ZO5BH++nMGcoBiibyuSUIOSik92+AA64RXUdUn+6Qa+f/XcfuZHVec8H0tdIGv9q
> scCsubm1hw2VgzF4ldtp8y1xVc+cxfAqyg4Jf5LxGMouK6Yp1o1pj2B6eW7XtG8W
> +0io2QcwnZq0dTB+nSUlvyJDOj/Cf9dajaDmArNeS0+kDZyREbHgiZRAvWWlf9wv
> IilKvw0GHeW9ootrFasfPlqMpsvRrpmYvR51xgWFkSDNv+hWj0CWvhzmUFR11d/x
> GHtehj3CKIavp7b9jT+pGuOwFDPwiyczkIRKMT1YZXKykM7ycnI=
> =UoQF
> -END PGP SIGNATURE-
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 

Re: [VOTE] Release XML Graphics FOP PDF Images 2.4

[Clay Leeds]

Thanks Simon!

+1

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

> On Oct 25, 2019, at 5:16 AM, Simon Steiner  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP PDF Images 2.4.
> 
> Artifacts can be found there:
> https://people.apache.org/~ssteiner/fop-pdf-images-2.4/
> 
> The release is signed with the key:
> https://people.apache.org/~ssteiner/KEYS
> 
> The vote will end on 1/11/2019
> 
> +1 from me.
> 
> Thanks
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEXJow/yKywC8wJhwwW5Px33zbbeoFAl2y528ACgkQW5Px33zb
> bepjiQ/+OMnuTYH3Iu0iKGo5WCVDTg8xQ2rSg7tbRU1LUMf3SHRmFeXVb2DgvLXi
> GmC9/Bw6hUwZSp+HNSxv2bdN5Wxukjn3s3pu5A4hHgJ0/66nxogiVk6Ss7i8HSGs
> wiyBBn0w7r6mWb8sUxC97VH6Tf4fejBErsPff3Aa4pon840kto4NG118RhqZLvsx
> 8c3LHygP4pWoGDMElcoBF2z2VKS9SE7Or3/Nd93hsF89b/MKuPJ3xR3a82clGR+1
> WhzNPyRMCKjXqwrVraNdh6VzRdUEmZ6OeDS7/wLUJMmEK5y79FSdV1d1ZmyOje8k
> nFPh6CnpaPilXNNsWlq1M207ZoksDowRmTzOW8qnijBFHzSnR6ZBtE9Hpb8Pp81H
> bHNpMkoiySRq7zpCOgW5JaRt7eGDjv7VlzhzPqCZYmrfC9EfJLEc0Te3H9KywQDW
> 3CBltvAFO16I6vjXp5ZlilmxoWA6dXrTgFNq5sw3APJuAHiOTYVly362O0/7bNGN
> m+xF17C+X8Q4kmLS/pqMeW/grhN5lAI2IpYObBkUAFwh9yc4dJx/lE/pjpZAUDPA
> UWhEVIzixec9xhwoKy4Oar2HALW+YSS2y2+1pBlMTpVQ7rYphqw5F+LxscgIxB+r
> xRVXP/xK5Oz5YPzwCI11d2HDi3iRurKan3onjbED2ktyr29RKNU=
> =zYoz
> -END PGP SIGNATURE-
> 

Re: Moin wiki xmlgraphics-fop successfully migrated to Confluence space XMLGRAPHICSFOP

[Clay Leeds]

Thanks Chris!

Clay Leeds - the.webmaes...@gmail.com

> On Mar 29, 2019, at 9:07 AM, Chris  wrote:
> 
> Hi All,
> 
> I have now migrated the FOP Wiki to confluence. Please use that going 
> forwards. The Moin wiki will go offline after a few weeks
> 
> Chris
> 
>  Forwarded Message 
> Subject:Moin wiki xmlgraphics-fop successfully migrated to Confluence 
> space XMLGRAPHICSFOP
> Date:Fri, 29 Mar 2019 15:31:09 +
> From:ASF Self-Service Platform 
> Reply-To:ASF Infrastructure 
> To:cbowdi...@apache.org, ASF Infrastructure 
> 
> 
> 
> 
> Hi there,
> As requested by cbowdi...@apache.org, migration from moin wiki 
> xmlgraphics-fop to Confluence space has been completed at:
> https://cwiki.apache.org/confluence/display/XMLGRAPHICSFOP
> 
> 
> 
> With regards,
> ASF Self-Service Platform, https://selfserve.apache.org
> For inquiries, please contact: us...@infra.apache.org
> .
> 

Re: [VOTE] Merge Temp_Avalon to trunk

[Clay Leeds]

Thanks Simon (& Chris West and Thomas Pasch!),

It looks like this VOTE actually succeeded. I count 4 +1s and no -1s.

What's the next step? Will there be a release, or is this just a PATCH we 
support in TRUNK/HEAD?

Warm regards,

Clay Leeds  -  the.webmaes...@gmail.com
"My religion is simple. My religion is kindness."
HH the Dalai Lama of Tibet

> On Jan 16, 2019, at 3:26 AM, Simon Steiner  wrote:
> 
> Hi,
> 
> Normally I use fop dev for fop bugs and general when doing a fop release.
> 
> Thanks
> 
> -Original Message-
> From: Clay Leeds  
> Sent: 15 January 2019 14:01
> To: fop-dev@xmlgraphics.apache.org
> Subject: Re: [VOTE] Merge Temp_Avalon to trunk
> 
> +1
> 
> Should this happen on general@?
> 
> Clay
> 
> "My religion is simple. My religion is kindness."
> - HH Dalai Lama of Tibet
> 
>> On Jan 15, 2019, at 2:48 AM, Simon Steiner 
> wrote:
>> 
>> Hi,
>> 
>> Chris West and Thomas Pasch submitted a patch to remove Avalon, since 
>> this dependency is no longer maintained and doesn't compile under Java 9.
>> The vote will last 5 working days, ending next Tuesday. 
>> 
>> https://issues.apache.org/jira/browse/FOP-2733
>> http://svn.apache.org/viewvc/xmlgraphics/fop/branches/Temp_Avalon/
>> 
>> Here is my vote: +1
>> 
>> Thanks
>> 
>> 
>> 
> 

Re: [VOTE] Merge Temp_Avalon to trunk

[Clay Leeds]

+1 

Should this happen on general@?

Clay

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

> On Jan 15, 2019, at 2:48 AM, Simon Steiner  wrote:
> 
> Hi,
> 
> Chris West and Thomas Pasch submitted a patch to remove Avalon, since this
> dependency is no longer maintained and doesn't compile under Java 9.
> The vote will last 5 working days, ending next Tuesday. 
> 
> https://issues.apache.org/jira/browse/FOP-2733
> http://svn.apache.org/viewvc/xmlgraphics/fop/branches/Temp_Avalon/
> 
> Here is my vote: +1
> 
> Thanks
> 
> 
> 

Re: [VOTE] Merge Temp_ChangeBars2 to trunk

[Clay Leeds]

+1 from me

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

> On Jul 5, 2018, at 6:09 AM, Simon Steiner  wrote:
> 
> Hi,
> 
> Stephan Thesing, Jan Tošovský and William Eliot Kimber have made changes to
> support change-bars
> https://www.w3.org/TR/xsl/#fo_change-bar-begin
> 
> The vote will last 5 working days, ending next Thursday. 
> 
> https://issues.apache.org/jira/browse/FOP-1760
> http://svn.apache.org/viewvc/xmlgraphics/fop/branches/Temp_ChangeBars2/
> 
> Here is my vote: +1
> 
> Thanks
> 
> 

Re: [VOTE] Merge Temp_SurrogatePairs to trunk

[Clay Leeds]

+1

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

> On Mar 9, 2018, at 6:04 AM, Simon Steiner  wrote:
> 
> Hi,
> 
> Simone Rondelli has done some changes that allows you to use code points >
> 65535
> 
> The vote will last 5 working days, ending next Friday. 
> 
> https://issues.apache.org/jira/browse/FOP-1969
> http://svn.apache.org/viewvc/xmlgraphics/fop/branches/Temp_SurrogatePairs/
> 
> Here is my vote: +1
> 
> Thanks
> 

Re: [ANN] Apache FOP-PDF-Images 2.2 Released

[Clay Leeds]

Thank you Simon!

Warm regards,

Clay Leeds  -  the.webmaes...@gmail.com
"My religion is simple. My religion is kindness."
HH the Dalai Lama of Tibet

> On Apr 10, 2017, at 7:43 AM, Simon Steiner <simonsteiner1...@gmail.com> wrote:
> 
> The Apache XML Graphics team is pleased to announce the immediate 
> availability of Apache FOP-PDF-Images Version 2.2 [1].
>  
> This package contains classes which add support using PDF images in
> fo:external-graphic elements when you generate PDF files. This means you can 
> write something like:
> 
>  
> Apache FOP-PDF-Images is published under the Apache License v2.0.
>  
> This release fixes a number of bugs. In addition the following significant 
> functional enhancements are provided:
> - Move to PDFBox 2
> - Deduplicate PDF streams
> - PDF to PS deduplication of images
> - Remove xobj type=form
> - Merge fonts (off by default)
> - Support PDF shading to PS
> - Merging of Tagged (Accessible) PDF
>  
> For release notes see [1]. Source and binary distributions can be downloaded 
> from an ASF Mirror at [2]. Further download information is available at [1]. 
> Maven artifacts for this release are available at [3].
>  
> Note, that depending on which download mirror you use, it may take up to 24 
> hours to see the download images at [2].
>  
> [1] https://xmlgraphics.apache.org/fop/fop-pdf-images.html 
> <https://xmlgraphics.apache.org/fop/fop-pdf-images.html>
> [2] http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop-pdf-images 
> <http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop-pdf-images>
> [3] 
> https://repository.apache.org/index.html#nexus-search;gav~org.apache.xmlgraphics~fop-pdf-images~2.2~~
>  
> <https://repository.apache.org/index.html#nexus-search;gav~org.apache.xmlgraphics~fop-pdf-images~2.2~~>
>  
> The Apache XML Graphics team.

Re: Apache PDFBox 2.0.0 released.

[Clay Leeds]

Cool Simon! That's great!

Thanks!

Kind regards,

Clay Leeds  #  949-510-8993  @  the.webmaes...@gmail.com
"My religion is simple. My religion is kindness."
HH the Dalai Lama of Tibet

> On Mar 23, 2016, at 7:30 AM, Simon Steiner <simonsteiner1...@gmail.com> wrote:
> 
> Hi,
> 
> There is pdf-plugin side changes and fop side changes. The story below was
> for pdf-plugin work so far.
> 
> Thanks
> 
> -Original Message-
> From: Simon Steiner [mailto:simonsteiner1...@gmail.com] 
> Sent: 23 March 2016 14:28
> To: fop-dev@xmlgraphics.apache.org
> Subject: RE: Apache PDFBox 2.0.0 released. 
> 
> Hi,
> 
> We have https://issues.apache.org/jira/browse/FOP-2562
> 
> Thanks
> 
> -Original Message-
> From: Clay Leeds [mailto:the.webmaes...@gmail.com]
> Sent: 23 March 2016 14:20
> To: Apache FOP <fop-dev@xmlgraphics.apache.org>
> Subject: Apache PDFBox 2.0.0 released. 
> 
> Hi folks,
> 
> It looks like PDFBox 2.0.0 was released:
> 
> https://pdfbox.apache.org
> 
> Does this mean we'll need to make a release to support its changes?
> 
> I recall a discussion a coulee of months ago that we'd had some code that
> couldn't launch since they were still at 1.8.5 (I think!). 
> 
> I don't know whether it makes sense to do this in conjunction w the Maven
> changes...
> 
> Then again you guys are probably already paying attention to PDFBox anyway.
> ;-)
> 
> Clay
> 
> Sent from my iPhone 6s
> 
> 

Apache PDFBox 2.0.0 released.

[Clay Leeds]

Hi folks,

It looks like PDFBox 2.0.0 was released:

https://pdfbox.apache.org

Does this mean we'll need to make a release to support its changes?

I recall a discussion a coulee of months ago that we'd had some code that 
couldn't launch since they were still at 1.8.5 (I think!). 

I don't know whether it makes sense to do this in conjunction w the Maven 
changes...

Then again you guys are probably already paying attention to PDFBox anyway. ;-)

Clay

Sent from my iPhone 6s

Re: [VOTE] Merge from xmlgraphics/fop/branches/maven to trunk

[Clay Leeds]

+1 from me!

Sent from my iPhone 6s

> On Mar 12, 2016, at 7:13 PM, Glenn Adams  wrote:
> 
> I would like to start a vote on merging from xmlgraphics/fop/branches/maven 
> [1] to trunk [2]. Please respond by Wednesday, 03/16, 1700Z. Lack of a 
> response will be interpreted as +0.
> 
> [1] http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/maven/
> [2] http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/
> 
> The following run without error (on my platform) using both JDK 1.6 and 1.7:
> ant -f fop/build.xml clean all checkstyle findbugs
> mvn clean install checkstyle:check findbugs:check -U
> I am using the following tool versions (with JDK 1.6 enabled):
> 
> bash-3.2$ mvn -v
> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 
> 2014-12-14T10:29:23-07:00)
> Maven home: /opt/local/share/java/maven32
> Java version: 1.6.0_65, vendor: Apple Inc.
> Java home: /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: "mac"
> 
> bash-3.2$ ant -version
> Apache Ant(TM) version 1.9.6 compiled on June 29 2015
> A Jenkins build project is running (without error) at [3], wherein both 
> checkstyle and findbugs analyses are enabled by default.
> 
> [3] https://builds.apache.org/job/xmlgraphics-fop-maven/
> 
> Notes:
> 
> the ant build is run from the fop subdirectory of [1];
> all build artifacts (fop, fop-sandbox, fop-servlet, fop-transcoder, 
> fop-transcoder-allinone) have been verified for content;
> source code is now distributed between fop-util, fop-events, and fop-core 
> modules; this was needed to eliminate a circular dependency between fop and 
> the generation of event infrastructure; i expect some further fine-tuning to 
> occur here over time;
> 

Re: FOP Maven Build Running

[Clay Leeds]

Nice work Glenn!

Sent from my iPhone 6s

> On Mar 8, 2016, at 2:06 AM, Glenn Adams  wrote:
> 
> I now have maven build/test running from [1], with Jenkins job at [2]. Still 
> have to populate fop-{sandbox,servlet,transcoder} modules. Have not yet 
> configured checkstyle, findbugs.
> 
> Temporary work arounds for problems:
> exclude o.a.f.util.bitmap.JAIMonochromeBitmapConverter on compile
> jai not present on Jenkins ubuntu executors
> @Ignore o.a.f.render.pdf.PDFEncodingTest.testPDFEncodingWithStandardFont on 
> test
> fails for yet to be determined reason
> All other junit tests appear to be running.
> 
> Hope to propose a merge vote to start in next few days.
> 
> [1] http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/maven/
> [2] https://builds.apache.org/job/xmlgraphics-fop-maven/
> 

Re: [VOTE] Release XML Graphics FOP 2.1 (2nd attempt)

[Clay Leeds]

Just in case... +1!

Thanks Simon!

Sent from my iPhone 6s

> On Jan 7, 2016, at 7:13 AM, Simon Steiner  wrote:
> 
> Hi,
>  
> Chris asked for a new build and I also added a fix for a pdf to pdf 
> regression.
>  
> Thanks
>  
> From: Glenn Adams [mailto:gl...@skynav.com] 
> Sent: 07 January 2016 14:48
> To: FOP Developers ; XML Graphics Project 
> 
> Subject: Re: [VOTE] Release XML Graphics FOP 2.1 (2nd attempt)
>  
> Unless there was a -1 that needs resolving, there is no need to start a new 
> vote just to fix the status file.
>  
> On Thu, Jan 7, 2016 at 7:23 AM, Simon Steiner  
> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP 2.1, status.xml has been removed.
> 
> Artifacts can be found there:
> https://people.apache.org/~ssteiner/fop-2.1
> 
> The release is signed with the key:
> https://people.apache.org/~ssteiner/KEYS
> 
> The vote will end on 14/1/2016
> 
> +1 from me.
> 
> Thanks
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iQIcBAEBAgAGBQJWjnStAAoJEFuT8d98223qzs4QAKqo+dNlr8yTD8NRBF23tdeh
> gpy7GwW6zQMHMihbRLZVbV+uUAg7KwV9H3WxBMmoZegasTKY6IS+CQulUeQHyJRE
> K/blb9E0wGFJzXDq9HbgLFlq+rYPtAN2myW9KdJ6+Wy219mW7bKOPQwLSQkFCpxi
> MmKFsXLV3BHPPWUK4gTlHkptZwu8L2b/LKw3p9FW3+02S/athgbBeUiG5Qri7yuF
> +Zl1bNoXT6mJ/41aYB6qLIYN/LCgoQoMzoMEKk9IfPcQ5twvB3OP7p4U47mCR0kQ
> Ij7KbuLvUAI44+SFqcVcJ7okBwPoPaE0blPck9yJaEcUNadfXkOpvN/LiapH+9MY
> 41rtKtCczsQBrSYjkF1ubtC4p957oxxvFBDoJf8Qfh3YHTHDBUCP52hTzZYkMBTD
> kZQRoTp5BnhIoJFNHr4F6uTrt9bDLdKsJhM9xL32jWuKFB/VkVbytFbj70kmy5PL
> FXI/6Z8CpkjcVDa9GJpStgRvHTiGNX3vC1kOrMZUzaSg/HwKdpfGMMnaUwWtVvmo
> TxmCWPM+UlMHwGAxhgm+M2ernpkllbgaT1ps4rX1OklYTkK0BVovM5UaWDIamtie
> klPszMDqPjHHuA2a9/OoHIUnYHvely9Ges7Dy8BGFD/BGce7RyM3wH+faxUkxHqg
> 9FqOHlwPkgZHbZMNuP06
> =fPbU
> -END PGP SIGNATURE-
> 
>  

Re: [jira] [Updated] (FOP-2527) RTF first line indent not being rendered by fo:block text-indent

[Clay Leeds]

Hi Luis,

Here're the instructions:

https://confluence.atlassian.com/display/JIRA063/Configuring+Email+Notifications

###
JIRA can send email notifications to users when significant events occur (e.g. 
creation of an issue; completion of an issue).

Email notifications
Disabling email notifications

To disable email notifications for a project, you can remove the notification 
scheme from the project by editing the project and selecting 'None' as the 
project's notification scheme.

Alternatively, you can edit the notification scheme so that no emails are sent.
###

There's more help at the above link.

I suspect one final (nuclear?) options is that you can just disable your JIRA 
account.

NOTE: It's *possible* (although unlikely) that fop-dev@ is also getting these 
emails by default. If that's the case, you would have to unsubscribe from 
fop-dev@. I do *not* think this is likely.

Web Maestro Clay

> On Sep 18, 2015, at 12:48 AM, Luis Ferro  wrote:
> 
> Can someone explain me how to unsubscribe to the jira ticket log emails?
> 
> Thank you in advance,
> LF
> 
> On 17/09/2015 21:17, Stanley Santos de Araújo (JIRA) wrote:
>>  [ 
>> https://issues.apache.org/jira/browse/FOP-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>  ]
>> 
>> Stanley Santos de Araújo updated FOP-2527:
>> --
>> Description:
>> I am using FOP to convert from XHTML to RTF using Antennahouse Stylesheet 
>> for XHTML to XSL-FO transformation.
>> 
>> My scenario is desbribed below:
>> 
>> I am using stylesheet xhtml2fo.xslt and it works fine when parsing XHTML to 
>> PDF, but when I change Fop MIME_TYPE to RTF and execute the same code,  RTF 
>> output file does not contain first line indentation according XHTML style.
>> 
>> 1) XHTML input:
>> 
>> BLAH BLAH BLAH
>> 
>> Stylesheet xhtml2fo.xslt:
>> 
>> http://www.antennahouse.com/XSLsample/sample-xsl-xhtml2fo/xhtml2fo.xsl
>> 
>> 2) FO Output:
>> 
>> BLAH BLAH BLAH
>> 
>> 3) Expected RTF output:
>> 
>> { fiXXX BLAH BLAH BLAH }
>> 
>> 4) I have verified FOP source code and noticed that current version have a 
>> bug on RtfText:
>> 
>> /** constant for left indent first */
>> public static final String LEFT_INDENT_FIRST = "fi-";
>> 
>> 5) Also TextAttributesConverter is not considering text-indent attribute:
>> 
>> public static RtfAttributes convertAttributes(Block fobj)
>> throws FOPException {
>> 
>> FOPRtfAttributes attrib = new FOPRtfAttributes();
>> 
>> attrFont(fobj.getCommonFont(), attrib);
>> 
>> attrFontColor(fobj.getColor(), attrib);
>> 
>> //attrTextDecoration(fobj.getTextDecoration(), attrib);
>> 
>> attrBlockBackgroundColor(fobj.getCommonBorderPaddingBackground(), attrib);
>> 
>> attrBlockMargin(fobj.getCommonMarginBlock(), attrib);
>> 
>> attrBlockTextAlign(fobj.getTextAlign(), attrib);
>> 
>> attrBorder(fobj.getCommonBorderPaddingBackground(), attrib, fobj);
>> 
>> attrBreak(fobj, attrib);
>> 
>> return attrib;
>> }
>> 
>> 6) I implemented the following patch and it is working fine for me. Check 
>> this out:
>> 
>> - Fixed LEFT_INDENT_FIRST to public static final String LEFT_INDENT_FIRST = 
>> "fi";
>> 
>> - New method to convert text-indent attribute:
>> 
>> public static RtfAttributes convertAttributes(Block fobj)
>> throws FOPException {
>> ...
>> attrBlockTextIndent(fobj.getTextIndent(), attrib);
>> ...
>> return attrib;
>> }
>> 
>> private static void attrBlockTextIndent(Length textIndent, 
>> FOPRtfAttributes rtfAttr) {
>> rtfAttr.setTwips(RtfText.LEFT_INDENT_FIRST, textIndent.getValue());
>> }
>> 
>> Thank you!
>> 
>>   was:
>> I am using FOP to convert from XHTML to RTF using Antennahouse Stylesheet 
>> for XHTML to XSL-FO transformation.
>> 
>> My scenario is desbribed below:
>> 
>> I am using stylesheet xhtml2fo.xslt and it works fine when parsing XHTML to 
>> PDF, but when I change Fop MIME_TYPE to RTF and execute the same code,  RTF 
>> output file does not contain first line indentation according XHTML style.
>> 
>> 1) XHTML input:
>> 
>> BLAH BLAH BLAH
>> 
>> Stylesheet xhtml2fo.xslt:
>> 
>> http://www.antennahouse.com/XSLsample/sample-xsl-xhtml2fo/xhtml2fo.xsl
>> 
>> 2) FO Output:
>> 
>> BLAH BLAH BLAH
>> 
>> 3) Expected RTF output:
>> 
>> { fiXXX BLAH BLAH BLAH }
>> 
>> 4) I have verified FOP source code and noticed that current version have a 
>> bug on RtfText:
>> 
>> /** constant for left indent first */
>> public static final String LEFT_INDENT_FIRST = "fi-";
>> 
>> 5) Also TextAttributesConverter is not considering text-indent attribute:
>> 
>> public static RtfAttributes convertAttributes(Block fobj)
>> throws FOPException {
>> FOPRtfAttributes attrib = new FOPRtfAttributes();
>> attrFont(fobj.getCommonFont(), attrib);
>> attrFontColor(fobj.getColor(), attrib);
>> //attrTextDecoration(fobj.getTextDecoration(), attrib);
>>  

Re: 'Validating XSL-FO' on FOP website

[Clay Leeds]

On Aug 28, 2015, at 7:22 AM, Tony Graham tgra...@mentea.net wrote:
 
 
 Please consider adding 'focheck' (https://github.com/AntennaHouse/focheck)
 to the set of schemas listed on the FOP website at
 http://xmlgraphics.apache.org/fop/fo.html#fo-validate
 
 Regards,
 
 Tony Graham.

Fixed in SVN. Should go LIVE to the site during the next push.

Cheers!

Clay

Re: [VOTE] Merge Temp_PCLSoftFont branch with trunk

[Clay Leeds]

+1

Best regards,

Clay Leeds # 714-796-6881

On Aug 4, 2015, at 8:33 AM, Robert Meyer rme...@hotmail.co.uk wrote:

 Hi All,
 
 This is a vote to merge the temporary branch for adding PCL soft font support 
 to FOP trunk.
 
 What this allows for are TrueType fonts to be converted into a PCL native 
 font format. This moves FOP away from using AWT and rasterized characters 
 allowing for PCL output to potentially be generated over a cloud, better 
 rendering quality and smaller documents. Other font formats will still be 
 rasterized but TrueType will now default to being converted for PCL output.
 
 If you want to give it a try please do. The branch can be found here:
 
 http://svn.eu.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_PCLSoftFonts
 
 This vote wll last 6 days (as I'm unavailable this weekend) and will conclude 
 next Monday. 
 
 Here is my +1.
 
 Thanks,
 
 Robert

Fwd: TAC Applications close tomorrow!

[Clay Leeds]

Travel Assistance is available to ApacheConEU in Budapest this Fall…

Deadline is tomorrow...

Details are below.

 Begin forwarded message:
 
 From: Gavin McDonald gmcdon...@apache.org
 Subject: TAC Applications close tomorrow!
 Date: July 16, 2015 at 7:42:01 AM PDT
 To: committ...@apache.org
 
 HI All,
 
 This is a reminder that currently applications are open for Travel Assistance 
 to go to ApacheCon EU Budapest 
 this coming September/October.
 
 Applications close tomorrow night so if you have not applied yet and intend 
 to do so, please act now!
 
 For those that have submitted talks for this event and have not heard back as 
 to whether or not they will be 
 accepted or not; and you intend to apply for assistance based on getting your 
 talks accepted — please DO 
 apply for assistance now anyway, should your talk not be accepted, your 
 assistance application can be 
 cancelled.
 
 See apache.org/travel http://apache.org/travel for more info. 
 See https://cwiki.apache.org/confluence/display/TAC/Application+Criteria 
 https://cwiki.apache.org/confluence/display/TAC/Application+Criteria for 
 more about the process.
 
 Thanks and hope to see you all in Budapest!
 
 Gav… (On behalf of the Travel Assistance Committee)
 
 

Re: Change bars status

[Clay Leeds]

 No real preference here. Your suggestion is OK. 
 In general, in typesetting, a lorem ipsum generator is frequently used to 
 generate dummy text (for 'simple' Latin scripts, that is). See: 
 http://www.lipsum.com
 
 KR
 
 Andreas

Heh...

You can get a similar output using the 'Classic Ipsum' setting on this site:

http://slipsum.com

...but that's not nearly as much fun...

Then there's always:

http://buseyipsum.com

Web Maestro Clay

Re: xercesImpl dependency

[Clay Leeds]

 Can this jar be removed?
 
 I would say so, yes, unless the policy is to keep it for the sake of 
 supporting old JVMs (1.3 and earlier?).

IIRC, FOPs Run page, Java 1.5 and above is required to rub FOP 2.0:

http://xmlgraphics.staging.apache.org/fop/2.0/running.html
System Requirements

The following software must be installed:

Java 1.6 or later Runtime Environment.

Re: [VOTE] Release XML Graphics FOP 2.0 (2nd attempt)

[Clay Leeds]

+1

Cheers!

Clay

--

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

 On May 26, 2015, at 1:33 AM, Simon Steiner simonsteiner1...@gmail.com wrote:
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi,
 
 This is a vote to release XML Graphics FOP 2.0. Findbugs is passing.
 
 Artifacts can be found there:
 https://people.apache.org/~ssteiner/fop-2.0
 
 The release is signed with the key: 
 https://people.apache.org/~ssteiner/KEYS
 
 The vote will end on 2/6/2015
 
 +1 from me.
 
 Thanks
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1
 
 iQIcBAEBAgAGBQJVZC+NAAoJEFuT8d98223qmbQQALDSXQIf+owqV/s/5eXfvSu3
 EvzQtgu6RZEfL6TwZZX/iY3/7RtTF5OPz6b+i9QFpH2TN5fmLM7A720tK0IAjhB1
 oU9RdKH4dakii7uRUOoolGVOAav0K0DDF1/3HSxf1Ys11CraRqKSGEnJH4WYI1Pv
 xvGgQvFpRP2oQm12jTcfx9rolqijDykboEH+uCUF+MzNSoFMo/W93Id4CLpskr3O
 /m+cNXz0YqUdwnsD/1HrzfauozLR/jDOWePj3OnOyw+CXzrtmtil7fytIHzg1YD3
 B2t7+0InDVgEEqY94ojMXTGB9f/5iYfw/Gol4kg40o7H+9FXdO4YoduE5G7qEaKb
 k9QGwaN4DG74vIlB4DtCdJONI9ikgj6xDA8LV/e6XmpFcKEFmsk6HVgoRU9NKKyI
 jH+r4baa2tlR+cGJgeAr8SgjAQ3cf67ynRXBP74k9RPFATwCt5f+9GAVzV+Q/IDd
 LODw0S+2oKmI1lXPS5pLqeoeo7ccBPlI8rzqTd+9L0RqBQ5K7YmUI2ZngqU86NjV
 1GC5R/caPd1kbnhS6alZAKDj5XAv26kHp/wtHPkKcsdBAcpQk+GjEC7UotD1s0VI
 B0Xja4VBxpUyLIp1jcDTkPe0JgXM7CqjY+Y40CCJeJSek2F/HpRy4QKJcZJYUW0v
 NM66eXRXoVEfVRrkwQqq
 =Xhjn
 -END PGP SIGNATURE-
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: general-h...@xmlgraphics.apache.org
 

Re: JIRA access

[Clay Leeds]

Hi Glenn,

Does it make sense to give all PMCs admin rights? IMHO committees could but we 
can draw the line somewhere. ;-)
Cheers!

Clay

--

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

 On May 24, 2015, at 10:34 AM, Glenn Adams gl...@skynav.com wrote:
 
 I've added Andreas to the Committer role on both FOP and XGC. Also, I've 
 added you (Luis) to the Administrator role on FOP and XGC. Someone besides me 
 should be able to administrate these projects.
 
 On Sun, May 24, 2015 at 7:38 AM, Luis Bernardo lmpmberna...@gmail.com 
 wrote:
 
 You need to be added to one of the roles that is able to resolve issues 
 before you can do that.
 
 For FOP and XGC only Glenn has admin rights. For BATIK both Glenn and I have.
 
 
 On 5/24/15 12:47 PM, Andreas Delmelle wrote:
 Hi
 
 Just wondering:
 Should I be able to set JIRA issues to 'Resolved' or assign them to myself, 
 or does this require someone else (Glenn?) to provide me with the 
 appropriate permissions first?
 
 If the latter, can you take care of this?
 
 
 Thanks!
 
 
 KR
 
 Andreas
 
 

Re: JIRA access

[Clay Leeds]

+1

Cheers!

Clay

--

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

 On May 24, 2015, at 12:53 PM, Glenn Adams gl...@skynav.com wrote:
 
 I would not have any problem with that if the group wishes to do so.
 
 On Sun, May 24, 2015 at 1:37 PM, Clay Leeds the.webmaes...@gmail.com wrote:
 Hi Glenn,
 
 Does it make sense to give all PMCs admin rights? IMHO committees could but 
 we can draw the line somewhere. ;-)
 Cheers!
 
 Clay
 
 --
 
 My religion is simple. My religion is kindness.
 - HH The Dalai Lama of Tibet
 
 On May 24, 2015, at 10:34 AM, Glenn Adams gl...@skynav.com wrote:
 
 I've added Andreas to the Committer role on both FOP and XGC. Also, I've 
 added you (Luis) to the Administrator role on FOP and XGC. Someone besides 
 me should be able to administrate these projects.
 
 On Sun, May 24, 2015 at 7:38 AM, Luis Bernardo lmpmberna...@gmail.com 
 wrote:
 
 You need to be added to one of the roles that is able to resolve issues 
 before you can do that.
 
 For FOP and XGC only Glenn has admin rights. For BATIK both Glenn and I 
 have.
 
 
 On 5/24/15 12:47 PM, Andreas Delmelle wrote:
 Hi
 
 Just wondering:
 Should I be able to set JIRA issues to 'Resolved' or assign them to 
 myself, or does this require someone else (Glenn?) to provide me with the 
 appropriate permissions first?
 
 If the latter, can you take care of this?
 
 
 Thanks!
 
 
 KR
 
 Andreas
 

Re: [VOTE] Release XML Graphics FOP 2.0

[Clay Leeds]

I too would prefer no findbugs* warnings going into a Release, and if it's 
'easy' for someone to resolve that issue, then by all means, that's great!

However, I'm not prepared to VETO this RELEASE due to this issue. IIRC, this 
issue has been brought up before, but was never resolved and I don't think now 
is the time to resolve, unless it's relatively painless.

Clay

My +1 remains...

* [OT] heh... AutoCorrect tried to change that to 'windbags'! ;-)

 On May 21, 2015, at 11:00 AM, Glenn Adams gl...@skynav.com wrote:
 
 I would prefer no findbugs warnings going into the release. I'm finding
 more and more commercial uses of code have policies that require no
 findbugs warnings. You can simply add entries to the findbugs-exclude.xml
 file to disable the warnings for the release.
 
 On Thu, May 21, 2015 at 11:42 AM, Simon Steiner simonsteiner1...@gmail.com
 wrote:
 
 Hi,
 
 
 
 Did we agree that these need to be fixed (we never passed a vote to fail
 build on findbugs):
 
 
 
 XGC has no findbugs target in ant.
 
 XGC has 6 compiler warnings.
 
 
 
 FOP has 124 findbugs warnings:
 
 
 https://builds.apache.org/view/XMLGraphics/job/xmlgraphics-fop/ws/build/report_findbugs.html
 
 
 
 Thanks
 
 
 
 *From:* Glenn Adams [mailto:gl...@skynav.com]
 *Sent:* 21 May 2015 18:06
 *To:* FOP Developers; XML Graphics Project
 *Subject:* Re: [VOTE] Release XML Graphics FOP 2.0
 
 
 
 Before you create the final artifact, please ensure there are no compiler,
 checkstyle, or findbugs warnings. Same applies for XGC 2.0.1.
 
 
 
 On Thu, May 21, 2015 at 7:39 AM, Glenn Adams gl...@skynav.com wrote:
 
 +1
 
 
 
 On Thu, May 21, 2015 at 7:21 AM, Simon Steiner simonsteiner1...@gmail.com
 wrote:
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi,
 
 This is a vote to release XML Graphics FOP 2.0.
 
 Artifacts can be found there:
 https://people.apache.org/~ssteiner/fop-2.0
 
 The release is signed with the key:
 https://people.apache.org/~ssteiner/KEYS
 
 The vote will end on 28/5/2015
 
 +1 from me.
 
 Thanks
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1
 
 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz
 M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS
 maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5
 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd
 QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9
 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp
 Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg
 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v
 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+
 kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW
 OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx
 Vs3s8aMGH8xBEN0SEv+l
 =t6hJ
 -END PGP SIGNATURE-

Re: FOP Committer

[Clay Leeds]

Congratulations Matthias!

Welcome to Apache XML Graphics!

We will be giving you some newbie information soon. In the meantime, you can 
look here to double-check if your chosen Committer name is taken:

http://people.apache.org/committer-index.html

TIP: I think 'matthias' might be available. ;-)
Cheers!

Clay

--

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

 On May 12, 2015, at 4:43 AM, Chris Bowditch bowditch_ch...@hotmail.com 
 wrote:
 
 Hi Matthias,
 
 The XMLGraphics PMC has voted to grant you the rights of committership on the 
 FOP project. If you accept can you let me know your preferred userid so I can 
 create your account?
 
 Thanks,
 
 Chris

Re: Float implementation - no reference in status.xml?

[Clay Leeds]

We are no longer using .xml files for documentation…

You need to follow the instructions here:

https://www.apache.org/dev/cms.html https://www.apache.org/dev/cms.html

Here’s some info about the change (the WHY):

https://www.apache.org/dev/infra-site.html 
https://www.apache.org/dev/infra-site.html

Good luck!

Clay

 On May 8, 2015, at 9:53 AM, Andreas Delmelle andreas.delme...@telenet.be 
 wrote:
 
 Hi all
 
 Something that caught my eye: while browsing status.xml, I could not find a 
 reference to the basic side-float implementation that was merged into trunk a 
 while back.
 
 Maybe it’s just me, but this is precisely the kind of enhancement I would 
 want to see advertised in a future release. Get as much people as possible to 
 try it out and report back on quirks, strange side-effects, etc.
 
 An oversight? Or are we not actively maintaining that file anymore?
 
 
 KR
 
 Andreas

Re: Float implementation - no reference in status.xml?

[Clay Leeds]

 Thanks! Definitely some catching up to do here!
 
 Just tried it, and looks straightforward enough. Strange that I can edit the 
 page, but in edit mode, I still see yesterday's source? I mean, the change 
 you applied yesterday is not yet visible in the source code.
 
 Sensors are detecting ruptures in the cyber-spacetime continuum... :-)

Yeah… That *is* strange… it shouldn’t be like that...

You can also make changes via CLI if you’d like, but this is pretty convenient… 
That said, there have been discussions about changing *again* to something 
else… I forget where that resolved, but I guess as long as we’re moving folks 
think we’re moving forward…

Cheers!

Clay Leeds  #  949-510-8993  @  the.webmaes...@gmail.com
My religion is simple. My religion is kindness.
HH the Dalai Lama of Tibet

[jira] [Resolved] (FOP-2467) Syntax error in DOAP file release section; wrong bug-database URL

[Clay Leeds (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOP-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Clay Leeds resolved FOP-2467.
-
Resolution: Fixed
  Assignee: Clay Leeds

DOAP file updated. Please confirm.

 Syntax error in DOAP file release section; wrong bug-database URL
 -

 Key: FOP-2467
 URL: https://issues.apache.org/jira/browse/FOP-2467
 Project: Fop
  Issue Type: Bug
 Environment: 
 http://svn.apache.org/repos/asf/xmlgraphics/site/trunk/content/fop/doap.rdf
Reporter: Sebb
Assignee: Clay Leeds

 The DOAP still shows Bugzilla for the bug database.
 DOAP files can contain details of multiple release Versions, however each 
 must be listed in a separate release section, for example:
 release
   Version
 nameApache XYZ/name
 created2015-02-16/created
 revision1.6.2/revision
   /Version
 /release
 release
   Version
 nameApache XYZ/name
 created2014-09-24/created
 revision1.6.1/revision
   /Version
 /release
 Please can the project DOAP be corrected accordingly?
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: FOP Release

[Clay Leeds]

One of the changes for PDFBox 2.0.0 (from what I gather from the PDFBox ‘Ideas’ 
page), is a switch to Java 1.6.

We discussed a switch for FOP that required a higher version of Java (I believe 
it was 1.6, but don’t recall).

But I can’t find anywhere on our site that indicates what the minimum Java 
requirement actually is. I’d like to update the site to include the minimum 
requirements if someone can let me know what those are… ;-)

Clay

 On Apr 21, 2015, at 8:21 AM, Simon Steiner simonsteiner1...@gmail.com wrote:
 
 Hi,
  
 Since Batik and XGC have been released, are we ready to release FOP?
  
 It has been said we can’t release PDF plugin using a snapshot release of 
 PDFBox 2.0. PDFBox 1.8 is missing font parsing libraries we need for font 
 merging.
 We could make release a PDF plugin beta release using snapshot of PDFBox or 
 ask user to use PDF plugin snapshot version with FOP 2.0.
  
 Thanks

Re: [VOTE] Merge Temp_PDFLinearization to trunk

[Clay Leeds]

D'oh! Thanks!

Cheers!

Clay

--

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

 On Feb 10, 2015, at 6:04 AM, Chris Bowditch bowditch_ch...@hotmail.com 
 wrote:
 
 Hi Clay,
 
 Only votes affecting all projects must be held on general, e.g. new 
 committers to give the whole PMC the opportunity to vote. Merging a branch in 
 FOP is very FOP specific, so its fine to hold the vote on fop-dev@
 
 Thanks
 
 Chris
 
 On 10/02/2015 13:34, Clay Leeds wrote:
 D'oh! VOTEs must be on general@, so please everyone reply to general@ with 
 your VOTE so it will count...
 
 Here's my +1... Great work Simon!
 
 Web Maestro Clay
 
 On Feb 10, 2015, at 2:54 AM, Simon Steiner simonsteiner1...@gmail.com 
 wrote:
 
 Hi,
  Vote to merge PDF Linearization branch to trunk.
 Linearization is helpful to allow viewing of a pdf over a slow connection.
  Feature will be disabled by default, can be enabled with
  fop version=1.0
   renderers
 renderer mime=application/pdf
   linearizationtrue/linearization
 /renderer
   /renderers
 /fop
  The vote will last 5 working days, ending next Tuesday.
  https://issues.apache.org/jira/browse/FOP-2445 
 https://issues.apache.org/jira/browse/FOP-2445
 https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_PDFLinearization
  
 https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_PDFLinearization
  Here is my vote: +1
  Thanks
 

Re: [VOTE] Merge Temp_PDFLinearization to trunk

[Clay Leeds]

+1 from me... Great work Simon!

 On Feb 10, 2015, at 2:54 AM, Simon Steiner simonsteiner1...@gmail.com wrote:
 
 Hi,
  
 Vote to merge PDF Linearization branch to trunk.
 Linearization is helpful to allow viewing of a pdf over a slow connection.
  
 Feature will be disabled by default, can be enabled with
  
 fop version=1.0
   renderers
 renderer mime=application/pdf
   linearizationtrue/linearization
 /renderer
   /renderers
 /fop
  
 The vote will last 5 working days, ending next Tuesday.
  
 https://issues.apache.org/jira/browse/FOP-2445 
 https://issues.apache.org/jira/browse/FOP-2445
 https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_PDFLinearization
  
 https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_PDFLinearization
  
 Here is my vote: +1
  
 Thanks

Re: [VOTE] Merge Temp_PDFLinearization to trunk

[Clay Leeds]

D'oh! VOTEs must be on general@, so please everyone reply to general@ with your 
VOTE so it will count...

Here's my +1... Great work Simon!

Web Maestro Clay

 On Feb 10, 2015, at 2:54 AM, Simon Steiner simonsteiner1...@gmail.com wrote:
 
 Hi,
  
 Vote to merge PDF Linearization branch to trunk.
 Linearization is helpful to allow viewing of a pdf over a slow connection.
  
 Feature will be disabled by default, can be enabled with
  
 fop version=1.0
   renderers
 renderer mime=application/pdf
   linearizationtrue/linearization
 /renderer
   /renderers
 /fop
  
 The vote will last 5 working days, ending next Tuesday.
  
 https://issues.apache.org/jira/browse/FOP-2445 
 https://issues.apache.org/jira/browse/FOP-2445
 https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_PDFLinearization
  
 https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_PDFLinearization
  
 Here is my vote: +1
  
 Thanks

Re: [VOTE] Merge Temp_MergeTaggedPDF to trunk

[Clay Leeds]

And once more to *really* be complete!

My +1... Just making it count! Great work!

Web Maestro Clay

 On Feb 10, 2015, at 5:36 AM, Clay Leeds the.webmaes...@gmail.com wrote:
 
 And once more for completeness...
 
 VOTEs must be on general@, so please everyone reply to general@ with your 
 VOTE so it will count...
 
 Here's my +1... Great work Thanasis and Thanks Simon!
 
 Web Maestro Clay
 
 p.s. Yasoo! Efharisto poli!
 
 On Feb 10, 2015, at 3:04 AM, Simon Steiner simonsteiner1...@gmail.com 
 mailto:simonsteiner1...@gmail.com wrote:
 
 Hi,
  
 Thanasis Giannimaras provided patch to merge Tagged PDF for pdf plugin and 
 small patch for fop.
  
 Known Limitations :
  
 - Only PDF with marked-content sequences in the page content stream are 
 supported. Marked-content sequences in content stream other than the content 
 stream of the page are not supported.
 - Repeated headers and footers are not completely supported. Example: 2-page 
 pdf including table that spans both pages with repeated header. If you merge 
 the second page, the table header will be visible in the pdf but the reader 
 will ignore it (same principle applies for repeated footers).
  
 In order to use this feature, accessibility must be enabled in the 
 configuration file and the source pdf must be accessible (tagged).
  
 The vote will last 5 working days, ending next Tuesday.
  
 https://issues.apache.org/jira/browse/FOP-2436 
 https://issues.apache.org/jira/browse/FOP-2436
 https://svn.apache.org/repos/asf/xmlgraphics/fop-pdf-images/branches/Temp_MergeTaggedPDF
  
 https://svn.apache.org/repos/asf/xmlgraphics/fop-pdf-images/branches/Temp_MergeTaggedPDF
  
 Here is my vote: +1
  
 Thanks
 

Re: [jira] [Updated] (FOP-2441) pdf:embedded-file extension is broken, gives NullPointerException

[Clay Leeds]

I sent a note to infra@ to see if they can clear things up.

Web Maestro Clay

 On Jan 24, 2015, at 12:09 PM, Luis Bernardo lmpmberna...@gmail.com wrote:
 
 
 I see. Chris is the PMC chair and may be able to explain/fix it.
 
 On 1/24/15 8:42 PM, Luca Furini wrote:
 Luis Bernardo wrote:
 
 I am under the impression that committership rights are never revoked but I
 could be wrong. Are you sure that you can log in to your Apache account?
 Maybe a year ago or so Apache forced a change in passwords. Did you change
 your password when that happened?
 Yes, I remember changing the password when requested.
 
 When I try to commit I get a 403 forbidden error message after being
 requested username and password (by comparison, if I enter a wrong
 username / password I keep being asked to enter them correctly).
 
 I think my apache account still exists as I can log in to
 https://id.apache.org, and I'm in the commiters list at
 http://people.apache.org/committer-index.html#lfurini (although I'm
 not assigned to any svn projects).
 
 On the other hand I have been inactive for several years, so I
 wouldn't be surprised or offended if someone / an authomatic procedure
 revoked my powers ...
 
 So ... does anyone has any ideas? :-)
 
 Bye
 Luca
 

Re: [VOTE] merge branches/Temp_BasicSideFloats to trunk

[Clay Leeds]

Looks like a great addition, Luis!

+1 from me!

Cheers!

Clay

--

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

 On Nov 25, 2014, at 3:05 PM, Luis Bernardo lmpmberna...@gmail.com wrote:
 
 
 Includes layout tests.
 
 On 11/25/14, 5:14 PM, Glenn Adams wrote:
 What are your plans for testing? I haven't looked, but does your branch 
 include new unit tests for this feature?
 
 On Tue, Nov 25, 2014 at 7:41 AM, Luis Bernardo lmpmberna...@gmail.com 
 wrote:
 
 I would like to merge the branch branches/Temp_BasicSideFloats to trunk. 
 The branch has a implementation of side floats that uses the same approach 
 used when handling change in IPD across pages.
 
 These are the known limitations:
 -- the clear fo:float attribute is ignored; only the float attribute 
 (left or right) is used
 -- overlapping of floats in the Y is not handled (even in the case there 
 would not be overlap in the X direction)
 -- floats that extend beyond the body region are not properly handled and 
 will overflow past the edge of the region
 -- if a float extends to bottom of the body region and there are footnotes 
 in the page the float may overlap with the footnote region
 -- floats next to a table are not supported unless the start and end of the 
 table happens in between the start and end of the float
 
 Examples can be found in the thread with subject RFC: basic side floats 
 in this mailing list.
 
 To follow due process and since this will be a new major feature I am 
 launching a vote.
 
 Please vote or report a bug before the end of Monday UTC, December 1st.
 
 
 

Re: nightly snapshots page broken?

[Clay Leeds]

The changes have been checked into SVN. Hopefully we'll see the changes soon! 
;-)

Cheers!

Clay

--

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

 On Oct 13, 2014, at 8:19 AM, Clay Leeds the.webmaes...@gmail.com wrote:
 
 I'll report back when I get more information. 
 
 Cheers!
 
 Clay
 
 --
 
 My religion is simple. My religion is kindness.
 - HH The Dalai Lama of Tibet
 
 On Oct 13, 2014, at 5:51 AM, Clay Leeds the.webmaes...@gmail.com wrote:
 
 Will do. 
 
 Cheers!
 
 Clay
 
 --
 
 My religion is simple. My religion is kindness.
 - HH The Dalai Lama of Tibet
 
 On Oct 10, 2014, at 2:23 AM, Luis Bernardo lmpmberna...@gmail.com wrote:
 
 Yes, I saw that but I was not able to figure out how to fix it. This 
 probably happened when we changed our site and it seems we need to provide 
 the CI folks with a new header file.
 
 Clay, can you please follow up with INFRA-8443 and provide a new header 
 file?
 
 On Wed, Oct 8, 2014 at 9:06 PM, Glenn Adams gl...@skynav.com wrote:
 Thanks! Now we need to fix the HTML on that page [1], which links appear 
 to all be broken, missing style sheet, etc.
 
 [1] http://ci.apache.org/projects/xmlgraphics/fop/snapshots/
 
 On Wed, Oct 8, 2014 at 11:51 AM, Luis Bernardo lmpmberna...@gmail.com 
 wrote:
 
 This has been addressed by INFRA and the nightly builds link are working 
 again.
 
 
 On 10/8/14, 12:17 AM, Luis Bernardo wrote:
 
 FYI, I submitted a request to INFRA (INFRA-8443) since I don't think we 
 can fix this ourselves.
 
 The buildbot logs are here: http://ci.apache.org/builders/fop-trunk
 
 On 10/1/14, 4:14 PM, Glenn Adams wrote:
 thanks! i had an inquiry from someone looking for the nighly snapshots; 
 i think it was working a few months ago, as i recall checking that page 
 then and it showed recent builds
 
 On Wed, Oct 1, 2014 at 2:11 AM, Luis Bernardo lmpmberna...@gmail.com 
 wrote:
 I think this was set up by Simon Pepping years ago and I don't know 
 how this is configured but I will investigate.
 
 On Wed, Oct 1, 2014 at 3:30 AM, Glenn Adams gl...@skynav.com wrote:
 http://ci.apache.org/projects/xmlgraphics/fop/snapshots/ appears to 
 be broken, with no links to builds, other broken links, etc
 
 clay? luis?
 

Re: nightly snapshots page broken?

[Clay Leeds]

Will do. 

Cheers!

Clay

--

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

 On Oct 10, 2014, at 2:23 AM, Luis Bernardo lmpmberna...@gmail.com wrote:
 
 Yes, I saw that but I was not able to figure out how to fix it. This probably 
 happened when we changed our site and it seems we need to provide the CI 
 folks with a new header file.
 
 Clay, can you please follow up with INFRA-8443 and provide a new header file?
 
 On Wed, Oct 8, 2014 at 9:06 PM, Glenn Adams gl...@skynav.com wrote:
 Thanks! Now we need to fix the HTML on that page [1], which links appear to 
 all be broken, missing style sheet, etc.
 
 [1] http://ci.apache.org/projects/xmlgraphics/fop/snapshots/
 
 On Wed, Oct 8, 2014 at 11:51 AM, Luis Bernardo lmpmberna...@gmail.com 
 wrote:
 
 This has been addressed by INFRA and the nightly builds link are working 
 again.
 
 
 On 10/8/14, 12:17 AM, Luis Bernardo wrote:
 
 FYI, I submitted a request to INFRA (INFRA-8443) since I don't think we 
 can fix this ourselves.
 
 The buildbot logs are here: http://ci.apache.org/builders/fop-trunk
 
 On 10/1/14, 4:14 PM, Glenn Adams wrote:
 thanks! i had an inquiry from someone looking for   the nighly 
 snapshots; i think it was working a few months ago, as i recall checking 
 that page then and it showed recent builds
 
 On Wed, Oct 1, 2014 at 2:11 AM, Luis Bernardo lmpmberna...@gmail.com 
 wrote:
 I think this was set up by Simon Pepping years ago and I don't know how 
 this is configured but I will investigate.
 
 On Wed, Oct 1, 2014 at 3:30 AM, Glenn Adams gl...@skynav.com wrote:
 http://ci.apache.org/projects/xmlgraphics/fop/snapshots/ appears to be 
 broken, with no links to builds, other broken links, etc
 
 clay? luis?
 
 
 
 
 
 

Re: nightly snapshots page broken?

[Clay Leeds]

I'll report back when I get more information. 

Cheers!

Clay

--

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

 On Oct 13, 2014, at 5:51 AM, Clay Leeds the.webmaes...@gmail.com wrote:
 
 Will do. 
 
 Cheers!
 
 Clay
 
 --
 
 My religion is simple. My religion is kindness.
 - HH The Dalai Lama of Tibet
 
 On Oct 10, 2014, at 2:23 AM, Luis Bernardo lmpmberna...@gmail.com wrote:
 
 Yes, I saw that but I was not able to figure out how to fix it. This 
 probably happened when we changed our site and it seems we need to provide 
 the CI folks with a new header file.
 
 Clay, can you please follow up with INFRA-8443 and provide a new header file?
 
 On Wed, Oct 8, 2014 at 9:06 PM, Glenn Adams gl...@skynav.com wrote:
 Thanks! Now we need to fix the HTML on that page [1], which links appear to 
 all be broken, missing style sheet, etc.
 
 [1] http://ci.apache.org/projects/xmlgraphics/fop/snapshots/
 
 On Wed, Oct 8, 2014 at 11:51 AM, Luis Bernardo lmpmberna...@gmail.com 
 wrote:
 
 This has been addressed by INFRA and the nightly builds link are working 
 again.
 
 
 On 10/8/14, 12:17 AM, Luis Bernardo wrote:
 
 FYI, I submitted a request to INFRA (INFRA-8443) since I don't think we 
 can fix this ourselves.
 
 The buildbot logs are here: http://ci.apache.org/builders/fop-trunk
 
 On 10/1/14, 4:14 PM, Glenn Adams wrote:
 thanks! i had an inquiry from someone looking for the nighly snapshots; 
 i think it was working a few months ago, as i recall checking that page 
 then and it showed recent builds
 
 On Wed, Oct 1, 2014 at 2:11 AM, Luis Bernardo lmpmberna...@gmail.com 
 wrote:
 I think this was set up by Simon Pepping years ago and I don't know how 
 this is configured but I will investigate.
 
 On Wed, Oct 1, 2014 at 3:30 AM, Glenn Adams gl...@skynav.com wrote:
 http://ci.apache.org/projects/xmlgraphics/fop/snapshots/ appears to be 
 broken, with no links to builds, other broken links, etc
 
 clay? luis?
 

Re: [VOTE] Enable findbugs

[Clay Leeds]

Don't VOTES need to go on general@?

+1 from me. 
Cheers!

Clay

--

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

 On Sep 4, 2014, at 5:48 AM, Simon Steiner simonsteiner1...@gmail.com 
 wrote:
 
 Hi,
  
 Vote to fail fop on Jenkins if findbugs 2.0.3 finds a warning. The exclude 
 file has been updated so present warning types are excluded therefore more 
 controversial warnings are not enabled.
  
 You would at minimum only maintain exclude file.
  
 The vote will run for 7 days until 11 Sept.
  
 Here's my +1
  
 Thanks

Re: [VOTE] Merge Temp_FontMerging to trunk

[Clay Leeds]

Will there be 'one last release using Java 5’ enabling the most widespread use 
of the latest FOP development or does this mean that the last version of Java 5 
support will be FOP 1.1?

Either way, I think this is a great improvement!

Great work, Simon!

+1 from me.

On Jun 23, 2014, at 8:11 AM, Chris Bowditch bowditch_ch...@hotmail.com wrote:
 Hi Simon,
 
 This branch represents many months of hard work. Merging fonts within 
 separate PDFs is far from a trivial task, and has been requested by almost 
 everyone who uses the PDF Plug-in. Thanks you and well done on bringing the 
 implementation to this point.
 
 I downloaded the branch and ran a couple of basic tests, seems ok from a high 
 level. Therefore I am +1 to merge this branch into trunk
 
 Thanks,
 
 Chris
 
 On 20/06/2014 12:23, Simon Steiner wrote:
 
 Hi,
 
 I have been working on merging fonts inside pdf external graphic using the 
 pdf-plugin. The feature is disabled by default and can be enabled using 
 fop.xconf:
 
 fop version=1.0
 
  renderers
 
renderer mime=application/pdf
 
 merge-fontstrue/merge-fonts
 
/renderer
 
  /renderers
 
 /fop
 
 It is using pdfbox 2.0 snapshot which requires Java 6 or later so you vote 
 needs to agree to end support for Java 5 on trunk.
 
 It is supporting fonts of type CFF, Truetype, CID and Type1.
 
 The vote will last 5 working days, ending next Friday.
 
 https://issues.apache.org/jira/browse/FOP-2302
 
 https://svn.apache.org/repos/asf/xmlgraphics/fop-pdf-images/branches/Temp_FontMerging
 
 https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_FontMerging
 
 Here is my vote: +1
 
 Thanks
 
 

Re: FOP Release Automation

[Clay Leeds]

Agreed, ‘some’ people wouldn’t be happy with that. ;-)

I wonder if the CMS Web interface could be extended to allow for a few keywords 
like FOP_VERSION, FOP_REVISION, FOP_BRANCH, etc.

The CMS tool's WYSIWYG interface indicates it uses the Wysiwym MarkDown Editor, 
which is extensible:

https://web.archive.org/web/20110121060932/http://wmd-editor.com/

(site’s down  hasn’t been updated since 2011)...

or

https://code.google.com/p/wmd/

We might still need to do some ANT hanky panky, but at least if we could 
leverage WMD’s extensibility it would help us get where we’re trying to go?

Clay

On May 30, 2014, at 7:19 AM, Robert Meyer rme...@hotmail.co.uk wrote:
 Hi,
 
 I like the simplicity of your idea, but the web interface is not so easy to 
 dismiss unfortunately.
 
 If you do have a copy with those tags in, if any changes are made on the web 
 interface then that copy would become out of date.
 
 We could always shutdown the web interface, but I don't think too many people 
 would be happy with that ;-)
 
 Regards,
 
 Robert
 
 From: simonsteiner1...@gmail.com
 To: fop-dev@xmlgraphics.apache.org
 Subject: RE: FOP Release Automation
 Date: Fri, 30 May 2014 14:48:15 +0100
 
 Hi,
  
 Simple way is to store docs inside fop repo:
  
 Fop/docs/index.markdown
  
 Inside markdown file you reference ant properties eg:
 ${version}
  
 Then you call which does ant expandproperties and calls markdown to html tool:
 ant docs
  
 Then you call which does a zip, scp and unzip of html files to web server:
 ant upload-docs
  
 This method doesn’t support web interface of editing files but I don’t see 
 how this is really needed.
 If I submit a patch to fop it should also contain doc changes rather than 
 having separate repo and patch for that.
  
 Thanks
  
 From: Robert Meyer [mailto:rme...@hotmail.co.uk] 
 Sent: 30 May 2014 14:05
 To: fop-dev@xmlgraphics.apache.org
 Subject: RE: FOP Release Automation
  
 Hi,
 
 After investigating your suggestions Clay I have found that svn-hooks can't 
 be used for the purpose we require unfortunately as it may lead to problems 
 with how SVN operates and also may have some unexpected results with files 
 being committed. This is stated in the documentation under Creating 
 Repository Hooks highlighted in the warning red box further down:
 
 http://www-inst.eecs.berkeley.edu/~cs61b/fa09/docs/svn-book-html-chunk/svn.reposadmin.create.html
 
 Pascal, I agree that the process is fairly straightforward, but I have been 
 asked to automate this further so am just looking into ideas presently.
 
 I think a possible way forward then would be to use your suggestion Pascal of 
 placing the versioned docs for the site inside the FOP repository for their 
 associated version. These can then be referenced using the svn-externals from 
 the main site repository.
 
 In addition to this, the main site files (which would need to be updated) 
 could contain tags for the last three versions which would be replaced using 
 Clay's markdown pre-processor suggestion. The pre-processor would replace the 
 tags with values stored in a properties file in the main site repository.
 
 To create a release, the user would need to update the svn-external 
 references to account for the new version and update the properties file for 
 tag replacement. When the properties file is pushed it will be read by the 
 custom markdown pre-processor and display the new version when rendered.
 
 Those two stages could be done using a single script to simplify things 
 further, but the main complication is getting the markdown pre-processor 
 working. From looking at this page:
 
 http://www.apache.org/dev/cmsref.html#markdown
 
 I am guessing we use PyPy (Python Markdown) which supports extensions, so I 
 will look at this shortly to try out a small example and investigate the 
 feasibility of doing this. There is also the matter of updating the versioned 
 documents for each FOP when a new version is released, but maybe this could 
 be done with the pre-processor as well.
 
 Anyway, let me know what you think.
 
 Regards,
 
 Robert

Re: FOP Release Automation

[Clay Leeds]

Thank you for looking at this, Robert. I'll take a look at MarkDown solutions 
as well. 

Cheers!
Clay

--

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

 On May 21, 2014, at 2:24 AM, Robert Meyer rme...@hotmail.co.uk wrote:
 
 Hi All,
 
 I've been asked to look at a way to automate the FOP release process with 
 regards the website documentation. At the moment every new release requires 
 the following:
 
 1) Download the site from SVN
 2) Copy the folder containing the latest version's markdown files (1.1 for 
 example) and rename to the new version
 3) Go through all the files manually and update all the references from the 
 old to the new version
 4) Update any markdown files in the main directory with regard to the current 
 and previous versions.
 5) Delete the oldest version folder as we need only mantain the last 3.
 6) Check and resubmit all files back to SVN
 
 My initial thought would to have a master copy in a separate directory. That 
 copy would contain a tag in place where the version is given which could be 
 substituted by a script of some kind (ant has a facility to do this). The ant 
 script would also perform all of the above tasks so the only thing left to 
 the user will be to check the output and push the new files. The problem I 
 have with this is that SVN is not the only way in which the files can be 
 edited as there is the web interface. If someone were to edit the files from 
 there, the master copies would become out of date and worse, if someone were 
 to perform a release it would overwrite all those changes.
 
 I've been recommended to look at markdown extensions but if anyone else has 
 any ideas on the best way to go about this it would be much appreciated.
 
 Thanks,
 
 Robert Meyer

Re: [VOTE] Add Type 1 subset support

[Clay Leeds]

Thanks for this explanation and the work you’ve done to implement, Robert,

Here’s my +1

On May 16, 2014, at 9:20 AM, Robert Meyer rme...@hotmail.co.uk wrote:
 Hi Chris,
 
 Here are some performance statistics for three different types of fonts:
 
 TrueType:
 Full = 1123ms
 Subset = 1137ms
 Difference = 1.2%
 
 OpenType:
 Full = 3497ms
 Subset = 3512ms
 Difference = 0.4%
 
 Type 1:
 Full = 1148ms
 Subset = 1896ms
 Difference = 39%
 
 The reason for this can be easily explained. Type 1 fonts contain Postscript 
 code. OpenType and TrueType do not as they only contain binary data. This 
 means no special effort by them has to be made to parse, understand and 
 reconstruct what is effectively another high level programming language.
 
 Because of this deficit, it may be best to leave it as an option as per 
 Vincent's suggestion unless the user wants to create a smaller file and incur 
 the hit. In the meantime I could investigate in the near future whether any 
 performance improvements could be made to speed up the process. It's likely 
 though this will never result in it being close to either OTF or TTF levels 
 of performance.
 
 Best Regards,
 
 Robert 
 
  Date: Fri, 16 May 2014 08:33:52 +0100
  From: bowditch_ch...@hotmail.com
  To: fop-dev@xmlgraphics.apache.org
  Subject: Re: [VOTE] Add Type 1 subset support
  
  Hi Rob,
  
  You've done a great job in developing this feature. Before voting though 
  I'd like to understand why the default is not to subset Type 1 fonts. 
  Most users will want the smallest output file size possible. Not 
  enabling it by default is also inconsistent with True Type fonts, whose 
  default is to subset. This inconsistency could lead to confusion.
  
  Thanks,
  
  Chris
  
  On 14/05/2014 10:22, Robert Meyer wrote:
   Hi All,
  
   Following on from the last failed vote for adding Type 1 subset 
   support, I have now put forward a modified patch and am ready to try 
   this again. The patch went up on Monday to address the issues and 
   comments made by Vincent and Luis. This vote will last 5 working days 
   and will finish next Wednesday at the same time.
  
   As always if you have any concerns or find anything please let me 
   know. If they are small I will try and address the issue before the 
   vote is finalized in order to avoid repeating this again. Please note 
   that all type 1 fonts will default to full embedding unless you use 
   the embedding-mode=subset as per one of the recommendations from the 
   last vote.
  
   Here is my vote: +1
  
   Best Regards,
  
   Robert Meyer
 

Re: [VOTE] Applying the Type 1 subset patch

[Clay Leeds]

+1 from me. Nice work, Robert!

Clay

On Mar 7, 2014, at 3:23 AM, Robert rme...@hotmail.co.uk wrote:

 Hi All,
 
 About a week ago I posted a patch to add Type 1 subset support to FOP. All 
 referenced Type 1 fonts (unless set to embedding-mode=full) will now be 
 subset by default much like the behaviour exhibited by TrueType and OpenType. 
 As this is a big feature and quite involved I think it is necessary to vote 
 on whether to add this feature in it's current state to FOP. I'm not sure if 
 anyone has taken a look at what has gone into this or tried it out yet, but 
 it might be worth doing so before making your decision.
 
 I am going to be away for the next week or so but will tally up the votes and 
 post the result once I am back.
 
 Here is a link to the patch and issue:
 https://issues.apache.org/jira/browse/FOP-2354
 
 Regards,
 
 Robert Meyer

Re: Informal FOP Users/Developers/Sponsors Meeting

[Clay Leeds]

Likewise for Los Angeles  Southern California. 

In any event, since we can't all be there it might make sense to do a join me 
or other video conference meeting while you're there in Mass (en masse? ;-). 

It was fun to meet Glenn Mazza once upon a time in San Diego at ApacheCon. 
Cheers!

Clay

--

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

 On Oct 21, 2013, at 2:32 AM, Chris Bowditch bowditch_ch...@hotmail.com 
 wrote:
 
 Hi Glenn,
 
 A conference with the below agenda (plus other items) would be great. 
 Unfortunately we don't have the budget to fly the team out to the U.S. for a 
 short 1 day meeting. Therefore, we must decline with regret. However, if you 
 are ever in the UK for whatever reason it would be good to hold such a 
 conference. Others on this list would also be welcome of course.
 
 Thanks,
 
 Chris
 
 On 18/10/2013 03:43, Glenn Adams wrote:
 Dear FOP Users and Developers,
 
 I will be visiting Basis Technology [1] in Cambridge, Massachusetts during 
 the week of Oct 28 through Nov 1, who has sponsored my work on FOP, 
 especially the Complex Script support. Basis has agreed to host an informal 
 meeting of parties interested in FOP, including users, developers, or 
 sponsors or potential sponsors.
 
 I would like to determine if there is an interest in having people attend a 
 half to full day meeting during that week, which would be organized along an 
 /unconference/ style. Some of the topics that I would like to talk about 
 include:
 
  * future work on complex script support, e.g., fixing bidi issues,
adding additional script support;
  * PDF extensions, such as support for inter- and intra-page
transitions and layers (optional content groups)
  * how to increase interest and use of FOP
  * how to increase levels of sponsorship on the core work of
maintaining and enhancing FOP
 
 Please let me know if you are interested in attending, which day of that 
 week would be best for you, and any additional topics you would like to 
 explore.
 
 I realize this is rather short notice, but let's see if there is sufficient 
 interest.
 
 Regards,
 Glenn
 
 [1] http://www.basistech.com/
 

Re: [VOTE] Merge Temp_FopFontsForSVG into trunk

[Clay Leeds]

Well, I don't want to be a stock in the mud so here's my unconditional +1!
;-)

Cheers!

Clay

--

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

On Aug 27, 2013, at 7:08 AM, Robert Meyer rme...@hotmail.co.uk wrote:

 +1 
 
 I think this sounds ok based on what Luis is saying. 
 
  Date: Tue, 27 Aug 2013 13:25:03 +0100
  From: bowditch_ch...@hotmail.com
  To: fop-dev@xmlgraphics.apache.org
  Subject: Re: [VOTE] Merge Temp_FopFontsForSVG into trunk
  
  Hi Vincent,
  
  On 21/08/2013 11:08, Vincent Hennebert wrote:
   This work allows to directly use FOP-configured fonts for SVG images,
   instead of trying to find, via AWT, equivalent fonts installed on the
   system, and then mapping them to FOP fonts when generating the output.
  
   Please note that this introduces a dependency on the trunk version of
   Batik, with the patch from BATIK-1041 applied. That means that before
   releasing the next version of FOP, a new version of Batik will have to
   be released first.
  
   This vote will run until Monday, 26 August 11:00 UTC.
  
   +1 from me.
  
  +1
  
  I also share the concerns of Pascal and Clay. However, I really see that 
  as a separate discussion that the PMC needs to have about the future of 
  Batik. I've been meaning to start it but I'm really busy ATM. In the 
  meantime there is a practical solution to the dependency issue as 
  mentioned by Luis.
  
   Thanks,
   Vincent
  
  Thanks,
  
  Chris

Re: [VOTE] Merge Temp_FopFontsForSVG into trunk

[Clay Leeds]

This looks like a great and important step. Nice work Vincent!

I have similar concerns as Pancho, so when the BATIK patch is applied I'll vote 
+1.


Regards,

Clay

Clay Leeds  #  949-510-8993  @  the.webmaes...@gmail.com

On Aug 21, 2013, at 4:30 AM, Pascal Sancho psancho@gmail.com wrote:

 Hi,
 
 from [1], I understand that the BATIK patch is not yet applied on BATIK 
 trunk, so introducing a such dependency is not a good idea for the moment.
 
 I will vote +1 when the patch will be applied.
 
 For now, we depend on Batik team
 
 [1] 
 https://issues.apache.org/jira/browse/BATIK-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 
 
 2013/8/21 Vincent Hennebert vhenneb...@gmail.com
 This work allows to directly use FOP-configured fonts for SVG images,
 instead of trying to find, via AWT, equivalent fonts installed on the
 system, and then mapping them to FOP fonts when generating the output.
 
 Please note that this introduces a dependency on the trunk version of
 Batik, with the patch from BATIK-1041 applied. That means that before
 releasing the next version of FOP, a new version of Batik will have to
 be released first.
 
 This vote will run until Monday, 26 August 11:00 UTC.
 
 +1 from me.
 
 Thanks,
 Vincent
 
 
 
 -- 
 pascal

Re: [Xmlgraphics-fop Wiki] Trivial Update of DanielA62 by DanielA62

[Clay Leeds]

Thanks Luis! That's starting to get annoying!
Warm regards,

Clay

Clay Leeds ~ (949) 510-8993 ~ the.webmaes...@gmail.com


On Apr 13, 2013, at 12:21 PM, Luis Bernardo lmpmberna...@gmail.com wrote:

 
 FYI, the wiki ACL request has been made to INFRA but we have to wait a few 
 days.
 
 https://issues.apache.org/jira/browse/INFRA-6146
 
 
 On 4/13/13 8:10 PM, Apache Wiki wrote:
 Dear Wiki user,
 
 You have subscribed to a wiki page or wiki category on Xmlgraphics-fop 
 Wiki for change notification.
 
 The DanielA62 page has been changed by DanielA62:
 http://wiki.apache.org/xmlgraphics-fop/DanielA62
 
 New page:
 There is nothing to write about myself really. I love learning KoreanBR
 BR
 BR
 ??? .BR
 Finally a part of this site.BR
 I really wish I'm useful in one way .BR
 BR
 Here is my site [[http://www.ejk.pl/sowacki/|Zobacz j angielski nauka . 
 Kliknij!]]
 
 -
 To unsubscribe, e-mail: fop-commits-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-commits-h...@xmlgraphics.apache.org
 

[jira] [Commented] (FOP-2208) remove obsolete documentation files

[Clay Leeds (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOP-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13575471#comment-13575471
 ] 

Clay Leeds commented on FOP-2208:
-

Done. Now we need to ensure that FOP builds properly. I also need to do the 
same for Batik and XML Graphics Commons, but I thought I'd wait until other 
folks had a chance to ensure I didn't munge stuff!

 remove obsolete documentation files
 ---

 Key: FOP-2208
 URL: https://issues.apache.org/jira/browse/FOP-2208
 Project: Fop
  Issue Type: Task
  Components: documentation
Affects Versions: trunk
Reporter: Glenn Adams
Assignee: Clay Leeds
Priority: Minor
 Attachments: build.xml


 The old (pre-CMS) documentation files need to be removed from the repository. 
 In addition, any old ant targets related to producing pre-CMS documentation 
 need to be removed as well as the publish.xml file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FOP-2208) remove obsolete documentation files

[Clay Leeds (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOP-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Clay Leeds updated FOP-2208:


Attachment: build.xml

Hi Glenn,

I've gone through the fop/trunk/build.xml and believe I have eradicated the 
documentation portion. Before I nuke the following unnecessary files, could you 
run the ant/build process with the attached build.xml file to ensure I'm not 
munging something?

Thanks!

Files to be nuked:
- fop/trunk/forrest.properties
- fop/trunk/forrest.properties.xml
- fop/trunk/publish.xml
- fop/trunk/src/documentation/

Thanks!

Clay

 remove obsolete documentation files
 ---

 Key: FOP-2208
 URL: https://issues.apache.org/jira/browse/FOP-2208
 Project: Fop
  Issue Type: Task
  Components: documentation
Affects Versions: trunk
Reporter: Glenn Adams
Assignee: Clay Leeds
Priority: Minor
 Attachments: build.xml


 The old (pre-CMS) documentation files need to be removed from the repository. 
 In addition, any old ant targets related to producing pre-CMS documentation 
 need to be removed as well as the publish.xml file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (FOP-2208) remove obsolete documentation files

[Clay Leeds (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOP-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13575371#comment-13575371
 ] 

Clay Leeds edited comment on FOP-2208 at 2/10/13 7:43 AM:
--

Hi Glenn,

I've gone through the fop/trunk/build.xml and believe I have eradicated the 
documentation portion. Before I nuke the following unnecessary files, could you 
run the ant/build process with the attached build.xml file to ensure I'm not 
munging something?

Thanks!

Files to be nuked:
- fop/trunk/forrest.properties
- fop/trunk/forrest.properties.xml
- fop/trunk/publish.xml
- fop/trunk/src/documentation/

Warm regards,

Clay

  was (Author: the_webmaestro):
Hi Glenn,

I've gone through the fop/trunk/build.xml and believe I have eradicated the 
documentation portion. Before I nuke the following unnecessary files, could you 
run the ant/build process with the attached build.xml file to ensure I'm not 
munging something?

Thanks!

Files to be nuked:
- fop/trunk/forrest.properties
- fop/trunk/forrest.properties.xml
- fop/trunk/publish.xml
- fop/trunk/src/documentation/

Thanks!

Clay
  
 remove obsolete documentation files
 ---

 Key: FOP-2208
 URL: https://issues.apache.org/jira/browse/FOP-2208
 Project: Fop
  Issue Type: Task
  Components: documentation
Affects Versions: trunk
Reporter: Glenn Adams
Assignee: Clay Leeds
Priority: Minor
 Attachments: build.xml


 The old (pre-CMS) documentation files need to be removed from the repository. 
 In addition, any old ant targets related to producing pre-CMS documentation 
 need to be removed as well as the publish.xml file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: documentation!???

[Clay Leeds]

Hi Glenn,

The documentation exists solely in the ASF CMS, and so fop/src/documentation is 
obsolete. We purposely did not delete the src/documentation path until we were 
completely sure we weren't going back. I suppose we're there…

I'm happy to nuke ye olde documentation Forrest-based 'xdoc' directories.

After I do that, I'll update the Document Management page with updated 
instructions:

http://xmlgraphics.apache.org/fop/dev/doc.html

Clay







.

On Feb 5, 2013, at 9:44 AM, Glenn Adams gl...@skynav.com wrote:

 where do we edit documentation now? is fop/src/documentation now obsolete? if 
 so, then why is it still in the tree? how will we do releases and still 
 include documentation if it lives in another tree?

Re: documentation!???

[Clay Leeds]

I'll investigate the ANT stuff. 

As for including the docs in the dist, I don't believe there's an option at 
present. I'll investigate that as well. 

Clay








On Feb 5, 2013, at 1:56 PM, Glenn Adams gl...@skynav.com wrote:

 ok; how about the question about future releases? until now, batik, 
 xgc-commons, and fop could be released with source artifacts that contained 
 document sources; but now, it doesn't seem like that is possible, or at least 
 the dist-src build targets do not go out to collect the new documentation 
 sources and copy them into the generated source artifact;
 
 while you are at it, the old publish.xml ant files seem to be obsolete as 
 well; are there any other ant updates needed to rid us of obsolete doc work 
 flow?
 
 On Tue, Feb 5, 2013 at 2:17 PM, Clay Leeds the.webmaes...@gmail.com wrote:
 Hi Glenn,
 
 The documentation exists solely in the ASF CMS, and so fop/src/documentation 
 is obsolete. We purposely did not delete the src/documentation path until we 
 were completely sure we weren't going back. I suppose we're there…
 
 I'm happy to nuke ye olde documentation Forrest-based 'xdoc' directories.
 
 After I do that, I'll update the Document Management page with updated 
 instructions:
 
 http://xmlgraphics.apache.org/fop/dev/doc.html
 
 
 On Feb 5, 2013, at 9:44 AM, Glenn Adams gl...@skynav.com wrote:
 
 where do we edit documentation now? is fop/src/documentation now obsolete? 
 if so, then why is it still in the tree? how will we do releases and still 
 include documentation if it lives in another tree?
 

Re: [Vote] Add dependency to fontbox for OTF CFF

[Clay Leeds]

+1 from me to adding FontBox support and making it optional as Chris recommends.

FOP functionality should not change if OTF CFF Font is not requested. Of 
course, there may be other Font areas where FOP can use FontBox's help, and 
that'll come in the course of time.

Clay Leeds ~ the.webmaes...@gmail.com

On Jan 10, 2013, at 5:36 AM, Chris Bowditch bowditch_ch...@hotmail.com wrote:

 Hi Rob,
 
 On 10/01/2013 12:07, Robert Meyer wrote:
 Hi all,
 
 I posted a message yesterday about getting opinions on either adding a 
 dependency to fontbox to use their implementation or write our own for OTF 
 CFF support. I personally think that using fontbox would be the better 
 option due to:
 
 1) Re-use of code rather than re-writing
 2) Stability and subsequent bugfixes since the time it was released.
 3) Will cut development time for implementing this feature.
 
 There is room for discussion about making the new dependency optional i.e. 
 FOP working without the jar and only being called if a CFF font is used. At 
 this stage though the dependency issue needs to be voted on. I would 
 therefore like to start a vote.
 
 My suggestion would be to make Fontbox an optional dependency and to output a 
 warning message along the lines of: For OTF CFF support please add FontBox 
 to the classpath in the event a user tries to use an OTF CFF Font and 
 doesn't have FontBox in the classpath. For all other font types, FOP should 
 work as normal.
 
 
 As a contributor, my vote will not count toward the result, therefore the 
 decision is left up to the rest of you.
 
 +1 from me.
 
 
 Regards,
 
 Robert Meyer
 
 Thanks,
 
 Chris

Re: [Vote] for the merge of Temp_RoundedCorners

[Clay Leeds]

+1 from me...

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

On Oct 22, 2012, at 8:04 AM, Peter Hancock peter.hanc...@gmail.com wrote:

 Hi Glenn,
 
 I have just committed to Temp_RoundedCorners to address some of the
 concerns raised.
 
 My preference would be to provide both the CSS3 named properties and also
 writing system relative properties, giving the user the preference of which
 to use. But I would suggest using the same pattern as CSS3 for property
 names for these latter:
 
 border-top-left-radius
 border-top-right-radius
 border-bottom-right-radius
 border-bottom-left-radius
 
 border-before-start-radius
 border-before-end-radius
 border-after-start-radius
 border-after-end-radius
 
 I have now implemented border properties of the form
 border-before-start-radius, that take one or two values, in line with
 the CSS3 recommendation.  However, I have not been able as yet to
 implement properties for the absolute properties
 (border-top-left-radius, etc).  I am unable to prove concretely that
 the property resolution system can or cannot support my requirements
 here, but either way I have decided to put this requirement on hold
 for now.  The omission of these properties will not affect backwards
 compatibility going forward and so I do not personally consider it to
 be a show stopper.
 
 it would also be useful to support the border-radius shortcut from CSS3
 (mapping to the above CSS3 longhand flavors)
 This was done previously if we accept that the second value refers to
 the block progression direction and not the absolute top-to-bottom
 direction.
 
 I have updated the example fo and the CMS to reflect these changes.
 
 If you are happy with the change I can proceed with the merge.
 
 Thanks,
 
 Peter

Re: [Vote] for the merge of Temp_RoundedCorners

[Clay Leeds]

I would prefer CSS3 naming conventions as well. 

Clay 

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

On Oct 12, 2012, at 6:48 AM, Peter Hancock peter.hanc...@gmail.com wrote:

 Thanks for taking the time to review this!
 
 On Fri, Oct 12, 2012 at 2:12 PM, Glenn Adams gl...@skynav.com wrote:
 ...
 However, I also notice that the fox property name proposed in [1] contains
 uppercase (fox:border-BLOCK-radius-INLINE). That is a definite no-no, and
 thus warrants a -1 vote until changed to LC. All LC please!
 
 The upper case BLOCK and INLINE were meant to represent variables with
 values before and after, and start and end, respectively.
 
 I haven't had a chance to look at the details, but does this extension
 follow the (property name and value) definitions found in CSS3 Backgrounds
 and Borders [4]? If it doesn't, then my vote is -1; otherwise, I would vote
 +1.
 
 I do concede that there is a departure from CSS3:
 To specify the top left corner in CSS3 you do
 border-top-left-radius=x y
 and with the fox extension (assuming a viewport orientated with the page)
 fox:border-start-radius-before=x
 fox:border-before-radius-start=y
 
 If this is unsatisfactory then I guess it is back to the drawing board.
 
 Peter

Re: svn commit: r1360665 - in /xmlgraphics/fop/trunk: ./ src/java/org/apache/fop/layoutmgr/ test/java/org/apache/fop/intermediate/ test/java/org/apache/fop/layoutengine/

[Clay Leeds]

OT, but I've made some progress on the CMS. I now have dynamic content working 
(separate header and sidenav for FOP, Batik  XGC). 

More relevant comments below...

On Jul 18, 2012, at 5:17 AM, Vincent Hennebert vhenneb...@gmail.com wrote:

 Hi Alexios,
 
 thanks for you input.
 
 On 18/07/12 01:05, Alexios Giotis wrote:
 Hi Vincent,
 
 On Jul 17, 2012, at 12:10 PM, Vincent Hennebert wrote:
 
 It improves documentation. For example, I frequently execute svn annotate, 
 read the usually brief commit message and then refer to the bug for more 
 info (and context in my case). I don't like the fact that I have to rely to 
 another system, but it helps, especially for old change sets.
 
 Well, the problem is probably not the lack of a BTS here, it’s probably
 the commit message that shouldn’t be that short. And a longer
 description should be in status.xml anyway. Also, I find the list of
 comments that usually appears in Bugzilla entries confusing more than
 anything else. You have to wander through the comments to understand
 what is going on.

Perhaps, if something significant changes, the OP or someone for a bug can 
update the description (e. g., w 'UPDATE:') where they pick out the meat of a 
discussion and stik it in the Description field. 

 That said, if a bug affects the rendering part of FOP which is not
 really unit-testable at the moment, the commit is unlikely to contain
 any test, so it helps to be able to retrieve an example output on
 Bugzilla. And I suppose that for the sake of consistency, the same
 should be done for layout bugs.

I would expect an example attachment of PDFs or Afp, Ps, etc. for layout bugs. 

 Also, I’m just remembering that we will at some point switch to the
 Apache CMS to generate the website and that the status.xml logic may not
 be ported there. That’s probably the biggest factor that would push me
 to switch to Bugzilla actually.

My hope is that the BTS system can output a file for us. I understand that HTML 
files can be inserted, unchanged by the CMS. I plan on something like this for 
Compliance.html. 

 snip/

Clay 

Re: [VOTE] Merge Temp_URI_Unification

[Clay Leeds]

Thanks! Happy Fourth (it's still the 4th even outside the U.S. ;-)!

Thanks for your efforts all!

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

On Jul 4, 2012, at 11:35 AM, mehdi houshmand med1...@gmail.com wrote:

 I wouldn't worry Clay, I'm not sure I really know what this thread is about 
 any more either. Either way, it's been merged but thanks for your support.
 
 The fix of this regression is easy, I'll fix it in the morning.
 
 On 4 July 2012 18:32, The Web Maestro the.webmaes...@gmail.com wrote:
 I'm a bit confused... Am I correct that this [VOTE] relates to merging
 the Temp_URI_Unification to fop/trunk and not to FOP-1.1rc*? If so,
 then +1 and if not then +0 since I don't quite understand... (not
 blocker, but not enough info for me to +1... ;-)
 
 Kind regards,
 
 Clay Leeds
 --
 the.webmaes...@gmail.com - http://ourlil.com/
 My religion is simple. My religion is kindness.
 - HH The 14th Dalai Lama of Tibet
 
 
 On Wed, Jul 4, 2012 at 9:26 AM, Chris Bowditch
 bowditch_ch...@hotmail.com wrote:
  On 04/07/2012 17:15, Glenn Adams wrote:
 
 
  On Wed, Jul 4, 2012 at 9:25 AM, mehdi houshmand med1...@gmail.com
  mailto:med1...@gmail.com wrote:
 
  On 4 July 2012 12:32, Vincent Hennebert vhenneb...@gmail.com
  mailto:vhenneb...@gmail.com wrote:
 
 
  There does seem to be a regression. Before, the
  FopFactoryConfigurator
  object was getting the strict-validation element from the
  config file
  and calling FopFactory.setStrictValidation if it was set to
  true. This
  is no longer the case.
 
  I’ve just tried to render a table with table-footer after
  table-body,
  and now a validation error is thrown even if I have
  strict-validation
  set to false in my config file. No validation error was thrown
  before.
 
 
  I've fixed the underlying issue but this is an interesting one; it
  isn't obvious that settings from the fop conf override the
  settings from the command line options. (Pete probably wrote this
  part hahaha ;) )
 
 
  They shouldn't. Command line options should override the conf file.
 
 
  Agreed, but IIUC, the team just copied the existing functionality due to
  time constraints. We should probably log a bug to track that as an issue.
 
  Thanks,
 
  Chris
 
 
 

Re: [VOTE] Merge Temp_TrueTypeInPostScript branch into trunk

[Clay Leeds]

I was going to say that Pascal had a good point, and that it was really up to 
Glenn. 

+1 from me

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

On Jun 15, 2012, at 6:00 AM, Pascal Sancho psancho@gmail.com wrote:

 Ok,
 then...
 +1 for me
 
 2012/6/15 Glenn Adams gl...@skynav.com:
 If Vincent would like this in the 1.1 release, then I'm in favor of a merge
 to trunk. So I'd say +1.
 
 
 On Fri, Jun 15, 2012 at 5:29 AM, Pascal Sancho psancho@gmail.com
 wrote:
 
 Hi,
 
 Since Glenn is in the process to release the FOP v1.1, I'm not sure
 it's time to merge such branch to trunk.
 I guess this new feature will not be part of the 1.1 release.
 
 If merging have to be done quickly, then we should create a 1.1
 maintenance branch to ensure that merging will not affect the
 releasing process.
 
 Or if this new feature have to be part of the 1.1 release, then
 perhaps we have to delay the release process *after* this merge.
 
 any thought?
 
 2012/6/15 Vincent Hennebert vhenneb...@gmail.com:
 As you may have noticed, I’ve recently spent some time updating the
 Temp_TrueTypeInPostScript branch to the latest trunk and doing some
 clean-up (thanks to Robert for updating the testcases to JUnit 4).
 
 We have been using the code from this branch for quite a while now and
 it has proven to work reasonably well. I won’t hide the fact that some
 parts of the code are truly ugly (in PSFontUtils mainly), but it’s not
 possible to clean that up without heavily refactoring the font
 sub-system, which I unfortunately can’t spend time on right now. At
 least the ugliness is fairly self-contained. Meanwhile some users may
 find the additional functionality useful.
 
 So I’d like to propose a vote for merging that branch back to Trunk. The
 vote will run until Thursday 21st, 8:00GMT.
 
 Here’s my +1.
 
 Thanks,
 Vincent
 
 -- 
 pascal

Re: Contributor Names in Commit Messages [was: Re: svn commit: r1339442 - in /xmlgraphics/fop/trunk: ./ conf/ src/documentation/content/xdocs/trunk/ src/java/org/apache/fop/afp/ src/java/org/apache/fo

[Clay Leeds]

Thanks Glenn ( Vincent for your diligence! ;-)

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

On May 18, 2012, at 6:12 PM, Glenn Adams gl...@skynav.com wrote:

 fixed, which, btw, can be done with:
 
 svn propedit -r revision --revprop svn:log new log message
 
 On Thu, May 17, 2012 at 3:02 AM, Vincent Hennebert vhenneb...@gmail.com 
 wrote:
 Glenn,
 
 May I remind you to put contributor names in commit messages when you
 apply their patches [1].
 
 [1] http://markmail.org/message/3ogyrnbief47rnks

Re: on changing fop documentation sources to markdown

[Clay Leeds]

On Apr 20, 2012, at 1:36 AM, Pascal Sancho pascal.san...@takoma.fr wrote:
 Hi,
 
 great job, Clay!
 
 I've looked at the compliance page closer, and it seems that rendering 
 doesn't support markdown extras (like table or headerid), when it is said 
 here [1] that such features are enabled for the CMS.
 
 As a workaround, we can insert html markup inside the markdown, I tried it 
 successfully with the legend table (in the preview pane).
 
 In staging view, there is a CSS issue:
 xmlgraphics.css@17  body {color: white;} is taken into acccount,
 regardless this rule:
 xmlgraphics.css@17  #content {color: #33;}

Wow! Nice work! It's nice to have help on this!

But there has to be a better way. Can we, as a start, change the CSS file 
xmlgraphics.css so it doesn't have body {color: white;}?

 Note that I have to be very patient when editing the (very long) compliance 
 page directly, since it is rendered directly in the preview pane. Don't try 
 it if your processor is a little out of age (;-|

 [1] http://www.apache.org/dev/cmsref.html#markdown

Thanks again for the assistance!

Clay

Re: on changing fop documentation sources to markdown

[Clay Leeds]

On Apr 18, 2012, at 5:12 AM, Chris Bowditch bowditch_ch...@hotmail.com wrote:
 On 18/04/2012 07:24, The Web Maestro wrote:
 
 Hi Clay,
 
 I added the logo (in GIF, JPG, PNG  SVG formats... ;-)
 
 Thanks, but I don't yet see it on the staging website. Is there a delay 
 before that appears?

Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? 
Try loading only the logo. 

 Sponsorship  Thanks were already there. License is on the Legal page, which 
 is there, but I've added it to the sidebar as well, along with the Security 
 page. ;-)
 
 Thanks. I can now see the 4 required links.
 
 I also got the Compliance table working. Unfortunately, the CMS is stripping 
 the 'class=ForrestTable', so the coloring is White-On-White (but if you 
 select the text, you'll see the content and layout is there).
 
 As for the navigation menu, I'd like it to collapse most of the links, 
 except the section you're in. Anyone have a favorite jQuery menu they like 
 for this? If not, I'll see about finding one...
 
 All the TM logos are missing from the content and headers though. It took 
 me quite some time to add them to all the pages. Will you be able to re-sync 
 the content with the latest xdocs as it would take quite some time to 
 re-apply them and I want to tell the board that FOP, Commons and XML Graphics 
 sites are now brand compliant in the upcoming report.

The current LIVE site has it, so we should be good informing the board it's 
there, no?

Weird. When I added the content, I did an `svn up` to ensure it was recent 
content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a 
caching thing!

 Thanks,
 
 Chris

Re: on changing fop documentation sources to markdown

[Clay Leeds]

I replaced the logo for all sites a month or so ago. 

I'm not at a place I can publish, but if someone can publish the PRODUCTION 
sites, the logo will show up (be sure to clear cache!). 

Clay

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

On Apr 18, 2012, at 7:09 AM, Chris Bowditch bowditch_ch...@hotmail.com wrote:

 On 18/04/2012 13:52, Clay Leeds wrote:
 On Apr 18, 2012, at 5:12 AM, Chris Bowditchbowditch_ch...@hotmail.com  
 wrote:
 On 18/04/2012 07:24, The Web Maestro wrote:
 
 Hi Clay,
 
 I added the logo (in GIF, JPG, PNG  SVG formats... ;-)
 Thanks, but I don't yet see it on the staging website. Is there a delay 
 before that appears?
 
 Hi Clay,
 
 Strange. The new logo showed up when I refreshed it. Perhaps it's your 
 cache? Try loading only the logo.
 
 Yes you are right. It was my browser cache. I can now see the updated logo.
 
 
 Sponsorship  Thanks were already there. License is on the Legal page, 
 which is there, but I've added it to the sidebar as well, along with the 
 Security page. ;-)
 Thanks. I can now see the 4 required links.
 
 I also got the Compliance table working. Unfortunately, the CMS is 
 stripping the 'class=ForrestTable', so the coloring is White-On-White 
 (but if you select the text, you'll see the content and layout is there).
 
 As for the navigation menu, I'd like it to collapse most of the links, 
 except the section you're in. Anyone have a favorite jQuery menu they like 
 for this? If not, I'll see about finding one...
 All the TM logos are missing from the content and headers though. It took 
 me quite some time to add them to all the pages. Will you be able to 
 re-sync the content with the latest xdocs as it would take quite some time 
 to re-apply them and I want to tell the board that FOP, Commons and XML 
 Graphics sites are now brand compliant in the upcoming report.
 The current LIVE site has it, so we should be good informing the board it's 
 there, no?
 
 Weird. When I added the content, I did an `svn up` to ensure it was recent 
 content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it 
 were a caching thing!
 
 I can see the TM logos in most of the content after clearing the cache. Just 
 the XML Graphics top page doesn't appear to have them now.
 
 Thanks,
 
 Chris
 
 
 Thanks,
 
 Chris
 
 

Re: on changing fop documentation sources to markdown

[Clay Leeds]

NOTE: Moving discussion to general@. Please make all further responses to 
general@. 

BACKGROUND:
We are discussing moving XML Graphics web site to ASF-CMS. You can see progress 
here:

http://xmlgraphics.staging.apache.org/

ToDo:
- Lots.
- Style  templating work
- Non-HTML content (figure out how to handle java-docs, download.cgi, demo 
stuff, etc.--might not be too difficult, just a matter of committing to CMS 
content/ dirs?)

Done:
- most HTML content

Clay

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

On Apr 17, 2012, at 1:19 AM, Chris Bowditch bowditch_ch...@hotmail.com wrote:

 On 15/04/2012 19:52, The Web Maestro wrote:
 I just added most of the nav for FOP Development (0.95, 1.0, trunk/ and 
 'dev'):
 Hi Clay,
 
 http://xmlgraphics.staging.apache.org/
 
 As mentioned, there are likely missing things (like java-docs, download.cgi, 
 Batik's DEMO, etc.)... It'd be great if folks could take a look... I haven't 
 figured out how to add other content, but It Might Just Work(tm) if weupload 
 it there via SVN...
 
 Many thanks for working on this.
 
 
 Come to think of it, we should probably move this to 
 gene...@xmlgraphics.apache.org mailto:gene...@xmlgraphics.apache.org. Or 
 is there a better mailing list? I'll refrain from sending to other lists, 
 until we figure out where it should go.
 
 Any ideas where this discussion should move, since it entails changes to all 
 XML Graphics Project web docs?
 
 Yes this discussion should move to general@ as it will affect all sub 
 projects of XML Graphics.
 
 Thanks,
 
 Chris
 
 
 Kind regards,
 
 Clay Leeds
 --
 the.webmaes...@gmail.com mailto:the.webmaes...@gmail.com - 
 http://ourlil.com/
 My religion is simple. My religion is kindness.
 - HH The 14th Dalai Lama of Tibet
 
 
 On Sat, Apr 14, 2012 at 11:53 PM, The Web Maestro the.webmaes...@gmail.com 
 mailto:the.webmaes...@gmail.com wrote:
 
I've updated the docs a bit, and gotten much (but not all!) of the
FOP, Batik  Commons content into the CMS...
 
We're still missing an adequate navigation system, so I did a
preliminary job of getting a few links in the sidenav, but it's
incomplete and ugly as sin. We'll need to build a mechanism to
hide (collapse?) non-relevant links, but that shouldn't be too hard.
 
We also need to figure out java-docs, download.cgi, and perhaps
some other issues...
 
Without further ado:
 
http://xmlgraphics.staging.apache.org/
 
 
Kind regards,
 
Clay Leeds
--
the.webmaes...@gmail.com mailto:the.webmaes...@gmail.com -
http://ourlil.com/
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
 
 
On Thu, Apr 12, 2012 at 10:03 PM, Clay Leeds
the.webmaes...@gmail.com mailto:the.webmaes...@gmail.com wrote:
 
On Apr 12, 2012, at 6:41 AM, Glenn Adams gl...@skynav.com
mailto:gl...@skynav.com wrote:
 Agreed that removing forrest dependency is desirable.
However, presumably the current xdocs would need to be
converted to MD, in which case someone will need to construct
an XSLT to do so. That begs the question of whether it would
be necessary (at this time) to convert the source format to
MD, or if an additional step in the CMS based process could
merely perform that step automatically. If so, then it should
not be necessary to change the authoring format at this time.
It could be done as a separate step later.
 
I am using Forrest 0.8 w markdown plugin. Conversion could be
scripted, but that would negate the benefit of the CMS.
 
 What I don't know yet is what we will lose from the
conversion to MD in terms of ability to markup our source
docs. Clearly, MD is not as semantically or syntactically rich
as an XML based source. But do we lose anything of
consequence? I don't know yet.

 One thing we may lose if we don't convert to MD is the
ability to use CMS in-page editing. So that is a
consideration. Perhaps that option is sufficient to justify
other potential negatives in converting.

 G.
 
One of my goals, was to see some discussion in the DEVers,
before I complete the task of converting the docs. The
MarkDown format is not nearly as semantic as xdoc, but it
serves a different purpose.
 
It'll take some time, and I'm still prepared to take it on.
But I was hoping for some discussion ;-)
 
 
 
 

Re: on changing fop documentation sources to markdown

[Clay Leeds]

Thx for the comments Glenn,

On Apr 15, 2012, at 12:50 PM, Glenn Adams gl...@skynav.com wrote:
initial comments:
 the navigation panel on the left needs to start in a collapsed mode, and 
 remember its settings as you move to  sub-projects and their descendants; 
 possibly better would be to limit what is in the navigation panel to the 
 content of each currently selected sub-project or home, while retaining 
 expansion within that set of content;

I'll likely make it collapse everything but the section you are in. I don't 
think it'll remember state, so much as be aware of where you are. I'm thinking 
we'll be using jQuery for that but perhaps that'll include state?

But I'm open to code additions... ;-)
 table formatting is broken, cf. compliance.html and complexscripts.html

Excellent! Thank you so much for checking up.

We might just paste that code in as straight HTML. 
 header margins seem strange; h[134] are aligned (on left) but h2 is indented; 
 cf. complexscripts.html
I need to format the page templates and such (the Nav collapse stuff will be a 
part of that). 

 also, since you are now in the process of making these changes, what should 
 we do with current site doc updates? i.e., can i continue to commit changes 
 to fop/src/documentation/content/xdocs and you will pick up these changes at 
 some point? or should we hold off on any changes until you have finished?

I'm not sure. I think we should probably do both. The CMS process is simple 
enough but I hate the prospect of double work for anyone. 

We should tag the web content for XML Graphics, FOP, Batik,  Commons, so we 
could have a reference point.

Clay

Re: on changing fop documentation sources to markdown

[Clay Leeds]

On Apr 12, 2012, at 6:41 AM, Glenn Adams gl...@skynav.com wrote:
 Agreed that removing forrest dependency is desirable. However, presumably the 
 current xdocs would need to be converted to MD, in which case someone will 
 need to construct an XSLT to do so. That begs the question of whether it 
 would be necessary (at this time) to convert the source format to MD, or if 
 an additional step in the CMS based process could merely perform that step 
 automatically. If so, then it should not be necessary to change the authoring 
 format at this time. It could be done as a separate step later.

I am using Forrest 0.8 w markdown plugin. Conversion could be scripted, but 
that would negate the benefit of the CMS. 

 What I don't know yet is what we will lose from the conversion to MD in terms 
 of ability to markup our source docs. Clearly, MD is not as semantically or 
 syntactically rich as an XML based source. But do we lose anything of 
 consequence? I don't know yet.
 
 One thing we may lose if we don't convert to MD is the ability to use CMS 
 in-page editing. So that is a consideration. Perhaps that option is 
 sufficient to justify other potential negatives in converting.
 
 G.

One of my goals, was to see some discussion in the DEVers, before I complete 
the task of converting the docs. The MarkDown format is not nearly as semantic 
as xdoc, but it serves a different purpose. 

It'll take some time, and I'm still prepared to take it on. But I was hoping 
for some discussion ;-)

Re: on changing fop documentation sources to markdown

[Clay Leeds]

On Apr 8, 2012, at 7:21 PM, Glenn Adams gl...@skynav.com wrote:
 Yes, we'd lose the XML-based nature of the documentation. That's a fairly 
 large loss, but I don't know if that's a showstopper, considering the 
 benefits of having CMS-based documentation.
 
 What prevents you from using the existing xdoc format as source, then using 
 an XSLT to map to MD whence it can be imported into / processed by the CMS. 
 Or can you incorporate this translation process into the CMS?

Nothing prevents, but the goal is in this exercise is to minimize launch 
preparation time. ;-)

If we continue to use xdoc, the CMS is skipped. It's certainly possible, but...

Clay

Re: on changing fop documentation sources to markdown

[Clay Leeds]

Makes sense to me. However, I don't think it's necessary to have all 
documentation as such.  Perhaps just the Day to day stuff can be translated 
(things that are more likely to change). 

That's my current plan, anyway (although I don't yet know how to make that 
happen). Ye olde documentation can remain on xdoc format, or better yet get 
converted to Docbook format. 

Web Maestro Clay

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

On Mar 29, 2012, at 9:22 PM, Glenn Adams gl...@skynav.com wrote:

 If I understand correctly, it is proposed that the FOP doc sources be changed 
 from the current forrest based format (and XML format) to markdown format. If 
 this is correct, then I would like to voice my objection to making this 
 change.
 
 I am all for improving FOP documentation and management process; however, I 
 am very leery about changing from an XML source format to a non-XML format, 
 especially one that is as semantically sparse as the markdown format.
 
 If a change is to be made, then I would suggest that some XML format remain 
 as the source format, and that markdown be one of a number of possible output 
 (publishing) formats.
 
 Overall, I would prefer spending scarce resources on improving the depth, 
 breadth, accuracy, and currency of FOP documentation content, rather than on 
 switching to a different source format, management, or publishing format.
 
 I also feel it is very important to continue using FOP documentation to 
 create some output format. I am not prepared to give up our dog food, as that 
 provides one more set of tests on FOP, that would otherwise be missing. Given 
 the sparseness of FOP test coverage, the more content we formally run FOP on, 
 the better.
 
 G.
 

Re: Working on getting the web site converted to Apache's ASF-CMS...

[Clay Leeds]

 Does that mean that we would be eventually phasing out Forrest
 altogether and store the documentation directly in the CMS?
 
 Yes. We hope to phase out Forrest... All content changes will occur in the
 CMS.
 
 
 At present, my understanding is that the forrest content is also converted
 to PDF by translating to XML, then running through FOP. Is this correct?
 
 What will happen if we switch to MD markup, which is considerably less
 semantically rich than forrest? Will it still be possible to create the
 same PDF docs?

 If not, then that seems like a fairly radical change to the current
 approach, at least for FOP documentation.

 A change that I personally welcome. Quite frankly the PDF versions of
 our web pages look terrible and don’t do honour to FOP. And I’ve never
 been comfortable enough with Forrest to change the way they look. And
 I must say, I don’t have the energy to learn enough of Forrest to be
 able to do it.
 
 I’m happy with the all-CMS and Markdown approach, especially if it can
 give our website a 21st century look.
 
 Vincent

Agreed. This will make it easier to update the site  but we won't eat our dog 
food, which is a bummer.

Perhaps someone can add PDF output to the CMS? GSOC?

It's definitely a topic for discussion. 

 Clay

Re: update to site/deploy/fop

[Clay Leeds]

Nice work troubleshooting the file date problem. I have had many problems w 
site deployment since long ago when I first brought the site to more or less 
it's current state of Forrest-y crunchiness. 

I'm currently spending some time researching the method for converting to the 
newly blessed method for site deployment using the new Apache CMS system, so 
hopefully it won't be an issue for too much longer. 

Clay

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

On Feb 27, 2012, at 12:39 AM, Glenn Adams gl...@skynav.com wrote:

 I've been attempting for a few hours now to successfully update the FOP site 
 directory. After a number of attempts I believe I've finally performed an 
 update (subject to an upcoming rsync). I noticed that the first time I was 
 able to perform a deploy.svn successfully, it only updated two files, two 
 newly added files, and did not update any of the other existing files.
 
 I finally determined that the following lines in 
 forrest/tools/forrestbot/core/deploy.xml
 
 copy todir=${deploy.svn.svn-dir}
   fileset dir=${build.site-dir}/
 /copy
 
 were failing to copy the changed (modified) files since the last modified 
 date on the target directory (work/svn-deploy/forrest-docs) were later than 
 the just previously built site directory (build/forrest-docs).
 
 This was because the newly checkout out files in the target directory had the 
 time of checkout as opposed to the last time of commit on the file, and, 
 consequently, the local site directory files, which are rendered (built) by 
 forrest prior to the checkout, had older last modified times.
 
 By adding overwrite=true as follows (along with verbose for a little 
 debugging help), I finally got all the modified site files copied, and 
 subsequently committed by deploy.svn.
 
 copy todir=${deploy.svn.svn-dir} verbose=true overwrite=true
   fileset dir=${build.site-dir}/
 /copy
 
 Has anyone else encountered this problem? What is the best way to effect a 
 shared fix?
 
 G.
 
 

Re: complex scripts patch committed

[Clay Leeds]

Nice work Glenn!

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

On Feb 26, 2012, at 12:09 AM, Glenn Adams gl...@skynav.com wrote:

 it looks like this commit didn't break the nightly trunk build, as it just 
 completed without error [1]
 
 [1] http://ci.apache.org/builders/fop-trunk/
 
 whew...
 
 On Sat, Feb 25, 2012 at 8:40 PM, Glenn Adams gl...@skynav.com wrote:
 The complex scripts (CS) patch is now committed to trunk at revision 1293736 
 [1].
 
 [1] http://svn.apache.org/viewvc?view=revisionrevision=1293736
 

Re: [VOTE] Glenn Adams for committer

[Clay Leeds]

+1 from me!

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

On Feb 20, 2012, at 2:16 AM, Chris Bowditch bowditch_ch...@hotmail.com wrote:

 Hi All,
 
 Glenn Adams is the author of the Complex Scripts branch for FOP. He has been 
 developing it for over 1 year now, providing regular updates to the patch as 
 well as support for it via the fop-users Mailing List. I therefore propose 
 Glenn is made a committer as reward for his dedication to the FOP project. 
 Glenn is an expert in eastern languages (amonst other things) and will bring 
 a wealth of valuable knowledge to the FOP development team.
 
 +1 from me.
 
 Votes on general@ only please.
 
 Thanks,
 
 Chris
 
 -
 To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: general-h...@xmlgraphics.apache.org
 

Re: [VOTE] merge Temp_ImproveAccessibility to trunk

[Clay Leeds]

+1 from me.

Peter, you might want to have a VOTE recorded too! ;-)

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

On Feb 1, 2012, at 7:40 AM, Peter Hancock peter.hanc...@gmail.com wrote:

 Hi All,
 
 Vincent and I have recently been working to improve the generation of
 tagged PDF and we now propose merging the branch
 Temp_ImproveAccessibility into trunk.
 
 The objectives and an implementation plan was summarised by Vincent in
 [1] and development has remained fairly faithful to that proposal.
 
 A core objective of this work was to remove the XSLT pre-process stage
 and instead build the structure tree from FONode creation events and
 this has been realised.
 
 The new implementation has allowed us to fix a few bugs related to the
 structure tree representation of tables.
 
 Thanks,
 
 Peter
 
 [1] 
 http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/201109.mbox/%3C4E6624CE.1030703%40gmail.com%3E

Re: Account mehdi created

[Clay Leeds]

Hi Mehdi,

I was going to update your bio on the FOP team page, but I figure you have 
commit access now so can do it yourself. ;-)

Please holler if you need assistance!

Clay

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

On Nov 18, 2011, at 3:45 AM, mehdi houshmand med1...@gmail.com wrote:

 Hi Simon,
 
 I can confirm receiving the username and password, thanks for doing
 all this so quickly, it's very much appreciated.
 
 Mehdi
 
 On 18 November 2011 11:22, Simon Pepping spepp...@leverkruid.eu wrote:
 Mehdi,
 
 The account mehdi has been created. I suppose you received a
 communication with the password. You are now a member of the
 xmlgraphics and xmlgraphics-fop groups, which grants you write access
 to the fop, commons and site repositories. Note that you must use the
 https protocol for your access to the repositories to enable writing.
 
 Success as a FOP developer,
 Simon Pepping
 

Re: Merge Request - Temp_ComplexScripts into Trunk

[Clay Leeds]

 However, if someone actually renamed my variables after I have declared my 
 position, then I would interpret that as doing bad things to the code. In 
 fact, i would revert such a change.
 
 If folks aren't willing to respect my style of coding along with my promise 
 to document short names, then I will withdraw my request for a merge and 
 abrogate my ICLA. I would not wish my work to be used in a community that 
 does not have sufficient respect for personal coding styles of contributors 
 that do not in any way vary from documented conventions.

This is a long thread and my hope is that we will be able to resolve it 
amicably, and that our community can grow from this experience. 

The ComplexScripts functionality being merged is a valued and important 
addition to the Apache FOP Project. 

More important than the code to me personally, is the continued community and 
its growth. 

FOP is a community built around a common desire to create a robust and open 
source tool for generating XSL Formatting Output in various common formats for 
print, screen, archival and transfer purposes.  

There is an expressed concern about code readability and reusability. What 
concerns me most is that this may cause division.

I'm concerned about the level of compromise and intent. It may take more of a 
stretch on each or our parts to move forward.

Clay

My religion is simple. My religion is kindness.
- HH The 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 pascal.san...@takoma.fr wrote:

 Hi,
 
 There was a discussion about enabling it by default, with some
 performances tests.
 
 see http://marc.info/?l=fop-devm=131108266423848w=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
 --
 the.webmaes...@gmail.com - http://ourlil.com/
 My religion is simple. My religion is kindness.
 - HH The 14th Dalai Lama of Tibet
 
 
 -- 
 Pascal

Re: Merge Request - Temp_ComplexScripts into Trunk

[Clay Leeds]

Quick question about this.

Please forgive my naïveté but, does this code affect processing
if you're not using ComplexScript support?

Thanks,

Clay

Re: [VOTE] to include the Mockito framework

[Clay Leeds]

I'll belly up to the bar and have a Mockito as well... ;-)

+1

Sent from my iPhone

On Oct 13, 2011, at 8:38 AM, Peter Hancock peter.hanc...@gmail.com wrote:

 I would like to launch a vote to include the Mockito framework and her
 dependencies in to FOP for unit testing.
 
 Some reasons for introducing a framework for mocking and stubbing, and
 Mockito in particular, have briefly been expressed [1] and patches
 have been provided [2] ... [4] that depend upon Mockito.
 
 Unit testing in FOP often proves difficult because it can be very hard
 to factor out dependencies: to run a piece of FOP code often requires
 substantial configuration.
 Mockito can go a long way in helping us here, and may even encourage
 us to write more unit tests!
 
 [1] http://markmail.org/message/zobrtzanojpkfysa
 [2] https://issues.apache.org/bugzilla/show_bug.cgi?id=50483
 [3] https://issues.apache.org/bugzilla/show_bug.cgi?id=50391
 [4] https://issues.apache.org/bugzilla/show_bug.cgi?id=46962
 
 +1 here.
 
 Peter

Re: svn commit: r1139721 - /xmlgraphics/fop/tags/fop-1_0/src/documentation/skinconf.xml

[Clay Leeds]

FWIW, I should've mentioned that there was some minor code cleanup in
here as well, to bring it closer to Forrest's skinconf.xml file.

Also, my primary purpose in making changes, was to help the Apache XML
Graphics PMC live up to its contractual duties as far as Trademark
Attributions go:

http://www.apache.org/foundation/marks/pmcs

I hope to get to the Batik  Commons sites soon. Could somebody
re-publish the FOP site for me? I haven't set up the deployment
process on my latest Mac...

Regards,

The Web Maestro
--
the.webmaes...@gmail.com - http://ourlil.com/
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: Initial soft hyphen support

[Clay Leeds]

On Jan 16, 2007, at 12:25 PM, Vincent Hennebert wrote:

Hadn't we agreed upon raising the minimum Java version to 1.4? Or at
least make a poll on fop-user to see if that would create any problem.
If that'd depend only on me, we would already be using all the Java  
1.5

nice features ;-)

Vincent


As I recall, we're targeting JDK 1.4 for 0.93+, and leave the JDK 1.3  
for 0.20.5 (since it's not changing anyway). I think the thought was  
that anyone who needs to stay on JDK 1.3 (AIX 4.x  others locked  
into IBM Java 1.3, etc.) can continue using fop-0.20.5.


Web Maestro Clay

Re: [Xmlgraphics-fop Wiki] Update of GoogleSummerOfCode2006/FloatsImplementationProgress by VincentHennebert

[Clay Leeds]

On Jun 10, 2006, at 11:59 AM, Simon Pepping wrote:

On Fri, Jun 09, 2006 at 10:56:53AM +0200, Jeremias Maerki wrote:
That's fine. Another general possibility is to set up a special  
account

for you with restricted write access to our repository. This has been
done last year for GSoC (with some of those becoming normal  
committers

afterwards). If everyone thinks that would be a good thing we can go
down that road (Obviously, it's a project decision). I'm also fine  
just

reviewing and applying your patches as quickly as possible. Normal
committership would also not be far away I guess if we're happy with
what you contribute over time.


Having access to a repository makes code management much easier. I
would agree with restricted write access.

Simon


I would agree with restricted write access for Vincent.

Clay Leeds
[EMAIL PROTECTED]

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

Re: How about a release?

[Clay Leeds]

On Apr 7, 2006, at 12:38 AM, Chris Bowditch wrote:

Clay Leeds wrote:

On Apr 6, 2006, at 11:50 AM, Peter S. Housel wrote:

WDYT?
From my perspective as a user, I think it's essential to fix the   
problem with preserving whitespace after a newline (for pre- 
style  output) before doing another release.


-Peter-
If it's resolved, then I'd give my +1 to a PMC VOTE. If not, then  
can  it be resolved quickly? If not, then I'd say '+1'.


This problem cannot be resolved quickly. It requires an adjustment  
to the Knuth algorithm used for generating Break Possibilities.  
Simon P has a proposal to change the Knuth algorithm that addresses  
this problem, but it will take some time to implement.


From my perspective (as a User), this problem is not high on the  
list of  priorities. Mainly because my stylesheets don't allow the  
user to preserve whitespace in incoming data. This is considering  
poor formatting. Instead the XML should be restructed to allow  
formatting attributes to be applied to text to yield the desired  
result.


Chris


I understand. As long as it will be resolved by v1.0, then IMO we are  
good to go. +1


Clay Leeds
[EMAIL PROTECTED]

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

Re: Encoding issue in PDFOutputIntent.java

[Clay Leeds]

You're running Windows! ;-)

On Apr 5, 2006, at 10:48 PM, Jeremias Maerki wrote:

Fixed. Don't know how I managed to type this special apostrophe.

On 06.04.2006 00:29:31 Manuel Mall wrote:

I am getting the warning below when compiling the latest trunk

Manuel

[javac] /home/mm/fop-trunk/src/java/org/apache/fop/pdf/ 
PDFOutputIntent.java:121:

warning: unmappable character for encoding UTF8
[javac]  *  document�s source  
colors to

output device colorants.


Jeremias Maerki



Clay Leeds
[EMAIL PROTECTED]

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

Re: Encoding issue in PDFOutputIntent.java

[Clay Leeds]

On Apr 5, 2006, at 11:14 PM, Clay Leeds wrote:

You're running Windows! ;-)


Seriously, I suspect you copied something w 'smart quotes' from MS  
Word...


Clay Leeds
[EMAIL PROTECTED]

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

Re: How about a release?

[Clay Leeds]

On Apr 6, 2006, at 8:55 AM, Chris Bowditch wrote:

Jeremias Maerki wrote:

We originally wanted to do a release much earlier but I was always in
the middle of something and I think I'm simply the only one who can
allocate enough time to do an actual release (prove me wrong,  
please). I
think I can make time next week to do a release of FOP and XML  
Graphics
Commons. FOP Trunk is currently in pretty good condition, the new  
API is
established and documented. I imagine a 0.92beta (beta only  
because of

the changed API and the many deprecations, PDF and PS output are
production-ready IMO), and after waiting for some time for  
feedback on
the API, we could release a 1.0. So if there's nothing that would  
block

a release, I can create a release branch and start a PMC vote for the
release.
WDYT?


Yes I agree completely

+1

Chris


I'd like to see a release as well.

But is this a new issue? Has it been resolved?

On Apr 6, 2006, at 11:50 AM, Peter S. Housel wrote:

WDYT?


From my perspective as a user, I think it's essential to fix the  
problem with preserving whitespace after a newline (for pre-style  
output) before doing another release.


-Peter-


If it's resolved, then I'd give my +1 to a PMC VOTE. If not, then can  
it be resolved quickly? If not, then I'd say '+1'.


Clay Leeds
[EMAIL PROTECTED]

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

Re: [NOTICE] XML Graphics Commons is now a dependency of FOP Trunk

[Clay Leeds]

On Apr 5, 2006, at 5:39 AM, Jeremias Maerki wrote:

On 05.04.2006 01:31:53 Web Maestro Clay wrote:

I was going to fix up the xmlgraphics page, but it doesn't look like
the src files were committed for the web site (src/documentation/
content/xdocs/*.xml). Am I missing something?


Hmm, sorry, but I don't know what you mean. So far, there's no website
for Commons.


I was talking about for xmlgraphics/site (not commons... that'll come  
later!). I couldn't find any svn updates to xmlgraphics, so I thought  
your changes must be local... Then again, it's possible you made  
those changes a while ago...


Clay Leeds
[EMAIL PROTECTED]

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

Re: [EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed

[Clay Leeds]

On Apr 5, 2006, at 5:59 AM, Jeremias Maerki wrote:

On 05.04.2006 14:37:30 Sam Ruby wrote:
The following annotations (debug/informational/warning/error  
messages) were provided:

 -DEBUG- Sole output [fop.jar] identifier set to project name
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: xmlgraphics-commons unknown to  
*this* workspace


I fixed this already. It should go away with the next Gump run.
Hopefully this will make the Gump run work again.


My Inbox thanks you! :-)

Clay Leeds
[EMAIL PROTECTED]

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

Re: [NOTICE] XML Graphics Commons is now a dependency of FOP Trunk

[Clay Leeds]

On Apr 5, 2006, at 7:13 AM, Clay Leeds wrote:

On Apr 5, 2006, at 5:39 AM, Jeremias Maerki wrote:

On 05.04.2006 01:31:53 Web Maestro Clay wrote:

I was going to fix up the xmlgraphics page, but it doesn't look like
the src files were committed for the web site (src/documentation/
content/xdocs/*.xml). Am I missing something?


Hmm, sorry, but I don't know what you mean. So far, there's no  
website

for Commons.


I was talking about for xmlgraphics/site (not commons... that'll  
come later!). I couldn't find any svn updates to xmlgraphics, so I  
thought your changes must be local... Then again, it's possible you  
made those changes a while ago...


It looks like the Commons info is in the SVN... never mind!

Clay Leeds
[EMAIL PROTECTED]

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