Re: patch to enable clang compilation of pil32 (on OSX)
Hi Illo, I hope some day to have the time to port pil64 on OSX -- although I hope /Mr.Burger/ will do it a lot sooner ;) Sorry! Now I've taken a fresh look at the matter again. And I must say that I'm frustrated. There are too many changes. All the trouble is because of the requirement of position indepent coding. Needs to change a lot of code, and gets short of registers in some cases. The problem is that x86 is a bad architecture for position independent code. Many indirections can't be done in a single instruction. So I don't want to waste my time on that. Sorry again to the Mac users! Please try to stay with the emulator, it works all right except being a little slow. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: patch to enable clang compilation of pil32 (on OSX)
On Mar 23, 2013, at 11:50 AM, Alexander Burger a...@software-lab.de wrote: I hope some day to have the time to port pil64 on OSX -- although I hope /Mr.Burger/ will do it a lot sooner ;) Sorry! Now I've taken a fresh look at the matter again. And I must say that I'm frustrated. There are too many changes. [...] Yep I took a quick look as well and after some tinkering I've come to the same conclusion. But I'm sorry to hear that from you. Thanks anyway! [...] Sorry again to the Mac users! Please try to stay with the emulator, it works all right except being a little slow. Alas, it is a lot slower in some cases (as trivial as interpreting huge CSV files that cannot be converted to picolisp DBs because they change every single day). Personally, I will stick with pil32: it may show its age, but it works its magic anyway. Ciao, Illo. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
tex to pdf and cyrillic text
ALT--PqdoetPd1364072482 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 IEhpIEFsZXgsCkkndmUgdGVzdGVkIGNvbnZlcnRpbmcgdGV4LWZpbGUsIGdlbmVyYXRlZCBieSB0 aGUgd2lraSB0byBwZGYgb24gbXkgaG9tZSBVYnVudHUgCldoZW4gSSBoYXZlIGN5cmlsbGljIHRl eHQsIG9ubHkgYWRkaW5nIHRoZXNlIHN0cmluZ3MgcmVzdWx0cyB0byB2YWxpZCBwZGY6CsKgClx1 c2VwYWNrYWdlW3V0Zjhde2lucHV0ZW5jfQpcdXNlcGFja2FnZVtlbmdsaXNoLHJ1c3NpYW5de2Jh YmVsfQpcdXNlcGFja2FnZXtjbWFwfQoKVGhhdCB3YXMganVzdCBmb3IgaW5mbywgYmVjYXVzZSBJ IGN1cnJlbnRseSBkb24ndCB3YW50IHRvIGluc3RhbGwgYSBsb3Qgb2YgcGFja2FnZXMgaW50byBt eSBGcmVlQlNEL05hbm9CU0QgYm94IDopIEJlc3QgcmVnYXJkcywgCk1hbnN1csKg ALT--PqdoetPd1364072482 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 CjxIVE1MPjxCT0RZPkhpIEFsZXgsPGJyPkkndmUgdGVzdGVkIGNvbnZlcnRpbmcgdGV4LWZpbGUs IGdlbmVyYXRlZCBieSB0aGUgd2lraSB0byBwZGYgb24gbXkgaG9tZSBVYnVudHUgPGJyPldoZW4g SSBoYXZlIGN5cmlsbGljIHRleHQsIG9ubHkgYWRkaW5nIHRoZXNlIHN0cmluZ3MgcmVzdWx0cyB0 byB2YWxpZCBwZGY6PGJyPiZuYnNwOzxicj48cD5cdXNlcGFja2FnZVt1dGY4XXtpbnB1dGVuY308 YnI+XHVzZXBhY2thZ2VbZW5nbGlzaCxydXNzaWFuXXtiYWJlbH08YnI+XHVzZXBhY2thZ2V7Y21h cH08YnI+PGJyPlRoYXQgd2FzIGp1c3QgZm9yIGluZm8sIGJlY2F1c2UgSSBjdXJyZW50bHkgZG9u J3Qgd2FudCB0byBpbnN0YWxsIGEgbG90IG9mIHBhY2thZ2VzIGludG8gbXkgRnJlZUJTRC9OYW5v QlNEIGJveCA6KTwvcD5CZXN0IHJlZ2FyZHMsIDxicj5NYW5zdXImbmJzcDs8L0JPRFk+PC9IVE1M Pgo= ALT--PqdoetPd1364072482-- -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
tex to pdf and cyrillic text
Hi Alex, Sorry, my previous letter was not plain text I've tested converting tex-file, generated by the wiki to pdf on my home Ubuntu When I have cyrillic text, only adding these strings results to valid pdf: \usepackage[utf8]{inputenc} \usepackage[english,russian]{babel} \usepackage{cmap} That was just for info, because I currently don't want to install a lot of packages into my FreeBSD/NanoBSD box :) Best regards, Mansur