text:
Heart Exeter
Crime's Fallen Across Devon And Cornwall
In the year up until March 2013 the number of recorded offences have fallen by 6000.
Overall crime across Devon, Cornwall and the Isles of Scilly has fallen by 6.7%.
It follows last years disappointing figures, but now the number of crimes being reported, which relate to burglary and vehicle offences have seen significant reductions, although violent crime is still a problem.
There has also been an increase in sexual offences, a crime Heart understands, still remains under reportered - It's thought high profile cases like the Jimmy Saville investigation will encourage more victims to come forward.
Chief Constable Shaun Sawyer is encouraged by these latest figures but recognises there is still much work to do. He said, 'I am in no doubt that my officers and staff have responded and worked extremely hard these last 12 months, after some disappointing figures last year, so that once again we are back to some historically low crime levels.'
'There has been significant falls in domestic burglaries, down nearly 21% and vehicle crime is down by over 12%. Criminal damage (the sort of crimes that blight our neighbourhoods) has also fallen by nearly 14% and robbery has fallen by just over 16%.'
'These are good results. I am enormously proud of my officers and staff in the way they have got on with things, despite the organisation having to make some necessary but challenging decisions. It is through their hard work and continued focus in delivering an excellent service to the public that we have been able to achieve these results.'
'There is more work to do though, particularly around violent crime. Last year violence with injury had increased across the force area. This is a priority area for us and I'm pleased to say that this has fallen by nearly 4%.'
'The wider, violence against the person measure (offences where there is no physical injury) saw an increase of over 5% which remind us there are challenges we continue to face. I have asked my senior officers to look at this area in detail and put in place plans to address this measure which I hope will begin to bear fruit next year.'
Another area that has seen an increase is sexual offences which have seen a rise of 2.6% - these are offences which are thought to be under reported. High profile prosecutions in Devon and Cornwall, along with Operation Yewtree 'the Jimmy Saville investigation' can only serve to help in raising awareness and encourage victims to come forward.'
'Partnership working is another critical yet often overlooked area that can have a significant effect on long term crime figures.'
'Chief Constable Sawyer also added, 'These effective partnerships must continue to develop so that improved practices can be sought to address complex problems. This will lead to more offenders being brought to justice and fewer victims of crime and ultimately safer communities where we all live. I am working closely with the Police and Crime Commissioner to make sure Devon, Cornwall and the Isles of Scilly remain one of the safest places in the country to live.'


text:
Difference between revisions of "Informer 304"
From Terminals
Legalize (talk | contribs)
(Created page with "The Informer 304 terminal was introduced in September, 1979.<ref>[http://books.google.com/books?id=ZIfqFFpyXo8C&lpg=PA6&pg=PA6 "AT&T Begins Testing EIS"], Computerworld, Septembe...")
The Informer 304 terminal was introduced in September, 1979.<ref>[http://books.google.com/books?id=ZIfqFFpyXo8C&lpg=PA6&pg=PA6 "AT&T Begins Testing EIS"], Computerworld, September 3, 1979, pg. 6</ref>
The Informer 304 terminal was introduced in September, 1979.<ref>[http://books.google.com/books?id=ZIfqFFpyXo8C&lpg=PA6&pg=PA6 "AT&T Begins Testing EIS"], Computerworld, September 3, 1979, pg. 6</ref> In May, 1981 the price was $2,295.<ref>[http://books.google.com/books?id=aScefDgbsnUC&lpg=PA94&pg=PA94 "Informer 304 Runs With DEC, NCR, DG, Univac, Other CPUs"], Computerworld, May 4, 1981, pg. 94.</ref>
{{References}}
The Informer 304 terminal was introduced in September, 1979.[1] In May, 1981 the price was $2,295.[2]
↑ "AT&T Begins Testing EIS", Computerworld, September 3, 1979, pg. 6
↑ "Informer 304 Runs With DEC, NCR, DG, Univac, Other CPUs", Computerworld, May 4, 1981, pg. 94.
Retrieved from "https://terminals-wiki.org/wiki/index.php?title=Informer_304&oldid=1692"
Terminals Wiki
Code Charts
About Terminals

redpajama_set_name: RedPajamaCommonCrawl


Dürr's modular, energy-efficient wet systems use electrodialysis, providing the basis for perfect corrosion protection on each and every vehicle body.
In the base coat section, along with pretreatment (i.e. cleaning, degreasing and phosphating the body), electrocoating is a key process. It entails immersing the body in a tank of paint diluted with water, through which an electrical current is passed.Applying the voltage triggers an electrolysis process that creates a highly resistant bond between the paint and the positively charged (cathode) body. Acidic ions remain in the tank and must be separated and filtered out of the solution through membranes. The dialysis cell is the structural unit made up of the anode and the membrane.
Dürr is a leading supplier of dialysis cells. Our EcoCell is available in 4 versions, each with its own application-specific benefits.
Our innovative system concept EcoDC MACS provides flexible control over single anodes and anode groups. Because it's modular, you can set different voltage profiles for each body type, which improves both energy efficiency and coating quality.


CA-Clipper | Viva Clipper !
This is a standard for establishing and maintaining NANFOR.LIB, a public-domain, user-supported library of functions designed to interface with Computer Associates CA-Clipper, version 5.01a, and later. You are encouraged to read it over and forward comments to Glenn Scott, CIS ID [71620,1521].
In October and November of 1990, a discussion on the evolution of third-party products, vendors, and marketing took place on the CompuServe Information Service's Nantucket Forum (NANFORUM). During this discussion, a forum subscriber named Alexander Santic suggested the idea of a user-supported Clipper function library, available to all on the CompuServe Information Service (CIS). A number of subscribers, including several Clipper third party developers, and some Nantucket employees, expressed their support. This standard was a first step toward organizing such an endeavor.
Release 1.0 of the toolkit was made available in April, 1991 and had nearly 150 functions. By the time version 2.0 was released in August, 1991, the 1.0 library had been downloaded nearly 700 times by CompuServe users. By October of 1992, release 2.0 had been downloaded over 2100 times. The source code had been downloaded nearly 1500 times. In addition, release 2.0 was placed on the massive Internet archive site called SIMTEL20 where it was downloaded by CA- Clipper users worldwide. Over the course of the year that release 2.0 was available, seven patches were issued, each one gathering nearly 1000 downloads.
Computer Associates International, Inc. acquired Nantucket in the summer of 1992 and subsequently renamed NANFORUM to simply CLIPPER. In addition, the Clipper product itself was renamed to CA-CLIPPER. Despite the name changes, forum members decided to keep the toolkit's name as "The Nanforum Toolkit," partly for nostalgia. References to NANFORUM in this RFC have been replaced with CLIPPER.
CA-Clipper is a registered trademark of Computer Associates International, Inc. Computer Associates will be referred to as CA throughout this document.
NANFOR.LIB is a project independent of any third party developer or CA. There is no official "sanction" or "seal of approval" from CA of any kind. In addition, NANFOR.LIB routines will be accepted and included without regard for whether or not routines performing a similar function are included in a commercial third party or CA product.
It is desired that NANFOR.LIB not compete with third party products but rather fill in the holes in CA-Clipper's standard library. However, there will be some overlap into commercial third-party library functions, so it would be best if this is never taken into consideration when deciding on including a particular function.
Developers submitting NANFOR.LIB routines can and will be corporate developers, third party developers, independent consultant / programmers, hobbyists, and other CA-Clipper people. Perhaps even CA employees will contribute. No one is excluded or included due to any particular affiliation.
CA employees submitting functions are doing so as individuals, and are not making a policy of involving CA in the project, nor are they committing CA to supporting the public domain library.
NANFOR.LIB functions, no matter what language they are written in, will be designed to work with CA-Clipper version 5.01a and later. Many of the functions, particularly those that use the EXTEND system, will be compatible with the Summer 1987 version of CA-Clipper. However, ensuring Summer 87 compatibility will be the responsibility of the user. If a user wants a function to work with Summer 87, she will have to modify the code herself if necessary. In many cases, this is a trivial task.
Queries from new users interested in finding NANFOR.LIB should be handled in a uniform and courteous way. A short text file will be created that will briefly explain NANFOR.LIB, who the current people maintaining it are, and how to get a hold of it. This text message can be sent in response to any query. TAPCIS users will find this method very easy to implement.
NANFOR.LIB, its source code, and documentation will be public-domain software. It is not for "sale", and shall not be sold. No fee or contribution of any kind will be required for anyone wanting a copy, other than what they would normally pay to download it from CompuServe. Users will be encouraged to submit functions via CompuServe.
It is possible that copies of NANFOR.LIB will be downloaded and distributed elsewhere. This is encouraged, but the only copy of NANFOR.LIB and all associated documentation that will be maintained by volunteers is in an appropriate library on the CIS CLIPPER Forum.
This will contain the files NANFOR.LIB (library), and NANFOR.NG (Norton Guide).
This will contain all the library source code, makefile, and other source-code related materials.
This contains an ASCII format, as well as a WordPerfect 5.1 format copy of NANFOR.RFC named NFRFC.TXT (ASCII) and NFRFC.WP5 (WordPerfect 5.1).
These are patch files (see paragraph 4.5.1).
It is possible that more than one developer will submit a function or package of functions that perform substantially the same services. In that event, the referees will choose one to be included based on power, functionality, flexibility, and ease of use. Due to the cooperative, non-commercial nature of the library, no one's feelings should be hurt by excluding duplicate functions.
In addition, it is possible that two substantially similar functions or packages will benefit from merging them together to provide new functionality. This will be the prerogative of the referees (see paragraph 6.3), in close consultation with the authors.
Each author submitting source code must include as part of that code a statement that this is an original work and that he or she is placing the code into the public domain. The librarian (see paragraph 6.1) and referees should make a reasonable effort to be sure no copyrighted source code, such as that supplied with some third party libraries, makes it into NANFOR.LIB. However, under no circumstances will the librarian, referees, or any other party other than the submitter be responsible for copyrighted code making it into the library accidentally.
Full source code must be provided by the author for every routine to be included in NANFOR.LIB. No routine, no matter what language, will be put into the library on the basis of submitted object code.
Due to the volume of submissions expected, librarians and referees may not have the time to fix inconsistencies in documentation format, function naming, and other requirements. Therefore, the librarian shall expect source code to arrive in proper format before proceeding further with it.
In a cooperative effort like this, it is very difficult to enforce some standard of quality and/or usefulness. For example, a package of functions to handle the military's "Zulu time" may be very useful to some, and unnecessary to others.
The Nanforum Toolkit will by its very nature be a hodgepodge of routines, some of very high quality, some not so high. It is up to the users to improve it. It will be complete in some areas and vastly inadequate in others. It is up to the users to fill in the holes.
We shall err on the side of including "questionable" functions, provided they seem to work. Debates on the quality of the library's source code shall be encouraged and will take place in the proper message section of the CompuServe CLIPPER forum.
Source code will be submitted to the librarian, the documenter (see paragraph 6.2), or one of the referees. Code will be added if it has been reviewed, and approved by at least one, but preferably two, referees.
Code not meeting the documentation or source code formatting standards will generally be returned to the author with instructions.
Referees will test the submitted code. When the referees have finished evaluating a submission, they will report their approval or disapproval to the librarian, with comments.
Every effort should be made to make sure that the C and ASM functions are reviewed by referees with suitable C and ASM experience.
As new functions are submitted, they will added to the library, and the documentation updated. Because this is a volunteer project, and because of the complexity involved in coordinating testing, documentation, and delivery, there will be no fixed interval for updates.
The major version will be numeric, starting from 1. This will change with each quarterly update. The minor version will change with each bug fix. This will start with zero and continue until the next major update, at which point it will revert to zero again.
Typical version numbers might be 1.1, 2.12, 15.2, etc.
The .LIB file, and all associated files, will carry a date stamp corresponding to the day it is released on the CLIPPER forum. The file time stamps shall correspond to the version number (i.e., 1:03am is version 1.3).
As the library and its associated documentation are updated, simple announcements will be posted on the CLIPPER forum. This is the only place where an update shall be announced. An update will be announced after it has been successfully uploaded to the appropriate library on CompuServe.
where <n> is a number starting from 1. Patches will be numbered sequentially. Patches will be deleted every time a new version of NANFOR.LIB goes on-line.
A patch zipfile may optionally contain .OBJ files to be replaced in user libraries via a LIB utility.
Technical support will work just as any technical subject on the CompuServe CLIPPER forum works. Users will post questions and suggestions to a particular message area or thread, and anyone who knows the answer should respond. No one is obliged to answer, but it is considered good form to respond with something, even if one doesn't know the answer.
Support will include help on recompiling the routines or modifying the source.
In order to assist users of CA-Clipper third party linkers (such as WarpLink or Blinker), NANFOR.LIB may need to broken up into root and overlay sections. How this will be done will be determined when splitting becomes necessary.
The librarian is not responsible for testing every possible linker for NANFOR.LIB compatibility. It is hoped that linker users will submit appropriate link scripts or other documentation for posting in the appropriate section on the CLIPPER forum.
It is possible that at some future date, it will make sense to split NANFOR.LIB into separate functional areas (e.g., video routines vs. date routines, etc). This RFC will be modified accordingly should that need arise.
The goal of this standard is not to force anyone to rewrite his code for this library, but to create some consistency among the functions so that they may more easily maintained and understood by all CA-Clipper developers, both novice and advanced.
However, it is extremely important that anyone submitting code attach the proper headers and documentation and fill them out correctly. This will make it much easier for code to be added to the library.
Figure 1 shows a header that must be included at the top of every piece of source code submitted to the library. This header will work with both CA-Clipper and C code. For ASM code, substitute each asterisk ("*") with a semicolon (";") and delete the slashes ("/").
Figure 1 - Standard function header.
Note that the date, revision, logfile, and modification history fields will be maintained by the librarian and should not be edited or adjusted by code authors.
The "File" field shall contain the source file name. This is often independent of the individual function name. For example, a function named ft_screen() would be included in SCREEN.PRG. As a rule, source files (.PRG, .C, .ASM) should not have the "FT" prefix.
The "Author" field should have the author's full name, and CIS number. A CIS number is important, as this will make bug fixing and other correspondence easier.
The documentation block must be carefully formatted as it is used by the documenter to produce the Norton Guide documentation for the library.
The keywords enclosed in dollar-signs delimit sections of the documentation header analogous to those in the CA-Clipper 5.0 documentation. Documentation should be written in the same style and flavor as the CA material, if possible. Refer to the CA-Clipper documentation for more detail and numerous examples.
The documentation will appear on comment lines between the keywords. Examples are optional. Do not put documentation on the same line as the comment keyword.
Note that the $DOC$ and $END$ keywords serve as delimiters. Do not place any text between $DOC$ and $FUNCNAME$, or any documentation after the $END$ keyword, unless that documentation belongs in the source code file and not in the resultant Norton Guide file.
Note the indent for readability. Parentheses shall be added after the function name as shown above.
The length of the entire $ONELINER$ shall not exceed 60 characters (this is a Norton Guide limitation).
All parameters have proper prefixes (see paragraph 5.4), and are enclosed in <angle brackets>. Optional parameters are enclosed in [square brackets] as well. An arrow should follow, pointing to the return value. If there is no return value, it should be NIL. Any others should be preceded with the proper prefix (see the CA- Clipper documentation).
Note that fields are separated by spaces and the parentheses are included.
Other documentation fields should be self- explanatory. Review the appendix for a sample. All fields are required and must be filled in. Examples should not be considered optional.
Refer to the Appendix for a sample header and documentation block.
A test driver is an optional section of C or CA- Clipper code that will only be compiled under certain circumstances. Developers are encouraged to include a short "test section" in front of their code.
The test driver is currently optional, but authors submitting Clipper code should seriously consider adding it. It is a good way to include short demos within a piece of source code, yet pay no penalty because it is only compiled if needed. It will be invoked when a #define is created that says "#define FT_TEST." This is a way for submitters to include short test routines with their functions and yet keep it all in one source file. This will be useful to end users.
This test driver may become required in a future version of the RFC.
The source code shall be formatted as described in paragraph 5.4.
Some functions will be submitted that either (1) bear a similar name to another function in the library, or (2) bear an inappropriate name. For example, a function called FT_PRINT that writes a character to the screen could be said to be named inappropriately, as a name like FT_PRINT implies some relationship to a printer. The librarian shall have the responsibility to rename submitted functions for clarity and uniqueness.
Once the library is released with a particular function included, then a function name should generally be frozen and not renamed. To do so would probably cause difficulties with users who had used the previous name and are not tracking the changes to the library.
Clipper code shall be formatted in accordance with CA's currently defined publishing standard. Although there will surely be some debate over whether this is a good idea, in general, the goal is to provide something consistent that all CA- Clipper developers will recognize.
Minor deviations will be permitted.
The CA standard usually means uppercase keywords, and manifest constants, and lower case everything else.
Refer to the CA-Clipper documentation for samples of CA's code publishing format.
C source code shall be formatted in a generally accepted way, such as Kernighan and Ritchie's style used in the book _The C Programming Language_." The use of CA's EXTEND.H is encouraged.
No particular formatting conventions are required for assembly language source code, since assembly code formatting is fairly standard. Lowercase code is preferred. Be sure to include the proper documentation header information, as described above.
Do not place ASM code in DGROUP. See paragraph 5.11.
Since many different people will be submitting routines, it is probably best if all routines that belong together are housed in the same .PRG. If there is some reason to split the .PRG, the referees and the librarian will handle that as part of library organization.
Including a ".ch" or ".h" or ".inc" file with each function would get unwieldy. For the purpose of NANFOR.LIB, all #defines, #ifdefs, #commands, #translates, etc that belong to a particular source file shall be included at the top of that source file. Since few submissions will split over multiple source files, there will usually be no need to #include a header in more than one place.
If a "ch" file will make the end user's job of supplying parameters and other information to NANFOR.LIB functions easier, then it shall be submitted as a separate entity. The referees will decide on whether to include these directives in a master NANFOR.CH file.
NANFOR.LIB routines that are written in CA-Clipper will make use of CA-Clipper 5.0's lexical scoping features to insulate themselves from the rest of the user's application.
If a package of Clipper functions is added to the library, then the lower-level, support functions will be declared STATIC as necessary.
Authors shall not use PUBLIC variables in NANFOR.LIB functions, due to the potential interference with an end-user's application or vice versa.
If a global is required for a particular function or package of functions, that global shall be accessed through a function call interface defined by the author (.e.g, "ft_setglobal()", "ft_getglobal()", and so on). Globals such as these shall be declared static in the .PRG that needs them.
The use of macros in NANFOR.LIB functions will be, for the most part, unnecessary. Since this is a CA-Clipper 5.0 library, the new 5.0 codeblock construct should be used instead. Anyone having trouble figuring out how to convert a macro to a codeblock should post suitable questions on the CLIPPER forum on CompuServe.
Any CA-Clipper 5.0 function that is only needed within the scope of one source file shall be declared STATIC. This applies mostly to NANFOR.LIB "internals" (names with an "_ft" prefix) that user programs need not access.
Segment _NanFor Word Public "CODE"
Use of CA-Clipper "internals" by code authors is allowed. However, should any code make use of an internal, i.e., a function or variable that is not part of the published CA-Clipper API, then that internal shall be clearly marked in the documentation (under "DESCRIPTION") and in the actual code, everywhere the internal is used.
Note that neither line numbers nor debugging information will find its way into NANFOR.LIB, to keep the code size down. End users may recompile NANFOR.LIB with these options enabled if they want to view NANFOR.LIB source in the debugger.
Assembly functions must compile successfully under any MSDOS assembler capable of producing the proper .OBJ file. However, care should be taken not to use any macros or special syntax particular to one vendor's assembler, because that would make it difficult for end users to recompile the source. The preferred assembler is MASM, followed by TASM.
C functions must compile successfully under any C compiler capable of interfacing to CA-Clipper. Obviously, Microsoft C, version 5.1, is the preferred development environment. Care should be taken, when writing C code, not to use any special compiler features particular to one vendor's C compiler, because that would make it difficult for end users to recompile the source.
It is very easy to write functions in C that call the compiler's standard C library functions. However, NANFOR.LIB can make no assumptions about the end user's ability to link in the standard library or any other library. Therefore, no function will be added to NANFOR.LIB that requires any other third party or compiler manufacturer's library.
The librarian will be the person who rebuilds the library from the sources and uploads the resulting deliverables to the proper CLIPPER forum library on CompuServe. The librarian generally does *not* test code or edit source code to repair formatting errors.
The documenter is responsible for maintaining the Norton and guides and keeping it in sync with each new release.
Referees are volunteers who read source code, clean it up, compile it, look for problems like potentially problematic C code, decide on which function is best, consolidate common functions, etc. They make sure the header and documentation blocks are present. There is no election or term for refereedom. One simply performs the task as long as one can and bows out when necessary.
Not everyone will be able to stay around forever to keep working on this project. Therefore, it is the responsibility of each referee, documenter, or librarian to announce as far in advance as possible his or her intention to leave, in order to give everyone a chance to come up with a suitable replacement. Don't let it die!
so not included in hbnf library.
We often do not realize the importance of people and events until many years later when the dust has settled and we can put them into perspective. Three years ago I was asked to write an article for the CDGN Magazine. It was titled "Back to the Future" and it dealt with the the role of Clipper in 1995 and into the future. I recently broke out my old copy of CDGN magazine and reread the article to see if my predictions match the current landscape.
I predicted that I would be writing my final article about Clipper in the year 2035. Many of you assumed that either I was much younger than I really am, that this was a typographical error, or that I had already lost it and was living on a ranch somewhere in California with Ronald Reagan. None of the above are true. I am now fifty-four years old. In the year 2035, I will be 91 years old but I will still be programming because in the year 2007 we will discover a new drug that restores dead brain cells. The year 2035 will mark the year that we finally arise from the ashes of the "great computer meltdown" of 2010. The meltdown will occur because of the Year 2000 debacle which will create a world-wide depression and create a political climate of hatred towards programmers that will build to a frenzy leading to "The Night of Broken Disks". Computer programmers will be fleeing to Russia, Iran and Iraq – the only safe havens in the world that will not be affected by the "Great-Satan Virus" due to their refusal to connect to the Information SuperHighway.
This great oppression of computer programmers will force those who are not killed outright, or sent to "de-programming camps" made their escape to third-world countries to hide for years in attics, befriended by a few, brave souls who know it is not their fault they were born "computer-literate". During this 20-year war on computers, an arsenal of "giant magnets" are created by the new war machine and the industrialized cities of the world are bombed with the largest "de-gaussing" campaign in history. No piece of software or database will be safe from annilation. Finally, the great war machine is defeated because it will fail to realize that it cannot maintain such a war when it destroys the very machines and software that allow it to wage war.When it is all over, a discovery is made in a little house on the Prinsengracht in Amsterdam. A old notebook computer is found in the attic and sent to a museum. While restoring the computer, a small disk is found, still fused in the disk drive. Because of its condition, it appears that the notebook had been there for many years. Much work goes into the restoration of the disk and its data and finally, it is discovered that the disk contains the diary of a young, computer-literate girl who had lived in hiding for many years. By this time, the only computer-literate people left in the world only speak Russian or Farsi, so it takes much effort to figure out how to decipher the data on the disk. Finally, a compelling and sad story emerges about a young girl who struggles to maintain her innocence, her sanity, her computer-proficiency, and her faith in God while hiding from the great de-gaussing and de-programming regime.
It is a sad story, and it takes time for the world to really understand her story, especially her references to "The Book of Clipper". What was Clipper? Was this what helped her maintain her sanity and her faith in God? What happened to the young girl? Her story spreads around the world, and a never-ending search continues for a copy of "The Book of Clipper". Finally, the search ends in a little Russian town. Not a single person realizes that "The Book of Clipper" is a reference to the manual for the computer language that every single Russian speaks fluently, until someone finds a copy of the manual that Larry Heimendinger had left at the only Russian Clipper conference ever held – in 1992. It is dusty and worn, but it is the only book left that tells the true story of Clipper. Even though every programmer in Russia can speak Clipper, not a single one of them has seen a copy of "The Book of Clipper" because none had ever been sold. The software had been pirated, and then spread from disk to disk throughout the country while the story of Clipper passed from mouth to mouth. The Russians are the only civilized society that still has a programming language, so they offer it as a gift to the world, and the world becomes whole again, and the people rejoyce, and I come out of hiding – to write my final article about Clipper.
I like to imagine that I am the angel in the story "It's a Wonderful Life" and that I have been called on by God to rescue a person who feels that his life has been lived in vain. In my rendition of the story, the desperate soul is not George Bailey but instead is Tom Rettig. Tom passed away about a year ago and I find myself haunted by him because I feel that I have never given back to him what he gave to me and the rest of the world. I often think back at what my life was like in the mid 80's. After many successful years as an Electronics Engineer my life was just not working anymore. Thieves broke into my business office and stole my computers and my software (including the backups). I was struggling with a failing computer-accessories manufacturing business that had pushed me deep into debt, and then my wife decided to just leave one day and head for greener pastures. I thought she had been kidnapped because she disappeared without a trace.
Arlo Guthrie once wrote a song about "The Last Man". He said "You think you've got it bad? Look at that guy?." I WAS that guy.
This simple question, in retrospect, was equivalent to someone posting a huge sign "Except a man be born again, he cannot see the kingdom of God". Clipper was my salvation. It allowed me to layeth down in green pastures and it restoreth my soul. So how did it come about that a person could be saved from the depths of depravity by a mere software product? We all have our stories of salvation, and they all take us down different paths but they all lead to the same place. My story in not unlike C.S. Lewis' story in "Mere Christianity", except the players are different. The Book of Clipper is not one story, but hundreds of stories all evolving from the "Platitudes of Vulcan".
Tom Rettig entered the scene around 1986 and offered an add-on product to Clipper titled "Tom Rettig's Library". Tom was a well-liked, generous person who eventually offered his library into the public-domain. Some of us are old enough to remember him as Jeff, the small boy in the original "Lassie" series on television in the 50's. I first met him at a user group in Southern California. After the meeting we went to a bar for a few beers and he sat and talked to us like we had all known him for years. He inspired us to do what he did, because he was just like us. The next day, I thought "If Tom Rettig can make a successful add-on product to Clipper, so can I". I wasn't the only person who had seen the light that night. Tom had broken new ground, had planted the first seeds, and from these seeds, an entire community of user-groups, programmers, applications, add-on products, books, magazines, et al, grew into maturity.
Have you ever heard anyone say "He's so far behind he's ahead"? By now, most of you have decided that you must move on to Windows and that there is no place for Clipper in your strategy. Many of you have already done so and are experimenting with products like VO, Delphi, VB, and Power-Builder or have created applications with these development environments. I am not writing this article to suggest that in any way, this was a bad choice. I have spent sufficient time with these products to come to the realization that Windows applications can be developed by travelling many different paths. What I am offering, however, is another perspective; one that frees us to open our minds to look at the future from a different view. Many of us have been so busy and so worried about constantly moving forward that we have forgotten how we got here in the first place, by the use of an enduring and powerful language – Clipper.
So you may be thinking "What is he talking about? Clipper is Dead!". In the sense of a product, this may be true, but in the sense of a language, it is far from true. Let's imagine that Chinese is packaged into a product named "Visual-Chinese" and this product includes a set of design-tools for creating quick-Chinese documents that can be easily integrated into our marketing documents. Soon we would find our business opened up to a new market of 1 billion people. The product becomes instantly successful and everyone love its and uses it – until, years later, when we find that our marketing documents are not delivering any sales. Why? Because the language had to be cut and trimmed to fit into the limitations of the software environment. It becomes ambiguous, arrogant and unwanted by the very people who inspired its development, so it dies and Visual-Chinese gets thrown away like every other Visual tool. Does this mean that the Chinese language dies with the product? No. Chinese is a language that will endure. It has lots of users; it is robust, and it is mature.
1. dBase – A Windows-based Interpreter.
2. FoxPro – A Windows-based Interpreter.
3. CA-Clipper – A DOS-based Xbase compiler.
4. CA-VO – A 32-bit Windows-based Xbase compiler.
5. Xbase++ – A 32-bit Multi-Platform Compiler.
dBase was the custodian of the Xbase language from around 1983 until about 1987. Unfortunately, it was an interpretive language so it never gained respectability as a true, robust language, however, it had much to offer the developer in ease-of-use and database design. dBase continues to be supported by Borland, simply because there is still money to be made in upgrades and conferences, but Borland has made it clear that they intend to make dBase programmers learn how to speak Pascal and eventually will phase Xbase out of their products.
FoxPro took over as a co-custodian of the Xbase language in about 1987 and emerged around the same time as Clipper. FoxPro defeated dBase nearly overnight simply because it was faster, not because it delivered any new language concepts. FoxPro continues to be supported by Microsoft, simply because there is still money to be made in upgrades and conferences, but Microsoft has made it clear that they intend to make FoxPro programmers learn how to speak Visual Basic and eventually will phase Xbase out of their products.
Clipper was undoubtely the best custodian of the Xbase language from 1987 to 1996. Clipper introduced the Xbase compiler, the open-architecture concept of the extend system, code blocks, locals, statics, multi-dimensional arrays, the RDD layer, the preprocessor, and language extensions. Clipper was the first Xbase custodian to give Xbase respectability as a true programming language. Clipper maintained this respectability until around 1996 when CA released CA-Clipper 5.3. CA chose to treat Clipper as a "package" rather than a "language" and alienated nearly the entire Clipper community when they bundled a Windows-IDE and several third-party products into the package. This was when Clipper died.
Computer Associates planned for VO to take over as the custodian of the Xbase language by forcing the death of Clipper and dragging CA customers into a new kind of development environment that kind of looks like Clipper, in that it inherited much of the new Clipper extensions. Unfortunately, migration to VO became cumbersome due to too many incompatabilities, poor performance, poor reliability and a third-party community who could not get their products to work with VO. VO promised it would be easy to migrate existing Clipper applications to Windows but could not deliver on the promise. Working in VO is in no way similar to working in Clipper. Many Clipper developers find that using a third-party Windows library (like Five-Win or Clip-4-Win) with Clipper is a much easier migration path than VO.
Many of us wonder why Xbase has not been given more respectability as a "mainstream" language. If Xbase is so good, why are Borland and Microsoft phasing it out of their future products? I was watching a television program the other day about an analysis of automobile technology over the years. We often assume that the best technology is what endures over time and that it eventually rises to the top. This may be true in an ideal world, but in a capitalist society, it is usually market dog-fights that determine dominance. In this analysis, it was determined that steam technology could have produced cars just as good as internal combustion technology, but Henry Ford chose the latter. Bill Gates has chosen Basic, not because it is better, but because he owns it. He doesn't own Xbase, and Bill cannot embrace something that he cannot control. Borland chose Pascal. Not because it is better, but becaused they own it.
Over the past 10 years, the success of the Xbase products has been due to the high degree of abstraction of the Xbase language, which makes it vastly simpler to acces and use operating system functions and resources. In addition, Xbase is more than just a specialized programming language, a database navigation language, or a user interface language – instead, it combines all of these roles, harmoniously integrating them with one another.
Xbase offers dynamic data types and is generally described as being highly "tolerant". Taken together, these benefits have persuaded a steadily growing community of users and developers to rely upon it as a choice for implementing mission-critical and commercial PC-desktop applications. In fact, world-wide, more than one-third of all DOS-based commercial applications now in use were written in Xbase, with Clipper accounting for the major share.
Most Windows programmers will tell you that you cannot take a standard Clipper application with @SAY..GETS, Menu Prompts, etc, and convert it to a Windows GUI program without a major change in the architecture and the functionality of the program. They claim that a text-based, modal design has too little in common with GUI-based, event-driven, non-modal design. They will tell you that it like trying to fit a square peg into a round hole. For years, I believed this because it made sense. I, like everyone else, wrote my Windows applications with a different structure than my Clipper applications. They were built around an event model rather than a procedural model and the code was tightly-bound rather than loosely-bound to the functional model. This always leaves me with an uneasy feeling because it forces me to write applications that are less modular and are platform specific. Microsoft, Borland, and CA each wants us to build applications their way. They want us to learn their programming tools, their methods, their plug-ins, their workshops, and their studios – not their language. Why? Because applications built around their environment will be harder to migrate to competitor's products than applications built around a language.
So they make sure that the language is difficult and inaccessible, and that the application cannot be maintained or migrated to any other platform, other than platforms that they support. Programmers, however, have to survive in the real world and this requires platform flexibility. The reason why so many mission- critical DOS applications are still surviving in the real world is because each development platform supports DOS as a subset, so DOS has been, out of necessity, elevated to the status "platform independent". I can run my Clipper applications under MS-DOS, PC-DOS, DR-DOS, OS/2, Windows 3.1, Windows 95, Citrix- Winframe, MULTI-DOS, Windows NT and Novell-DOS. I can run my Delphi applications only under 32-bit Windows. Is this a step forward?
In my dream, the "Ghost of Xbase Future" led me through the Land of Clipper and how it might look like up through the year 2035. I couldn't hold back my emotions as I witnessed the data meltdown and the termination of millions of programmers. I asked him "Spirit – is this a vision of how things MUST be or how things COULD be?" He never answered me. I woke up from my dream and ran to the mirror. I was relieved to see that I wasn't 91 years old but was still a young man. I exclaimed "There's still time!" I bolted to the window, looked out, and saw that The Land of Clipper looks different than it did yesterday. The paths are 32-bits wide and they lead everywhere, yet they look familiar and something tells me that there is nothing to fear at the end of these paths. Then I realized that I had not been dreaming and that Clipper had not really died at all but had been in a cocoon, waiting to metomorphose into a butterfly, one with big X's on it's wings. The butterfly is beautiful and it attracts the attention of people like Dirk Lesko (author of Funcky), of Jud Cole (author of Blinker), of Dave Kuechler (author of Comix), and others who once frolicked in the land of Clipper.
Note: This article is a summary ( by courtesy of author) original is here.


text:
Resources updated between Monday, December 08, 2014 and Sunday, December 14, 2014
13-Year old Boko Haram female suicide bomber arrested
"Nigeria is facing a rise in female teenage suicide bombers at the service of terror group Boko Haram.
"Residents of northern Nigeria are more on edge than ever. On top of a year of unprecedented terror at the hands of Boko Haram, an increasing number of young girls are donning explosive devices and blowing themselves up in public places-all in the name of the terror group, known for its egregious crimes against Nigeria's women.
"On Wednesday, two young female suicide bombers detonated in a crowded market in Kano State. The police commissioner told a local news site that the terrorists donned hijabs and attempted to go into a bank, but were stopped. They then entered a busy textile market, and went into the public bathrooms, after which two blasts shook the area, injuring seven and killing six, including the bombers. Witnesses said the girls were in their late teens and had been accompanied by a man who left soon after the blast. That same day a 13-year-old girl was arrested with explosives hidden under her hijab after walking into a medical clinic.
"Over the past eight months, there has been a disturbing spike in female suicide bombers and a rising body count to match. More than a dozen attacks have been carried out by women-with some attacks claiming up to 78 victims. This is a relatively new development: Boko Haram's first female suicide bomber was a middle-aged woman who rode a motorcycle into military barracks and blew herself up at a checkpoint this June..."
The New Face of Boko Haram's Terror: Teen Girls Document
"Human rights have not just been abused, but are 'virtually non-existent in President Hassan Rouhani's Iranian regime, the Friends of a Free Iran in the European Parliament have declared. There have been at least 1,100 executions during his 15 months in office - more than in any similar period in the past 25 years, the group said. Iran is holds the world record for the highest number of executions per capita and is the biggest executioner of juvenile offenders. Death sentences for ethnic and religious minorities have increased dramatically, it reported."
Human rights 'non-existent in Iran, group warns Document
"A resolution co-sponsored by U.S. Sen. Ted Cruz, R-Texas, Sen. Kirsten Gillibrand, D-New York, and Sen. Joe Manchin, D-West Virginia unanimously passed the Senate yesterday to condemn the use of civilians as human shields by the terrorist group, Hamas.
'The Senate has sent a united signal that we denounce Hamas' barbaric tactics and unequivocally support Israel's right to self-defense,' said Sen. Cruz. 'Even though Republicans and Democrats may be divided on many issues, there should be no daylight between us when it comes to standing up to radical Islamic terrorists including Hamas. I hope the international community will join America in condemning their deplorable use of human shields, which is a war crime. I thank my colleagues for their affirmation of our unshakable bond with the nation of Israel. We look forward to the passage of this resolution in the House or Representatives, where it has been led by Rep. Ileana Ros-Lehtinen, R-Florida and Rep. Ted Deutch, D-Florida and has 102 co-sponsors.'
Sen. Cruz's resolution:
• Strongly condemns the use of innocent civilians as human shields;
• Calls on the international community to recognize and condemn Hamas' use of human shields;
• Places responsibility for the rocket attacks against Israel on Hamas and other terrorist organizations, such as Palestine Islamic Jihad;
• Supports the sovereign right of the Government of Israel to defend its territory and its citizens from Hamas' rocket attacks, kidnapping attempts and the use of tunnels and other means to carry out attacks against Israel;
• Expresses condolences to the families of the innocent victims on both sides of the conflict;
• Supports Palestinian civilians who reject Hamas and all forms of terrorism and violence, desiring to live in peace with their Israeli neighbors;
• Supports efforts to demilitarize the Gaza Strip, removing Hamas' means to target Israel, including its use of tunnels, rockets, and other means; and
• Condemns the United Nations Human Rights Council's biased resolution establishing a commission of inquiry into Israel's Gaza operations." "
Congress Unites to Denounce Hamas and Support Israel Article
Juan Mendez, UN Special Rapporteur on torture and other cruel, inhuman or degrading treatment or punishment
UN Special Rapporteur on torture Juan E. Méndez calls the prosecution of Americans the next step, following the release of the Feinstein interrogation report.
"The Special Rapporteur stressed that this should be 'a first step in the direction of fulfilling other US obligations under Convention against Torture (CAT), namely to combat impunity and ensure accountability, by investigating and prosecuting those responsible.'"
Feinstein report leads UN expert to call for prosecution of Americans Development
While ignoring human rights violations affecting billions around the world, the UN General Assembly found time to adopt a resolution on the pressing issue of "the benefits of practicing yoga."
On December 11, 2014 the Assembly adopted a resolution entitled "International Day of Yoga." Terror-sponsor Qatar praised "the health benefits of that practice." Human rights abuser Sri Lanka was thrilled with yoga's "holistic effect" and also warned about western states "diluting" "the intrinsic beauty of yoga".
Ironically, the resolution was hailed as promoting "clarity of vision and action." The 2014 UN General Assembly will not be adopting one resolution warning about clear human rights violations, for instance, in China, Russia, or Saudi Arabia.
Latest UN priority: resolution on "the benefits of practicing yoga" Development
Stéphane Dujarric, UN spokesperson
"A routine UN press briefing this week was marred by an awkward exchange between New York Post correspondent Benny Avni and the UN Secretary-General's spokesman, Stéphane Dujarric, over calls by an official of UNRWA, the UN agency catering to the descendants of Palestinian refugees, for a boycott of Israeli newspaper The Jerusalem Post.
UNRWA spokesman Chris Gunness went into a rage on Twitter last week after the JPost published an oped on December 4 by Bassam Eid, a Palestinian human rights activist who was raised in an UNRWA refugee camp, in which he slammed the agency for perpetuating the refugee status of Palestinians in the West Bank and Gaza Strip, as well as neighboring countries. Eid made similar points in an interview with The Algemeiner's Senior Editor, Ben Cohen, that was published on the same day.
"Ultra-right @Jerusalem_Post carries anti-UNRWA garbage boycotting me ie no quote. Ask @stevelinde Boycott the JPost! Don't read their lies," Gunness tweeted, apparently unaware that the article in question was an opinion piece, rather a news item, and therefore did not require a balancing quote.
At Tuesday's press briefing, Avni asked Dujarric whether there would be any disciplinary action taken against Gunness as a result of his boycott call. Dujarric responded that Gunness 'was not calling for a boycott of this specific media outlet, but instead was making his objections quite clear on a single article that was found to be problematic.'"
UN takes heat for UNRWA Official's Call for 'Boycott' of Jerusalem Post Article
"Resolution Condemning the use of civilians as human shields by Hamas" H. Con. Res. 107 Document
Rising above personal attacks, the time has come to examine UNRWA policy Article
Senior Hamas leader Moussa Abu Marzouk
"Hamas said Thursday that Robert Serry, UN coordinator for the Middle East peace process, had held talks with its representatives at the UN headquarters in Gaza City, reported the Associated Press later in the day.
The Hamas statement said that its delegation was headed by Moussa Abu Marzouk, its number two man, and Ghazi Hammad...
UN officials would only say that Serry meets with Hamas officials when needed."
Hamas's #2 Man Meets UN's Serry in Gaza Article
The International Criminal Court in The Hague
"The celebrations by Mahmoud Abbas and the Palestinian leadership during the course of the 13th Assembly of States Parties to the International Criminal Court (ICC), in New York, on December 8, 2014, at their being invited to participate as an observer in the deliberations of the ICC Assembly of states parties1, would appear to indicate a major element of ignorance and naiveté on the part of the Palestinian leadership, as to the significance of such participation.
Failing such naiveté and ignorance, their statements are nothing more than a deliberate attempt to mislead the international public - and especially the Israeli leadership and public - into thinking that observer participation in an administrative body that regulates the management of the court, could in any way advance the oft-declared Palestinian hopes and aims to become a state party to the court and to attempt to institute claims against Israeli officials."
Palestinian Participation in the "Assembly of States Parties to the ICC Statute" Article
The Al-Nusra Front using the UN vehicle for the attack
"Syrian opposition sources say al-Qaeda-linked Syrian rebels, known as the Al-Nusra Front, have taken over areas along the Israeli-Syrian border and have recently been spotted using UN cars to conduct terror operations."
al-Qaeda-linked Syrian rebels are using UN cars to conduct terror operations Article
File Photo: Kurds hanged in Iran
"The United Nations wants us to remember human rights 365 days a year, in fact. One group that needs attention: 29 Kurds on a hunger strike in Iran's Orumiyeh prison.
"Today, December 10, marks United Nations Human Rights Day, first proclaimed in 1950 'to bring to the attention "of the peoples of the world" the Universal Declaration of Human Rights as the common standard of achievement for all peoples and all nations.'
"Today also marks the 20th day of a hunger strike by 29 political prisoners in Iran's Orumiyeh Central Prison, which mainly houses Kurdish political prisoners. Fellow Kurdish prisoners of conscience in other cities across Iran have followed suit.
"The prisoners of Ward 12 at Orumiyeh, in northwest Iran near the Turkish and Iraqi borders, 'started their hunger strike protesting felons and criminals in their ward,' according to HRANA, a human rights activist web site. 'The political prisoners on hunger strike have also demanded that another 27 prisoners who have been dispersed in other wards in the same prison be transferred to Ward 12.'
"Some 50 inmates with drug addiction problems or violent pasts have been mixed in with the political prisoners, according to Kurdish-language news agencies. This unexpected appears to be the result of a recent order by the Iranian Intelligence Ministry, and there are strong indications that there is a plan by various security and intelligence apparatus to shut down sections of various prisons dedicated to prisoners of conscience..."
Remembering Iran's Imprisoned Kurds on UN Human Rights Day Document
Sixty-six years ago was the high water mark of global disapproval of xenophobia, and racial and religious discrimination. On December 10, 1948, the United Nations General Assembly adopted the Universal Declaration of Human Rights and then gave Eleanor Roosevelt a standing ovation for her leading role. Today, this statement of principle would never pass.
Racial and religious discrimination is the trademark of the U.N. itself.
Let's look back at the year 2014.
At least another 75,000 people were butchered in Syria. There were violent crackdowns in Hong Kong, bloody takeovers in Ukraine, subjugation of women in Saudi Arabia, brutal lawlessness in Yemen, Libya, Nigeria, Mexico – and so on.
But at the United Nations, 2014 wraps up with the adoption of twenty times more resolutions by the General Assembly condemning the state of Israel for violating human rights than any other nation on earth.
There is not one General Assembly resolution worried about human rights in China or Russia or Saudi Arabia or Yemen or Libya or Nigeria or Mexico – and so forth.
The General Assembly will even adopt one resolution critical of Syria but two resolutions demanding Israel immediately return the Golan Heights to Syria – the place where lucky Syrians and UN peacekeepers dash to Israel for protection.
The demonization of Israel, and the inequality of the self-determination of the Jewish people, by way of the United Nations have one painfully obvious purpose: the end of the Jewish state. Eleanor Roosevelt would have called it a gross violation of the very spirit of the Universal Declaration of Human Rights.
If you walk into the newly-renovated UN, which opened its doors in the fall after a $2 billion dollar spending spree (a quarter of which came from American taxpayers), the first stop on the public tour straight off the elevator is an exhibit on Palestinian rights.
It's a fictional narrative of "11 million Palestinians" and the story of generation after generation of "refugees" from successive wars that spontaneously "broke out." The only "contraventions of international law" are by Israel. Palestinians have justifiable "uprisings." Israelis have "extremists." Arabs mount "peace initiatives." Israelis mount "military operations."
The kicker: Palestinian history miraculously mirrors Jewish history and begins in 1948 with an "exodus" after "the catastrophe" of the establishment of Israel.
If our nation is seriously worried about incitement to racial and religious intolerance, it is time to get serious about incitement at the UN.
On November 24, 2014, the U.N. held its annual International Day of Solidarity with the Palestinian People. It marked the anniversary of the 1948 General Assembly resolution partitioning Palestine into an Arab and a Jewish state by flying only the flag of the "State of Palestine" and banning the flag of Israel.
For the past two weeks, the public entrance to U.N. headquarters has been decorated with another exhibit. "The Long Journey" purports to tell the history of the Palestinian "exodus" that began in 1948 – not 1967. Photos show Palestinians studying, eating, praying, training, cooking, shopping, dancing, sewing, and playing. Never killing. Never terrorizing. Never making war. Never spouting anti-Semitism. But suffering with "ingenuity, resilience and steadfastness" from wanton Israeli aggression.
At the U.N. in Geneva there has been another public exhibit gracing the U.N.'s Palais des Nations. It is entitled "La Nakba: Exode et Expulsion des Palestiniens en 1948" – meaning "The Nakba: Exodus and Expulsion of the Palestinians in 1948." The exhibit, which was a "cultural activity" requested by "Palestine," required UN approval and facilitation. According to formal guidelines, it must have been approved at the highest levels – the Director-General, Michael Møller of Denmark.
It includes the following astounding statements: "The Palestinians failed to see why they should be made to pay for the Holocaust...Acts of terrorism...by the Zionists led to the flight and expulsion of the native Arab Palestinian population....Zionist representatives...planned and implemented the ethnic purge." "The partition resolution violates fundamental principles of the UN Charter."
The organizers shamelessly responded in a written handout to the rhetorical question: "Why did we create this exhibition on the Nakba?" Their answer: to reeducate those misinformed by "German guilt" and "the mass media" in order to appreciate that in 1948, Palestinians were "robbed of their homeland and their property."
Hiding in plain sight at the UN is the reason for the lack of peace between Israelis and Arabs – and it has nothing to do with 1967 and "occupation." For Palestinians and Arabs across the Middle East, Israel is one big settlement.
As Palestinian representative Riyad Mansour openly told his U.N. audience on November 24, 2014: "Our people are suffering immense and growing hardships, all stemming from the grave injustice done to them in Al-Nakba of 1948 and thereafter."
The month of November saw six full days at U.N. headquarters dedicated to dehumanizing Israelis, led by speakers from UNRWA, the Palestinian Authority and Iran. Israel was guilty of "an onslaught," "ethnic cleansing," "an inhumane blockade," "torture," "massacring civilians with a vengeance," "virulent racism," "barbarism," "a policy of terrorism," "genocide," "apartheid," "savagery," "terror rampages," "horrific abuse," "supporting Al Qaeda," "heinous crimes," "beating and torturing juveniles," and "crimes against humanity."
That was in addition, to repeating "Zionism is racism" and analogizing Israelis to Nazis. Lebanon, for instance, said: "From 1948 until today, many Palestinian young girls and boys are just as determined as Anne Frank to conquer their fear of the occupier..."
How many more stabbings, rapes, and killings of Jews around the globe will it take to end American tolerance for incitement to racial and religious intolerance at the United Nations?
Eleanor Roosevelt would have had an answer.
UN marks Human Rights Day by promoting violation of human rights Article
"On December 10, 2014, the Al-Furat province of the Islamic State (ISIS) (straddling parts of eastern Syria and western Iraq), announced that it had executed a man convicted of homosexuality.
The announcement read: "Following the example of Muslims Caliph Abu Bakr Al-Siddiq (ruled 632-634), the Islamic court in Al-Furat province sentenced a man who performed acts of the people of Lot [i.e.,homosexual acts] to be cast off the highest place in the town and then stoned to death. Allah's command [is valid] in both the past and the future."
The accompanying photos show the man being cast off the rooftop by a band of masked and armed ISIS fighters, followed by his stoning."
ISIS Executes Homosexual By Throwing Him Off A Rooftop And Then Stoning Him Document
Arak heavy water reactor
"Iran is being accused of illicitly stepping up purchases for its heavy water reactor, which if completed will produce enough plutonium for several nuclear weapons a year, UN diplomats said Tuesday. The allegation against Iran by an unnamed country, if true, would suggest that Tehran is rejecting the U.S. reconfiguration into a light-water reactor. The accusation was contained in a report to the Security Council sanctions committee prepared by experts monitoring sanctions against Iran..."
UN diplomats: Report says Iran buying for reactor Article
Margot Ellis, UNRWA Deputy Commissioner-General
"Addressing a conference of states pledging voluntary donations to UNRWA, the agency's deputy commissioner-general Margot Ellis, a former official with the United States Agency for International Development (USAID), claimed that "This summer, around 2,200 people were killed in 50 days; over 500 were children, most under age twelve. 46 of those killed were in our shelters at the time."
As well as failing to distinguish civilians from terrorists, Ellis omitted to mention that many UNRWA facilities, including schools, were used as weapons storage depots by Hamas.
The number cited by Ellis contradicts the assessment of the UN's own Office for the Coordination of Humanitarian Affairs (OCHA), which concluded that the "Palestinian fatality toll is 2,131, of whom 1,473 have been identified as civilians."
While OCHA records civilians as composing just under 70 percent of the total Palestinian death toll, other organizations place the figure even lower. Recent research by the Meir Amit Center, an Israeli strategic think-tank, estimates that as many as 52 percent of fatalities were terrorists. The Centers' figures are based on fatality lists collated by OCHA.
Nor do the UNRWA figures account for Palestinians killed by Hamas rockets aimed at Israel that landed in Gaza, either because of operational incompetence or a deliberate attempt by Hamas to increase the number of casualties. At the end of July, for example, dozens of Palestinians were killed and wounded at the Shifa Hospital in northern Gaza, after a Hamas Fajr-5 rocket aimed at central Israel was fired from a playground outside the hospital and exploded on the site."
Senior UNRWA Official Again Distorts Palestinian Fatality Figures from Gaza War Article
Paraguay, newly-elected Vice-Chair of the UN "Human Rights" Council, was first elected to the Council in October. Its election was part of what was called a "shocking" upset over the fully-free democracy of Costa Rica.
Notwithstanding its human rights record, Paraguay got 139 votes - that's 72 % of General Assembly members.
Just prior to the vote, Paraguay distributed a gift to every UN member state in the UN General Assembly Hall. It included a bag of Paraguayan baked goodies and a jar of guava jam.
Vice-Chair of the UN's top human rights body comes cheap.
The price of doing business in the UN "human rights" world Article
The current headquarters of the ICC in The Hague
"The President of the Assembly of State Parties of the Rome Statute of the ICC cautiously noted that this step was not indicative of any action the court's judicial body might later take on the matter, when she spoke at the start of Monday's meeting about the invitation to observer nations to attend the gathering.
"The assembly takes the following decisions on procedure independently and without prejudice to decisions taken for other purposes, including the decisions of any other organization or any organ of the court concerning legal matters before it," she said.
"At the same time I recall that Rule 94 of the rules of procedures states that at the beginning of every session of the assembly the president, subject to the adoption of the assembly, may invite states which are not parties to the Rome Statute and which have not signed the final act nor the statute to attend the assembly proceedings," she said.
She then listed those invited to attend the meeting, including the "state of Palestine." ICC participants were invited to object if they wanted to, but none did."
Palestinians "invited to attend" the ICC Assembly of the State Parties Article
Joachim Rücker, Ambassador of Germany and UN Human Rights Council president for 2015
Germany was elected as President of the UN Human Rights Council for 2015. Taking the helm will be German Ambassador Joachim Rücker. After his election, Rücker praised the notoriously anti-Israel Council for "having a serious impact on the world stage." Although he also said that "Israel should be treated like any other state," Germany's own voting record on the Council is part of the problem.
In 2014 the Council passed 6 resolutions slandering Israel and Germany supported four of them, while merely abstaining on another two.
Germany, for example, voted in favor of the following:
"[T]he Israeli settlements in the Occupied Palestinian Territory, including East Jerusalem, and in the occupied Syrian Golan are illegal and an obstacle to peace and economic and social development" (Resolution 25/28. "Israeli settlements in the Occupied Palestinian Territory, including East Jerusalem, and in the occupied Syrian Golan", March 28, 2014)
"[T]he construction of the wall by Israel, the occupying Power, in the Occupied Palestinian Territory, including East Jerusalem, along with measures previously taken, severely impedes the right of the Palestinian people to self-determination" (Resolution 25/27. "Right of the Palestinian people to self-determination", March 28, 2014)
"The Human Rights Council...expressing deep concern also about the ill-treatment and harassment of any Palestinian prisoner and all reports of torture...Condemns the excessive use of force by the Israeli occupying forces against Palestinian civilians, particularly in the Gaza Strip...Also calls upon Israel to end any harassment, intimidation and reprisals against human rights defenders...Expresses grave concern at: (a) The restrictions imposed by Israel that impede access of Christian and Muslim worshipers to holy sites in the Occupied Palestinian Territory, including East Jerusalem" (Resolution 25/29. "Human rights situation in Occupied Palestinian Territory, including East Jerusalem", March 28, 2014)...
Germany takes the helm of notorious anti-Jewish UN Human Rights Council Article
UN Human Rights Council, Geneva, Switzerland
On December 8, 2014 the UN Human Rights Council elected the five members of its executive committee, or "bureau," for 2015. Representing each of the UN's five regional groups on the bureau will be Ambassador Joachim Ruecker, Permanent Representative of Germany as President, and Filloreta Kodra of Albania, Juan Esteban Aguirre Martinez of Paraguay, Mukhtar Tileuberdi of Kazakhstan and Mothusi Bruce Rabasha Palai of Botswana as Vice Presidents. Ambassador Rabasha Palai was also elected to fill the post of Rapporteur. Only two of the five countries that will lead the Council in 2015, Germany and Botswana, are ranked "fully free" by the Freedom House index.
Here is part of the human rights records of vice-presidents Albania, Kazakhstan and Paraguay as set out in the latest US State Department reports:
"Security forces committed human rights abuses. The most significant human rights problems were: pervasive corruption in all branches of government, and particularly within the judicial system; the stalling of the reform agenda, in particular the fight against corruption, as the political parties focused on the June elections; and domestic violence and discrimination against women. Other human rights problems included police beating and other mistreatment of suspects during detention and interrogation, sometimes to elicit confessions; substandard prison conditions; an inefficient judiciary subject to political pressure and corruption; and child abuse...Marginalization and abuse of the Romani and Balkan Egyptian communities were serious problems...Discrimination on the basis of sexual orientation and gender identity was a problem...Incidents of societal killings, including both "blood feud" and revenge killings, occurred during the year...Victims rarely reported spousal abuse, and officials did not prosecute spousal rape. The concept of spousal rape was not well established, and authorities and the public often did not consider it a crime..."
"The most significant human rights problems were severe limits on citizens' rights to change their government; restrictions on freedom of speech, press, assembly, religion, and association; and lack of an independent judiciary and due process, especially in dealing with pervasive corruption and abuses by law enforcement and judicial officials... Other reported abuses included: arbitrary or unlawful killings; military hazing that led to deaths; detainee and prisoner torture and other abuse; harsh and sometimes life threatening prison conditions; arbitrary arrest and detention; infringements on citizens' privacy rights; prohibitive political party registration requirements; restrictions on the activities of nongovernmental organizations (NGOs)...
Violence against women, including domestic violence, was a problem...NGOs reported that women often withdrew their complaints because of economic insecurity...When domestic violence cases came to trial, the charge was most often light battery... the practice of kidnapping women and girls for forced marriage continued in some remote areas...A person who voluntarily releases an abductee is absolved of criminal responsibility if in this action he/she did not commit another offense. Because of this law, a typical bride kidnapper is not necessarily held criminally responsible for the act. Cases were typically not pursued...Law enforcement agencies often advised abductees to sort their situation out themselves... [M]aking a complaint to the police could be a very bureaucratic process and often subjected families and victims to humiliation...Sexual harassment remained a problem."
In Paraguay
"Security forces committed human rights abuses. The principal human rights problems were impunity in the judicial sector, together with lengthy pretrial detention and trial delays, harsh and at times life-threatening prison conditions, and police involvement in criminal activities, including unlawful killings by persons associated with the security forces. Other human rights problems included the killing and intimidation of journalists by organized-crime groups, corruption, discrimination, and violence in the society and in government against women and indigenous persons, persons with disabilities, and lesbian, gay, bisexual, and transgender (LGBT) persons, and trafficking in persons. Problems with child labor and violations of worker rights occurred often...[R]ape continued to be a significant and pervasive problem, including reports of minors who were drugged and gang raped...Domestic violence was common, and thousands of women received treatment for injuries sustained in domestic altercations."
Human rights abusers take top spots on the executive of UN "Human Rights" Council Development


text:
Надежда Драгова (; , Раднево) — болгарский филолог, писатель, драматург и культуролог, старшая научная сотрудница по балканистике, специалист литературы Возрождения, профессор.

Биография
Родилась 18 февраля 1931 года в городе Раднево. В 1952 году окончила Софийский университет Святого Климента Охридского, получив специальность «Болгарская филология». В 1971 стала одним из учредителей Шуменского университета «Епископ Константин Преславский». С 1988 по 1992 год работала научным руководителем Научного центра «Преславская книжная школа». Работала ассистенткой академика Петра Динекова в области фольклористики, староболгарской литературы и болгарской литературы эпохи Возрождения.

Автор многочисленных пьес. Как драматург больше известна в творческом тандеме со своим мужем Пырваном Стефановым. Вместе они написали пьесы: «Бог Перун» (1963, известная также под названием «Одиннадцатая заповедь»), «Между двумя выстрелами» (1967), «Хлеб наш насущный», «Мир родился из матери» и «На войне как на войне» (1972). Написала драму «Уголь».

Библиография

Отдельные книги
 1961 — «Знай свой род и езику»
 1962 — «Българкето още комиткето»
 1963 — «Пробуждане»
 1963 — «И го нарекоха Паисий»
 1965 — «Кой е създал нашитое буквы»
 1966 — «Климент Охридски. Разказ за него и враговете му»
 1992 — «Балканският контекст на старобългарската писмена култура (VIII–XII век)»
 2000 — «Отец Паисий — Патриарх на Българското възраждане»
 2005 — «Старобългарската култура»

В соавторстве
 2014 — «Култура, история, поезия. Надежда Драгова и Първан Стефанов в българската култура и наука. Сборник с изследвания»

Примечания

Ссылки
 Тошева, Кристина. Енциклопедия на българския театър: актьори, режисьори, драматурзи, сценографи, композитори, педагози, хореографи, критици, театри, институции, печат. Издателство "Труд", София, 2008 г., стр. 144
 ЗНАМ.bg - Българският портал на знанието
 Надежда Драгова

Писатели Болгарии
Филологи Болгарии
Преподаватели Шуменского университета

redpajama_set_name: RedPajamaWikipedia


text:
Trood

      Отчеты
      События

  <router-outlet></router-outlet>

  Сводка по ритейлу
  Сводка по производству
  Сводка по дистрибуция

redpajama_set_name: RedPajamaGithub


Plantpedia is here to be an online reference guide.
I have a strong interest in all areas of horticulture (and now have a garden centre based in Tuakau River Road Nursery) and wanted to build a site that I personally would use and find helpful.
I aim for Plantpedia to have factual and trust worthy information relative for New Zealanders and to also have interesting and inspiring content.
It is an on going project so new information and plants will constantly be added.
Any questions or queries please get in touch.
This is me in the vegetable garden, photo taken by Mr 4.


We had an excellent pool day today–we started our day at Mesa, singing some fun morning songs, and then headed to the pool, where we sunscreened and hopped into the water! We played all morning on the diving board and slide, and enjoyed the cool water and warm sun! After lunch, we re-sunscreened, drank a lot of water, and did some nifty poolside crafts, including lanyards, friendship bracelets, beaded jewelry, and spongebugs. It was fun to see the spongebugs in the pool! At the end of the day, we all changed into dry clothes, had some delicious clementines for snack, and sang some quieter songs to finish our day. Then, we hopped on the bus and headed home! Tomorrow, we're heading up to our new camp property–it should be a great time!


text:
package com.configx.client.config;

import org.springframework.beans.BeansException;
import org.springframework.beans.factory.config.BeanDefinition;
import org.springframework.beans.factory.config.BeanFactoryPostProcessor;
import org.springframework.beans.factory.config.ConfigurableListableBeanFactory;
import org.springframework.core.annotation.AnnotationUtils;
import org.springframework.util.ReflectionUtils;
import org.springframework.util.ReflectionUtils.MethodCallback;

import java.lang.annotation.Annotation;
import java.lang.reflect.Method;
import java.util.HashMap;
import java.util.Map;
import java.util.concurrent.atomic.AtomicReference;

/**
 * Utility class to memorize {@code @Bean} definition meta data during initialization of
 * the bean factory.
 *
 * @author Zhirong Zou
 */
public class ConfigurationBeanFactoryMetaData implements BeanFactoryPostProcessor {

    private ConfigurableListableBeanFactory beanFactory;

    private Map<String, MetaData> beans = new HashMap<String, MetaData>();

    @Override
    public void postProcessBeanFactory(ConfigurableListableBeanFactory beanFactory) throws BeansException {
        this.beanFactory = beanFactory;
        for (String name : beanFactory.getBeanDefinitionNames()) {
            BeanDefinition definition = beanFactory.getBeanDefinition(name);
            String method = definition.getFactoryMethodName();
            String bean = definition.getFactoryBeanName();
            if (method != null && bean != null) {
                this.beans.put(name, new MetaData(bean, method));
            }
        }
    }

    public <A extends Annotation> Map<String, Object> getBeansWithFactoryAnnotation(Class<A> type) {
        Map<String, Object> result = new HashMap<String, Object>();
        for (String name : this.beans.keySet()) {
            if (findFactoryAnnotation(name, type) != null) {
                result.put(name, this.beanFactory.getBean(name));
            }
        }
        return result;
    }

    public <A extends Annotation> A findFactoryAnnotation(String beanName, Class<A> type) {
        Method method = findFactoryMethod(beanName);
        return (method == null ? null : AnnotationUtils.findAnnotation(method, type));
    }

    private Method findFactoryMethod(String beanName) {
        if (!this.beans.containsKey(beanName)) {
            return null;
        }
        final AtomicReference<Method> found = new AtomicReference<Method>(null);
        MetaData meta = this.beans.get(beanName);
        final String factory = meta.getMethod();
        Class<?> type = this.beanFactory.getType(meta.getBean());
        ReflectionUtils.doWithMethods(type, new MethodCallback() {
            @Override
            public void doWith(Method method) throws IllegalArgumentException, IllegalAccessException {
                if (method.getName().equals(factory)) {
                    found.compareAndSet(null, method);
                }
            }
        });
        return found.get();
    }

    private static class MetaData {

        private String bean;

        private String method;

        MetaData(String bean, String method) {
            this.bean = bean;
            this.method = method;
        }

        public String getBean() {
            return this.bean;
        }

        public String getMethod() {
            return this.method;
        }

    }

}


2.2 Genetic counsellors with certification from ABGC or CAGC (USA or Canada) The training of genetic counsellors in USA and Canada is similar to the 2 year clinical masters degree in Australasia.... 4) To become certified as a genetic counselor one must have an undergraduate degree, and then obtain a Master's degree in genetic counseling from an accredited program in the US and Canada.
4) To become certified as a genetic counselor one must have an undergraduate degree, and then obtain a Master's degree in genetic counseling from an accredited program in the US and Canada.... 2.2 Genetic counsellors with certification from ABGC or CAGC (USA or Canada) The training of genetic counsellors in USA and Canada is similar to the 2 year clinical masters degree in Australasia.
13/07/2018 · Graduate programs in genetic counseling will want to see practical experience in the field of counseling or genetics to go with your strong science grades. Look for opportunities to volunteer at clinics and shadow current …... Genetic counselors need to complete a master's degree in genetic counseling. Coursework typically includes clinical genetics, population genetics, cytogenetics, and molecular genetics, coupled with psychosocial theory, ethics, and counseling techniques. Clinical placement in approved medical genetics centers is an integral part of the degree requirement.
Genetic counselors work with patients to assess the risks of hereditary disease and medical conditions. A counselor analyzes and interprets data from medical histories and testing to identify the risk of a genetic …... A genetic counsellor is a health care professional. He or she typically has a Master's degree in genetic counselling, with specialized training in medical genetics and counselling.
Counselors typically get their start as college undergrads majoring in a science field like biology, Sturm says, before gaining a master's degree in human genetics or genetic counseling. The final step is to become board certified as a genetic counselor.
The American Board of Genetic Counseling (ABGC) recognizes programs in the United States and Canada that demonstrate that their graduates have achieved the knowledge and skills necessary to provide competent genetic counseling services.
The National Society of Genetic Counselors, comprised of members primarily from the United States and Canada, contains a search engine to search genetic counsellors all over the world. The society aims to promote genetic counselling as a career and to provide genetic counselors with opportunities for growth.
Genetic counsellor usually have an undergraduate degree in science, nursing, social work, teaching or psychology followed by a two years masters course in genetic counselling. Once qualified and practicing in the field, genetic counsellors usually undergo an accreditation process to become certified.


text:
Blackmagic Video Assist is the best monitor/recorder of NAB Week 2020
Sean Berry
Update: The Blackmagic Video Assist 12G 7″ is a recipient of our Editors' Choice award, which recognizes exceptional video production equipment, software and services. Click here to see a complete list of current Editors' Choice award winners in the audio and video recorders category.
Congratulations to Blackmagic Design! The Video Assist 12G is Videomaker's best monitor/recorder pick for NAB Week 2020.
The monitors will have a brighter 2,500 nit screen than other Video Assist models. Both 7" and 5" models feature touchscreens and Blackmagic's BMD OS. Additionally, the new monitor/recorders will add a few new things to the Video Assist line to improve the line for the better. It comes in two sizes, 7" and 5", and could be brighter than previous Video Assist models. This is why it's our pick for the best monitor/recorder of NAB Week 2020.
Brighter screen
As we said above, the Video Assist 12G screen will sport 2,500 nits of brightness. At the same time, it will use the P3 wide color gamut. This goes without saying that the new models will be easier to see. In the field, the 12G monitor-recorder will be easier to see in daylight. It will also be better for HDR monitoring with its P3 wide color gamut.
Blackmagic Design Video Assist 12G
Added features
The Video Assist 12G has waveform, RGB parade, vectorscope, and histogram tools. These will be great for mirrorless cameras that don't have these integrated. Additionally, the monitor/recorder uses a picture-in-picture feature that allows you to preview your shot.
Also, LUTs are supported. They can be applied either temporarily for monitoring or they can be burned into files.
The monitors can record single or dual hot-swappable SD card slots in a variety of 10-bit 4:2:2 ProRes or DNx formats. The 5" records to a single SD card slot and the 7" records dual hot-swappable SD card slots. The framerates run up to 2160p60. It's also possible to record directly to a USB flash drive like the Samsung T5 over a USB-C connector. With a USB splitter, it's possible to lay off two recordings simultaneously through the USB port
Blackmagic's BRAW codec is also supported when recording from the Panasonic EVA1 and Canon C300 MkII cameras.
The Assist 12G can record to a single or dual hot-swappable SD card slots depending on the modle
Battery power
The Video Assist 12G uses Sony's L-type batteries. This should extend the battery life over past models. There are two hot-swappable slots. The monitor will drain the least-charged battery first.
Every monitor has three 1/4"-20 sockets on top and bottom for mounting.
The Video Assist 12G will be out in October. The 7" and 5" models will sell for $955 and $795.
SOURCEBlackmagic Design
Sean Berry is Videomaker's Managing Editor.
The RØDECaster Pro II just got advanced sub-mixing
TASCAM announces Portacapture X6 audio recorder
Irix launches new Matte Box IQ
Laowa launches Proteus 2x anamorphic lens series
Alec Baldwin to be charged with involuntary manslaughter
Sony will release a new 300 mm G Master prime lens