Re: [NTG-context] zint module on LMTX
Hi Michal and Hans, My LuaMetaTeX version (and ConTeXt LMTX...) was from 18.04.2022. That was the reason... As soon as I installed the fresh version, it started working properly, even with my library build. So next time before writing to list, I'll do the update and check first ;) That is a native Windows build using cmake in VS 2019. Hans, you can pass option to cmake and build zint without libpng like Michal's version... Mine has is, but it doesn't work :-) But I will certainly use your and Hans' recommendation of cross-compiling in wsl. Much less headache... Thanks for all the tips! Ivan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] zint module on LMTX
Дана 04.09.2022. у 12:36, ntg-context-requ...@ntg.nl пише:
looks like the library is loaded ... so what is your test
we don't do png, we do outlines (actually native zint graphic structures
that we then convert with mp)
Hans
Hi Hans,
here is the example that I used, basically I took it from the from the
module:
\starttext
\usemodule[zint]
\startTEXpage
\barcode[alternative=PDF417,text={Hans Hagen}]%
\blank
\barcode[alternative=pdf417,text={Ton Otten}]%
\blank
\barcode[alternative=ISBN,text=9789490688011]%
\blank
\barcode[alternative=isbn,text=9789490688011,width=3cm]%
\blank
\dontleavehmode
%\barcode[alternative=qr code,text={This is ConTeXt MKIV : #1}]
\barcode[alternative=qr code,text={This is ConTeXt LMTX}]
\barcode[alternative=qr code,text={\input{tufte}},width=3cm]
\stopTEXpage
\stoptext
The resulting PDF has just empty page
Best regards,
Ivan___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] zint module on LMTX
Hi Pablo, I'm resurrecting this thread, as I've just managed to get some progress on Windows with zint in LMTX. The thing is that you need 64-bit DLL, because LuaMetaTex is built for 64-bit architecture on Windows. As it is not available, I built 64-bit zint.dll (and zlib + libpng) from the latest git sources (2.11.1.9 (dev)), renamed it to libzint.dll and placed in appropriate place, as per the instructions. But there are still some problems... here is the excerpt from the log: modules > using user prefixed file 'libs-imp-zint' modules > 'zint' is loaded open source > level 2, order 3, name 'c:/Data/context/tex/texmf-context/tex/context/base/mkxl/libs-imp-zint.mkxl' resolvers > lua > loading file 'c:/Data/context/tex/texmf-context/tex/context/base/mkxl/libs-imp-zint.lmt' succeeded close source> level 2, order 3, name 'c:/Data/context/tex/texmf-context/tex/context/base/mkxl/libs-imp-zint.mkxl' optional> using library 'c:/Data/context/tex/texmf-win64/bin/lib/luametatex/zint/libzint.dll' zint> something went wrong: invalid result vector zint> something went wrong: invalid result vector backend > xmp > using file 'c:/Data/context/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1, subpage 1 zint> something went wrong: invalid result vector zint> something went wrong: invalid result vector zint> something went wrong: invalid result vector zint> something went wrong: invalid result vector zint> something went wrong: invalid result vector zint> something went wrong: invalid result vector I tested the library with the generated CLI tool, and I get the barcode images created. Although, png format is not working, I get file with length 0 and no error whatsoever. It could be that there is something wrong with the build, I'll try to figure out. Best regards, Ivan Дана 17.03.2022. у 1:32, ntg-context-requ...@ntg.nl пише: On 3/16/22 18:05, Hans Hagen via ntg-context wrote: On 3/16/2022 5:37 PM, Pablo Rodriguez via ntg-context wrote: Dear list, using latest LMTX and following the steps from https://wiki.contextgarden.net/Barcodes#Zint_module, I’m afraid I don’t get any barcode either in Linux or Windows. Minimal sample: \starttext \usemodule[zint] \barcode[alternative=isbnx, text=9783865419026, width=4cm] \stoptext [...] Are you sure that you have the latest zint? (from sourceforge) Many thanks for your reply, Hans. I have version 2.9.2 on Linux and version 2.10 on Windows. I’ll try to install the new version on Linux and report results here. Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Transliteration
Hello!
I've been working on a Serbian book and I had to transliterate it from
cyrillic to latin.
There's been some nice improvement in transliteration, and I would like
to propose a small change.
One of the peculiarities that current transliteration mechanisms (both
internal one and the 3rd party module from Philipp Gesang)
don't process is that Љ, Њ and Џ are transliterated to Lj, Nj and Dž in
normal words that start the sentence, or in names that normally start
with a capital letter,
but in titles written in all capitals they should be transliterated to
LJ, NJ and DŽ.
So, the quick solution was to update the current mapping vector and add
another one (that is attached) that maps cyrillic capitals to LJ, NJ and DŽ
and set the correct 30 letters used in Serbian language.
It requires a bit more manual work to set the correct mapping for all
capitals text, but it works.
I have also merged the Serbian hyphenation patterns, so there is no need
to switch the language in order to have hyphenation in transliterated text.
That was possible because cyrillic and latin scripts use different code
points, and there are no conflicts in patterns.
So I suggest merging the patterns for Serbian cyrillic and latin.
There is another issue if one wants to use a dropcap and the rest of
that first word, and several following words are to be typeset in small
caps.
If that first letter is Љ (or other two letters that transliterate as
digraphs), then the second letter of the digraph is not typeset in small
caps because
it gets injected before the group that turns on small caps.
For example:
\placeinitial
Љ{\sc уди нису знали}
but this is quite a special case...
Regards,
Ivan
return {
transliterations = {
["c2l"] = {
mapping = {
["А"] = "A", ["а"] = "a",
["Б"] = "B", ["б"] = "b",
["В"] = "V", ["в"] = "v",
["Г"] = "G", ["г"] = "g",
["Д"] = "D", ["д"] = "d",
["Ђ"] = "Đ", ["ђ"] = "đ",
["Е"] = "E", ["е"] = "e",
["Ж"] = "Ž", ["ж"] = "ž",
["З"] = "Z", ["з"] = "z",
["И"] = "I", ["и"] = "i",
["Ј"] = "J", ["ј"] = "j",
["К"] = "K", ["к"] = "k",
["Л"] = "L", ["л"] = "l",
["Љ"] = "Lj", ["љ"] = "lj",
["М"] = "M", ["м"] = "m",
["Н"] = "N", ["н"] = "n",
["Њ"] = "Nj", ["њ"] = "nj",
["О"] = "O", ["о"] = "o",
["П"] = "P", ["п"] = "p",
["Р"] = "R", ["р"] = "r",
["С"] = "S", ["с"] = "s",
["Т"] = "T", ["т"] = "t",
["Ћ"] = "Ć", ["ћ"] = "ć",
["У"] = "U", ["у"] = "u",
["Ф"] = "F", ["ф"] = "f",
["Х"] = "H", ["х"] = "h",
["Ц"] = "C", ["ц"] = "c",
["Ч"] = "Č", ["ч"] = "č",
["Џ"] = "Dž", ["џ"] = "dž",
["Ш"] = "Š", ["ш"] = "š",
}
},
["C2L"] = {
mapping = {
["А"] = "A", ["а"] = "a",
["Б"] = "B", ["б"] = "b",
["В"] = "V", ["в"] = "v",
["Г"] = "G", ["г"] = "g",
["Д"] = "D", ["д"] = "d",
["Ђ"] = "Đ", ["ђ"] = "đ",
["Е"] = "E", ["е"] = "e",
["Ж"] = "Ž", ["ж"] = "ž",
["З"] = "Z", ["з"] = "z",
["И"] = "I", ["и"] = "i",
["Ј"] = "J", ["ј"] = "j",
["К"] = "K", ["к"] = "k",
["Л"] = "L", ["л"] = "l",
["Љ"] = "LJ", ["љ"] = "lj",
["М"] = "M", ["м"] = "m",
["Н"] = "N", ["н"] = "n",
["Њ"] = "NJ", ["њ"] = "nj",
["О"] = "O", ["о"] = "o",
["П"] = "P", ["п"] = "p",
["Р"] = "R", ["р"] = "r",
["С"] = "S", ["с"] = "s",
["Т"] = "T", ["т"] = "t",
["Ћ"] = "Ć", ["ћ"] = "ć",
["У"] = "U", ["у"] = "u",
["Ф"] = "F", ["ф"] = "f",
["Х"] = "H", ["х"] = "h",
["Ц"] = "C", ["ц"] = "c",
["Ч"] = "Č", ["ч"] = "č",
["Џ"] = "DŽ", ["џ"] = "dž",
["Ш"] = "Š", ["ш"] = "š",
}
}
}
}
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] midi
>That is way too ambitious, maybe more like TeX (but in order to suite >tex/mp extreme precision we would have to support microtones which is >not in midi so that immediate abandons the project). Of course, when >Mojca had ever push for 流TeX I'd given it a try. Too late now. > >Hans Hans, it is possible to set up any scale through MIDI ;-) I use that to emulate historical quarter-comma meantone keyboard tuning for some 16th century harpsichord music from Byrd, for example... Ivan чет, 4. феб 2021. 00:33 је написао/ла: > Send ntg-context mailing list submissions to > ntg-context@ntg.nl > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.ntg.nl/mailman/listinfo/ntg-context > or, via email, send a message with subject or body 'help' to > ntg-context-requ...@ntg.nl > > You can reach the person managing the list at > ntg-context-ow...@ntg.nl > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ntg-context digest..." > Today's Topics: > >1. midi (Hans Hagen) >2. Re: midi (Henning Hraban Ramm) >3. Re: midi (Hans Hagen) >4. Re: midi (Fabrice L) >5. Re: midi (Jairo A. del Rio) > > > > -- Forwarded message -- > From: Hans Hagen > To: mailing list for ConTeXt users > Cc: > Bcc: > Date: Wed, 3 Feb 2021 18:09:19 +0100 > Subject: [NTG-context] midi > Hi, > > So, in context, we can do text, and we can do graphics, and also fonts, > now do we also need an interface to midi? > > https://www.youtube.com/watch?v=dIKEiKTVwgE > > Hans > > - >Hans Hagen | PRAGMA ADE >Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > - > > > > > -- Forwarded message -- > From: Henning Hraban Ramm > To: mailing list for ConTeXt users > Cc: > Bcc: > Date: Wed, 3 Feb 2021 19:09:13 +0100 > Subject: Re: [NTG-context] midi > > > Am 03.02.2021 um 18:09 schrieb Hans Hagen : > > > > Hi, > > > > So, in context, we can do text, and we can do graphics, and also fonts, > now do we also need an interface to midi? > > Are you thinking about Knuth’s ĩTeX? > Otherwise we have LilyPond. > > > https://www.youtube.com/watch?v=dIKEiKTVwgE > > funny idea > > HR > > > > -- Forwarded message -- > From: Hans Hagen > To: mailing list for ConTeXt users , Henning Hraban > Ramm > Cc: > Bcc: > Date: Wed, 3 Feb 2021 19:39:53 +0100 > Subject: Re: [NTG-context] midi > On 2/3/2021 7:09 PM, Henning Hraban Ramm wrote: > > > >> Am 03.02.2021 um 18:09 schrieb Hans Hagen : > >> > >> Hi, > >> > >> So, in context, we can do text, and we can do graphics, and also fonts, > now do we also need an interface to midi? > > > > Are you thinking about Knuth’s ĩTeX? > > That is way too ambitious, maybe more like TeX (but in order to suite > tex/mp extreme precision we would have to support microtones which is > not in midi so that immediate abandons the project). Of course, when > Mojca had ever push for 流TeX I'd given it a try. Too late now. > > Hans > > - >Hans Hagen | PRAGMA ADE >Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > - > > > > > -- Forwarded message -- > From: Fabrice L > To: mailing list for ConTeXt users > Cc: > Bcc: > Date: Wed, 3 Feb 2021 14:00:12 -0500 > Subject: Re: [NTG-context] midi > Hi, > > Off topic (I hope this is ok), an animation made 100% with ConTeXt / > MetaFun. Several elements in the 6 840 images are sync to the music (i.e > images « react » to music - although imperfectly). Theses thousand of pages > are used to make a 3m49s animation. If somebody if ever interested I can > give more details of the process. > > https://youtu.be/3x03g-eHFC8 > > Fabrice. > > Le 3 févr. 2021 à 12:09, Hans Hagen a écrit : > > Hi, > > So, in context, we can do text, and we can do graphics, and also fonts, > now do we also need an interface to midi? > > https://www.youtube.com/watch?v=dIKEiKTVwgE > > Hans > > - > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > - > > ___ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context@ntg.nl / >
Re: [NTG-context] A not so short introduction to ConTeXt Mark IV
One nice tool that I use for translation is https://po4a.org/index.php.en I used it to translate (and maintain) complete Vim documentation. It could be adapted to work with Context (there is already a Latex module) Regards, Ivan сре, 6. јан 2021. 12:56 је написао/ла: > Send ntg-context mailing list submissions to > ntg-context@ntg.nl > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.ntg.nl/mailman/listinfo/ntg-context > or, via email, send a message with subject or body 'help' to > ntg-context-requ...@ntg.nl > > You can reach the person managing the list at > ntg-context-ow...@ntg.nl > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ntg-context digest..." > Today's Topics: > >1. Re: A not so short introduction to ConTeXt Mark IV > (Bruce Horrocks) >2. Re: A not so short introduction to ConTeXt Mark IV > (Joaquín Ataz López) >3. Re: A not so short introduction to ConTeXt Mark IV > (Augusto Stoffel) >4. Re: Randomize order of blocks (Otared Kavian) >5. Re: Randomize order of blocks (Otared Kavian) > > > > -- Forwarded message -- > From: Bruce Horrocks > To: "ntg-context@ntg.nl" > Cc: > Bcc: > Date: Wed, 6 Jan 2021 00:36:23 + > Subject: Re: [NTG-context] A not so short introduction to ConTeXt Mark IV > > > > On 5 Jan 2021, at 20:31, Garulfo wrote: > > > > Hi all, > > > > I saw that Mojca created a directory > > https://github.com/contextgarden/not-so-short-introduction-to-context > > > > Joaquín, if you agree, and if > > - you provide me with the spanish + english source codes > > - Mojca provide you and me with github write access (garulfogb account) > > > > i could : > > 1/ push the current code > > 2/ start to write a github wiki page (+ link on contextgarden) to > describe : > > - for you : how to update from your own computer (the official source) > > - for any user : how to use git to get the source + link to this list > for discussion. > > > > Does anybody has a guide about "how to set up a documentation > translation project with git ?". > > One requirement will probably to define how propositions are officially > validated. Does it requires Joaquín to learn how to use git ? Can we just > work by sending files (or patches) to Joaquín who will update with a single > git command ? > > I think we need to be really clear about what we want to achieve here. > > 1) Is it just making the source plus the PDF available for download? If so > then there are plenty of simpler ways to do that than using Git. > > 2) If it is to gather feedback on things like typos then we don't need > Git. For example I spotted a missing ']' in the English translation so all > I need is a way to submit a 'bug report' not access to the source. > > 3) So what is left? To provide a way for translators to be notified of > changes to the original? To provide a collaboration mechanism for > significant changes to the document? > > I don't see that Git adds much in the way of value unless Joaquín and the > translators are already very familiar with it -- because the learning curve > is very steep and recovering from mistakes (made to the repository itself > rather than to the document content) can sometimes be extremely difficult. > > -- > Bruce Horrocks > Hampshire, UK > > > > > > -- Forwarded message -- > From: "Joaquín Ataz López" > To: ntg-context@ntg.nl > Cc: > Bcc: > Date: Wed, 6 Jan 2021 06:26:34 +0100 > Subject: Re: [NTG-context] A not so short introduction to ConTeXt Mark IV > I don't really know anything about git, so I can't give my opinion about > what is or isn't convenient to do. Certainly to report bugs in my text I > don't think it takes anything more than an e-mail to send them to me. > Having a repository can be useful to keep a version that is always up to > date; but that, on the other hand, would force me to be continually > modifying the text, which in principle is not my intention. I do not > exclude that there will be other versions in the future, but for the > moment this is not part of my plans. And if there were other versions, > it would be more to add some chapter; mainly I think that the most > important material that is missing is the one related to XML, Lua and > Metapost, that is: the three additional languages in which a ConTeXt > document can be written. But I am far from being able to write anything > about any of those three aspects. Some member of the list has offered to > help me with it, but not immediately (we all have a lot of work). > > The original idea, I think, was to provide a platform that would allow > different collaborators to translate the text into different languages. > Whether or not git is the best solution for that purpose, I really don't > know. > > What I would appreciate is that guide on "how to set up a documentation > translation project with git? that Garulfo proposes. > > El 5/1/21 a
Re: [NTG-context] new upload
Дана 07.11.2020. у 23:42, Hans Hagen пише: Question: do we really need all these 'named characters' or can we at some point ditch many .. I assume that users who key in greek and cyrillic use unicode nowdays (no hurry, just wondering). That's true Hans, normally I use UTF-8 encoding and a keymap in Vim so I can enter cyrillic text and english commands quite easilly (swapping between with CTRL-^). Ivan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] new upload
Дана 07.11.2020. у 23:42, Hans Hagen пише: Question: do we really need all these 'named characters' or can we at some point ditch many .. I assume that users who key in greek and cyrillic use unicode nowdays (no hurry, just wondering). That's true Hans, normally I use UTF-8 encoding and a keymap in Vim so I can enter cyrillic text and english commands quite easilly (swapping between with CTRL-^). Ivan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Adding built-in support for Serbian language
Дана 30.10.2020. у 16:42, Mojca Miklavec пише: > Would you be willing to also prepare the latin one then? > The codes should be sorted out by Hans (potentially with some help), > but we definitely want to use "sr-latn" and "sr-cyrl". Here is the lang-txt.lua diff with labels transliterated from serbian cyrillic to latin script. Other files basically do not differ, only codes should be sorted out. Language definition stays the same. Regards, Ivan Serbian-Latn.7z Description: Binary data ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Adding built-in support for Serbian language
Dear Mojca, Дана 30.10.2020. у 19:10, Mojca Miklavec пише: > Would you be willing to also prepare the latin one then? > The codes should be sorted out by Hans (potentially with some help), > but we definitely want to use "sr-latn" and "sr-cyrl". Sure, I will tomorrow create a transliteration to latin script and post diffs here. What you propose is in fact already used in some other places, I agree with you. > For the longer names there is some more freedom. LaTeX uses "serbianl" > and "serbianc", I think, but I believe we can come up with something > nicer. > Maybe something along the lines of the following? > \mainlanguage[serbian][script=latn] > or >\mainlanguage[serbian-latin] >\mainlanguage[serbian-cyrillic] > No clue, really. > > Thank you, > Mojca > > (PS: I would say that adding support for transliteration of the text > from one script to the other would be a really nice feature. Then you > could type your text for a book once and have it typeset in both > versions without any extra effort :) As for transliteration, cyrillic to latin is one-to-one, straightforward with no exceptions. A simple table lookup is enough. Going from latin to cyrillic, there are some exceptions, but we could solve that. I can provide Hans with all that is needed. Ivan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Adding built-in support for Serbian language
Appologies, I have forgot to attach the file :$ Here is it. Ivan serbian.7z Description: Binary data ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Adding built-in support for Serbian language
Hello all, I have recently started using ConTeXt. I've found that the distribution includes a proper (cyrillic) hyphenation file for Serbian language, but a complete language support is still not implemented. Therefore, I've added what I think is required, did some testing by putting changed files in my texmf-local, and the result looks fine. There is only one thing that requires a decision from the development team. Serbian language uses two scripts: cyrillic and latin. Context language codes are using 2 letters for identification. So I'm not sure how to include both scripts. What I'm sending now is a cyrillic script implementation, using the code "sr". It is trivial to generate (completely automatic) latin script version of these changes, once it is decided how to label it. Best regards, Ivan ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
