19 Apr
2020
19 Apr
'20
5:20 p.m.
Hi Chris,
Template::Plugin::Latex has an encoding routine which we're *not* using to
encode data before being passed to (Xe)LaTeX.
We're contemplating simplifying places in our codebase and one of the
changes would be to use the built-in latex_encode. Do you have any
recollection with respect to the choice for TeX::Encode and whether we
should be fine to move to "latex_encode" all these years later?
Regards,
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
22 Apr
22 Apr
3:23 p.m.
On Sun, Apr 19, 2020 at 07:20:44PM +0200, Erik Huelsmann wrote:
Hi Chris,
Template::Plugin::Latex has an encoding routine which we're *not* using to
encode data before being passed to (Xe)LaTeX.
We're contemplating simplifying places in our codebase and one of the
changes would be to use the built-in latex_encode. Do you have any
recollection with respect to the choice for TeX::Encode and whether we
should be fine to move to "latex_encode" all these years later?
I don't see any problems. Right now I'm waiting for ports lock to pass.
Then I will push in new stuff. Just let me know once a decision is made
and I will make that reflect what needs to go in.
We just traveled permanently from Washington state back to Texas, so I'm
a little out of touch with the ports mailing list (next list I'm going
to check).
Ports lock is done to stabilize everything in order to release 6.7
Simplifying is usually a good idea. :-}
I'll ping what I have already submitted and send in more modules once
things are unlocked.
Thanks,
Chris Bennett
7:53 p.m.
Hi Chris,
On Wed, Apr 22, 2020 at 5:23 PM Chris Bennett <chris(a)bennettconstruction.us>
wrote:
On Sun, Apr 19, 2020 at 07:20:44PM +0200, Erik
Huelsmann wrote:
That's perfect! How did you test for problems? I mean, which characters?
Which patch did you apply to our code base to make sure Tex::Encode wasn't
active and the "latex_encode" filter *was*?
Hi Chris,
Template::Plugin::Latex has an encoding routine which we're *not* using
to
encode data before being passed to (Xe)LaTeX.
We're contemplating simplifying places in our codebase and one of the
changes would be to use the built-in latex_encode. Do you have any
recollection with respect to the choice for TeX::Encode and whether we
should be fine to move to "latex_encode" all these years later?
I don't see any problems. Right now I'm waiting for ports lock to pass.
Then I will push in new stuff. Just let me know once a decision is made
and I will make that reflect what needs to go in.
Yup. We're working on developing tests within the LedgerSMB project to
assure we're making the right decisions; however, if you already did that,
that would be double work?
We just traveled permanently from Washington state
back to Texas, so I'm
a little out of touch with the ports mailing list (next list I'm going
to check).
Ports lock is done to stabilize everything in order to release 6.7
Simplifying is usually a good idea. :-}
Definitely! And that's why we're always looking to reduce the number of
dependencies. But not at the expense of good functionality.
I'll ping what I have already submitted and send in more modules once
things are unlocked.
Travel safely!
Regards,
Erik.
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
23 Apr
23 Apr
6:17 p.m.
On Wed, Apr 22, 2020 at 09:53:04PM +0200, Erik Huelsmann wrote:
We did! Very happy to be back!
Thanks,
Chris Bennett
Hi Chris,
On Wed, Apr 22, 2020 at 5:23 PM Chris Bennett <chris(a)bennettconstruction.us>
wrote:
I don't mind doing any double work at all. OpenBSD is far enough off the
beaten path that I am running any test within the modules that can be
run. Right now, 6.7 will ship with Perl 5.30.2, with some customizations
for OpenBSD. PostgreSQL 12.x.
I am hoping to get LedgerSMB up and running inside of 6.8 -current.
That can be run by anyone who wants to. Many do run -current, so that's
good.
I need to change my git email address and re-add LedgerSMB to that one.
The projects I was following were a bit overwhelming to this email.
Let me know what tests I should run. I will make sure I have any needed
modules ready for those tests.
On Sun, Apr 19, 2020 at 07:20:44PM +0200, Erik
Huelsmann wrote:
That's perfect! How did you test for problems? I mean, which characters?
Which patch did you apply to our code base to make sure Tex::Encode wasn't
active and the "latex_encode" filter *was*?
Hi Chris,
Template::Plugin::Latex has an encoding routine which we're *not* using
to
encode data before being passed to (Xe)LaTeX.
We're contemplating simplifying places in our codebase and one of the
changes would be to use the built-in latex_encode. Do you have any
recollection with respect to the choice for TeX::Encode and whether we
should be fine to move to "latex_encode" all these years later?
I don't see any problems. Right now I'm waiting for ports lock to
pass.
Then I will push in new stuff. Just let me know once a decision is made
and I will make that reflect what needs to go in.
Yup. We're working on developing tests within the LedgerSMB project to
assure we're making the right decisions; however, if you already did that,
that would be double work? We just traveled permanently from Washington
state back to Texas, so I'm
a little out of touch with the ports mailing list (next list I'm going
to check).
Travel safely!
1070
days inactive
1074
days old
3 comments
2 participants
participants (2)
-
Chris Bennett -
Erik Huelsmann