Saturday, March 14, 2009

At the Saskatchewan Association of Rural Municipalities (SARM) conference, a resolution was passed that encourages the Government of Saskatchewan, Canada to place a moratorium on specialty livestock farms raising wild boar. All wild boars that have escaped to roam wild should be killed, according to the resolution.

Agriculture Minister Bob Bjornerud endorses a ban on wild boar farming. The wild boar population is expanding exponentially. There are over 2,000 feral Sus scrofa swine roaming the prairies. Two litters of approximately 12 piglets are sired by each wild boar sow every year. The Saskatchewan Wildlife Federation (SWF) likewise passed a similar resolution at their 79th annual convention to urge the Saskatchewan Government to declare the wild boar as a nuisance species which can be killed on sight.

3% of farmed “wild” boars escape. Cells of wild boars are ravenous creatures killing and eating everything in their path. Horses, cows, and other livestock run from wild boars, breaking through fences in the process.

Ostriches, emus, llamas, alpacas, reindeer, wild boar, and fallow deer were amongst the animals introduced to farms in Saskatchewan during the agricultural diversification program in the late 1970s. Production of wild boars was promoted throughout the 1980s.

According to the Saskatchewan Agriculture and Food 2001 statistics, there were 150 wild boar producers raising approximately 15,000 and 20,000 head. Of these there were about 2,700 sows. On the 2006 Census of Agriculture, 401 farms reported 4,926 boars.

The boar’s red meat is an export commodity to Europe and Asia. The live breeding stock are also sold to trophy hunt ranches. Full blooded wild boar and hybrid crosses are raised.

Tuesday, January 15, 2008

The Bush administration officially notified Congress Monday of its intention to sell sophisticated precision-guided bombs to Saudi Arabia. The action, coinciding with President Bush’s visit to Saudi Arabia, is part of a broader U.S. effort to bolster Gulf allies in the face of a more assertive Iran. VOA’s David Gollust reports from the State Department.

The Bush administration has already briefed Congress on its arms sales plans for Saudi Arabia. Monday’s announcement sets in motion a 30-day period in which the House and Senate can block the plan with a joint resolution – an action that appears highly unlikely.

Under the proposed deal, worth more than $120 million, the United States would provide Saudi Arabia with 900 kits and associated equipment to convert conventional gravity bombs into GPS-guided smart-bombs, known as JDAMs.

The weapons are a mainstay of the U.S. military arsenal and their accuracy would vastly enhance the capability of the Saudi Air Force, which has top-of-the-line U.S.-made fighter-bomber aircraft.

The sale is part of a broader $20-billion arms package for Saudi Arabia and other Gulf states announced by Secretary of State Condoleezza Rice and Defense Secretary Robert Gates last August on a mission to the Gulf, aimed at shoring up U.S. allies concerned about Iranian influence in the region.

Several elements of the broader package including sales of Patriot anti-missile systems to Kuwait and the United Arab Emirates, and upgrades for Saudi Arabia’s AWACS airborne command and control planes, have already gotten congressional assent. Officials here say they also expect the Saudi J-DAMS sale to proceed despite concerns expressed by some congressional supporters of Israel.

At the time the Gulf weapons sales package was announced last year, the Bush administration also committed to a 10-year, $30-billion arms package for Israel, representing a 25 per cent increase in annual U.S. arms aid to that country.

Briefing reporters, State Department Spokesman Sean McCormack said the administration has assured Congress it would do nothing to upset Israel’s military edge over potential enemies in the region.

“We’ve spent a lot of time assuring that we abide by our commitments to a qualitative military edge for Israel,” said Sean McCormack. “This is something that President Reagan first talked about and it’s been reiterated and reconfirmed by each successive president after that. We’re committed to maintaining that qualitative military edge for Israel.”

Israel itself has not protested the pending sale. Israeli officials have said they anticipate being provided with a new-generation U.S. smart bomb more capable than J-DAMS, which have been in service for more than a decade.

A spokesman for House Foreign Affairs Committee Chairman Tom Lantos, a prominent advocate for Israel in Congress, said he does not intend to push a resolution of disapproval.

However one House member, New York Democrat Anthony Weiner, said he would introduce such a measure and already has more than 30 co-sponsors.

Critics of the package have faulted Saudi Arabia’s record in combating terrorism and advancing political reform. Under questioning here, Spokesman McCormack said the Saudi government has made “quantum leaps” in action against terrorist cells and financing in recent years and has begun the process of reform, though not necessarily at a pace that would please some critics.

Two-thirds majorities of the members in both houses would be required to block the sale and officials here say chances for that appear nil.

Saturday, May 17, 2008

Construction workers and next of kin of deceased workers filed a lawsuit in Tokyo, Japan Friday seeking damages of approximately 6.6 billion yen (about US$64 million) from the government and manufacturers related to illnesses stemming from exposure to asbestos. 178 plaintiffs; including construction workers and family members filed the suit in Tokyo District Court against 46 building manufacturers and the Government of Japan.

According to the Mainichi Daily News, the class action suit is the first that has been filed in Japan related to health damages caused by asbestos exposure at construction sites. The plaintiffs hail from the Japanese prefectures of Tokyo, Saitama and Chiba.

The plaintiffs claim that the government and manufacturers knew of the dangers of asbestos inhalation but failed to take proper precautions, including ceasing to promote asbestos as a cheap fire retardant and banning production of the material.

They state that after inhaling asbestos in the workplace, 172 people have developed lung cancer or mesothelioma, and that almost half of those afflicted are now dead. Plaintiffs argue that the government and health ministry did not act quickly enough after international organizations issued warnings in 1972 that asbestos could be a carcinogen.

Plaintiffs also place blame with the Ministry of Economy, Trade and Industry for sanctioning the use of asbestos under Japanese Industrial Standards, and with the Ministry of Land, Infrastructure and Transport for approving the use of materials comprised of asbestos and other substances under Japan’s Building Standards Law.

“We will do our utmost until we win the suit,” said Kazuo Miyajima, 78, who heads the group of plaintiffs. Lawyers for the plaintiffs released a statement saying: “We seek complete relief for the victims by clarifying the liability of the state and the manufacturers.”

Approximately 40 construction workers from Kanagawa Prefecture plan to file a similar lawsuit in June in Yokohama District Court.

After a 2005 revelation that residents who lived near a factory in Amagasaki, Hyogo Prefecture developed diseases related to asbestos, the government implemented a law in 2006 which provides monetary assistance to asbestos victims and relatives of deceased family members. The plaintiffs argue that the amount of financial assistance given to families and victims of asbestos-related diseases is not sufficient.

Asbestos has been used in Japan as a fire retardant, for sound absorption, and for insulation. It was mixed in concrete and water and sprayed on walls and ceilings, but the practice of spraying asbestos in this manner was banned in Japan in 1975.

Saturday, August 25, 2007

The leading supplier of school uniforms in the United Kingdom, Lancashire-based manufacturer Trutex, has announced it is “seriously considering” including GPS tracking devices in future ranges of its uniform products after conducting an online survey of both parents and children.

“As a direct result of the survey, we are now seriously considering incorporating a [tracking] device into future ranges” said Trutex marketing director Clare Rix.

The survey questioned 809 parents and 444 children aged nine to 16. It showed that 44% of parents were worried about the safety of pre-teen children, and 59% wanted tracking devices installed in school apparel. 39% of children aged nine to 12 were prepared to wear clothing with tracking devices in them, while teenagers were notably less enthusiastic and more wary of what Trutex has admitted they see as a “big brother” concept.

However, Trutex has claimed the tracking devices would bring about worthwhile benefits, including being a valuable resource for parents who wanted to keep a close eye on where their children were at all times.

“As well as being a safety net for parents, there could be real benefits for schools who could keep a closer track on the whereabouts of their pupils, potentially reducing truancy levels” says Rix.

Each year, Trutex supplies 1 million blouses, 1.1 million shirts, 250,000 pairs of trousers, 20,000 blazers, 60,000 skirts and 110,000 pieces of knitwear to the UK.

It is not the first company to manufacture school uniforms with a central focus on child safety; last week Essex firm BladeRunner revealed it was selling stab-proof school blazers to parents concerned about violence against their children. The blazers were outfitted with Kevlar, a synthetic fibre used in body armour. It has already received orders internationally, including Australia.

If the Trutex tracking devices go ahead, it is unclear where in the uniform they will be located.

Thursday, September 26, 2019

This morning Jacques Chirac, who served as President of France for twelve years, died at home in Paris, France, surrounded by family. He was 86. The news came from his son-in-law, Frédéric Salat-Baroux, and came after a long period of health problems. He had not made public appearances since 2014, which his wife Bernadette said was due to memory problems.

Jacques Chirac was born in 1932 in Paris. He was a civil servant before becoming a career politician. From 1967 to 1995 he was a member of the French Parliament during which he twice served as prime minister, first under President Valéry Giscard d’Estaing in the seventies and again in the eighties under President François Mitterrand. Additionally, Chirac was mayor of Paris from 1977 to 1995.

In 1995, Chriac was elected to his first of two terms as President of France. During his presidency he ended mandatory military service and cut two years off the length of presidential terms, down to five years. He favored European integration and sought a more federal European Union. Chirac was also an outspoken opponent of the United States-led Iraq War in 2003.

Chirac was convicted of corruption, stemming from his years as mayor, in 2011. The charges were held back while he was president due to presidential immunity. He was given a two-year suspended sentence.

Both houses of the French Parliament held a minute of silence in Chirac’s honor today. Assembly president Richard Ferrand in relaying the news to parliament said, “Jacques Chirac is part of the history of France”. Former president Nicolas Sarkozy said of Chirac, “He incarnated a France that was true to its universal values and to its historic role”.

[edit]

Friday, May 19, 2006

This interview intends to provide some insight into OpenSync, an upcoming free unified data synchronization solution for free software desktops such as KDE, commonly used as part of the GNU/Linux operating system.

Hi Cornelius, Armin and Tobias. As you are now getting close to version 1.0 of OpenSync, which is expected to become the new synchronisation framework for KDE and other free desktops, we are quite interested in the merits it can provide for KDE users and for developers, as well as for the Open Source Community as a whole. So there’s one key-question before I move deeper into the details of OpenSync:

What does OpenSync accomplish, that no one did before?

Cornelius:

First of all it does its job of synchronizing data like addressbooks and calendars between desktop applications and mobile devices like PDAs and cell phones.

But the new thing about OpenSync is that it isn’t tied to a particular device or a specific platform. It provides an extensible and modular framework that is easy to adopt for application developers and people implementing support for syncing with mobile devices.

OpenSync is also independent of the desktop platform. It will be the common syncing backend for at least KDE and GNOME and other projects are likely to join. That means that the free desktop will have one common syncing solution. This is something really new.

How do the end-users profit from using synching solutions that interface with OpenSync as framework?

Cornelius:

First, the users will be able to actually synchronize all their data. By using one common framework there won’t be any “missing links”, where one application can sync one set of devices and another application a different one. With OpenSync all applications can sync all devices.

Second, the users will get a consistent and common user interface for syncing across all applications and devices. This will be much simpler to use than the current incoherent collection of syncing programs you need if you have more than the very basic needs.

How does OpenSync help developers with coding?

Cornelius:

It’s a very flexible and well-designed framework that makes it quite easy for developers to add support for new devices and new types of data. It’s also very easy to add support for OpenSync to applications.

The big achievement of OpenSync is that it hides all the gory details of syncing from the developers who work on applications and device support. That makes it possible for the developers to concentrate on their area of expertise without having to care what’s going on behind the scenes.

I have written quite a lot of synchronization code in the past. Trust me, it’s much better, if someone just takes care of it for you, and that’s what OpenSync does.

Tobias:

Another point to mention is the python wrapper for opensync, so you are not bound to C or C++, but can develop plugins in a high level scripting language.

Why should producers of portable devices get involved with your team?

Cornelius:

OpenSync will be the one common syncing solution for the free desktop. That means there is a single point of contact for device manufacturers who want to add support for their devices. That’s much more feasible than addressing all the different applications and solutions we had before. With OpenSync it hopefully will become interesting for manufacturers to officially support Linux for their devices.

Do you also plan to support applications of OpenSync in proprietary systems like OSX and Windows?

Cornelius:

OpenSync is designed to be cross-platform, so it is able to run on other systems like Windows. How well this works is always a question of people actually using and developing for this system. As far as I know there isn’t a real Windows community around OpenSync yet. But the technical foundation is there, so if there is somebody interested in working on a unified syncing solution on Windows, everybody is welcome to join the project.

What does your synchronisation framework do for KDE and for KitchenSync in particular?

Cornelius:

OpenSync replaces the KDE-specific synchronization frameworks we had before. Even in KDE we had several separate syncing implementations and with OpenSync we can get replace them with a common framework. We had a more generic syncing solution in KDE under development. This was quite similar from a design point of view to OpenSync, but it never got to the level of maturity we would have needed, because of lack of resources. As OpenSync fills this gap we are happy to be able to remove our old code and now concentrate on our core business.

What was your personal reason for getting involved with OpenSync?

Cornelius:

I wrote a lot of synchronization code in the past, which mainly came from the time where I was maintaining KOrganizer and working on KAddressBook. But this always was driven by necessity and not passion. I wanted to have all my calendar and contact data in one place, but my main objective was to work on the applications and user interfaces handling the data and not on the underlying code synchronizing the data.

So when the OpenSync project was created I was very interested. At GUADEC in Stuttgart I met with Armin, the maintainer of OpenSync, and we talked about integrating OpenSync with KDE. Everything seemed to fit together quite well, so at Linuxtag the same year we had another meeting with some more KDE people. In the end we agreed to go with OpenSync and a couple of weeks later we met again in Nuernberg for three days of hacking and created the KDE frontend for OpenSync. In retrospect it was a very pleasant and straightforward process to get where we are now.

Armin:

My reason to get involved (or better to start) OpenSync was my involvement with its predecessor Multisync. I am working as a system administrator for a small consulting company and so I saw some problems when trying to find a synchronization solution for Linux.

At that point I joined the Multisync project to implement some plugins that I thought would be nice to have. After some time I became the maintainer of the project. But I was unhappy with some technical aspects of the project, especially the tight coupling between the syncing logic and the GUI, its dependencies on GNOME libraries and its lack of flexibility.

Tobias:

Well, I have been a KDE PIM developer for several years now, so there was no way around getting in touch with synchronization and KitchenSync. Although I liked the idea of KitchenSync, I hated the code and the user interface […]. So when we discussed to switch to OpenSync and reimplementing the user interface, I volunteered immediately.

Can you tell us a bit about your further plans and ideas?

Cornelius:

The next thing will be the 1.0 release of OpenSync. We will release KitchenSync as frontend in parallel.

Armin:

There are of course a lot of things on my todo and my wishlist for opensync. For the near future the most important step is the 1.0 release, of course, where we still have some missing features in OpenSync as well as in the plugins.

One thing I would really like to see is a thunderbird plugin for OpenSync. I use thunderbird personally and would really like to keep my contacts up to date with my cellular, but I was not yet able to find the time to implement it.

Tobias:

One thing that would really rock in future versions of OpenSync is an automatic hardware detection mechanism, so when you plugin your Palm or switch on your bluetooth device, OpenSync will create a synchronization group automatically and ask the user to start syncing. To bring OpenSync to the level of _The Syncing Solution [tm]_ we must reduce the necessary configuration to a minimum.

What was the most dire problem you had to face when creating OpenSync and how did you face it?

Cornelius:

Fortunately the problems which I personally would consider to be dire are solved by the implementation of OpenSync which is well hidden from the outside world and [they are] an area I didn’t work on 😉

Armin:

I guess that I am the right person to answer this question then 🙂

The most complicated part of OpenSync is definitely the format conversion, which is responsible for converting the format of one device to the format that another device understands.

There are a lot of subsystems in this format conversion that make it so complex, like conversion path searching, comparing items, detection of mime types and last but not least the conversion itself. So this was a hard piece of work.

What was the greatest moment for you?

Cornelius:

I think the greatest moment was when, after three days of concentrated hacking, we had a first working version of the KDE frontend for OpenSync. This was at meeting at the SUSE offices in Nuernberg and we were able to successfully do a small presentation and demo to a group of interested SUSE people.

Armin:

I don’t remember a distinct “greatest moment”. But what is a really great feeling is to see that a project catches on, that other people get involved, use the code you have written and improve it in ways that you haven’t thought of initially.

Tobias:

Hmm, also hacking on OpenSync/KitcheSync is much fun in general, the greatest moment was when the new KitchenSync frontend synced two directories via OpenSync the first time. But it was also cool when we managed to get the IrMC plugin working again after porting it to OpenSync.

As we now know the worst problem you faced and your greatest moment, the only one missing is: What was your weirdest experience while working on OpenSync?

Cornelius:

Not directly related to OpenSync, but pretty weird was meeting a co-worker at the Amsterdam airport when returning from the last OpenSync meeting. I don’t know how high the chance is to meet somebody you know on a big random airport not related at all to the places where you or the other person live, but it was quite surprising.

Tobias:

Since my favorite language is C++, I was always confused how people can use plain C for such a project, half the time your are busy with writing code for allocating/freeing memory areas. Nevertheless Armin did a great job and he is always a help for solving strange C problems 🙂

Now I’d like to move on to some more specific questions about current and planned abilities of OpenSync. As first, I’ve got a personal one:

I have an old iPod sitting around here. Can I or will I be able to use a program utilizing OpenSync to synchronize my calendars, contacts and music to it?

Cornelius:

I’m not aware of any iPod support for OpenSync up to now, but if it doesn’t exist yet, why not write it? OpenSync makes this easy. This is a chance for everybody with the personal desire to sync one device or another to get involved.

Armin:

I dont think that there is iPod support yet for OpenSync. But it would definitely be possible to use OpenSync for this task. So if someone would like to implement an iPod plugin, I would be glad to help 🙂

Which other devices do you already support?

Cornelius:

At this time, OpenSync supports Palms, SyncML and IrMC capable devices.

Which programs already implement OpenSync and where can we check back to find new additions?

Cornelius:

On the application side there is support for Evolution [GNOME] and Kontact with KitchenSync [KDE] on the frontend side and the backend side and some more. I expect that further applications will adopt OpenSync once the 1.0 version is released.

Armin:

Besides kitchensync there already are a command line tool and a port of the multisync GUI. Aside from the GUIs, I would really like to see OpenSync being used in other applications as well. One possibility for example would to be integrate OpenSync into Evolution to give users the possibility to synchronize their devices directly from this application. News can generally be found on the OpenSync web site www.opensync.org.

It is time to give the developers something to devour, too. I’ll keep this as a short twice-fold technical dive before coming to the takeoff question, even though I’m sure there’s information for a double-volume book on technical subleties.

As first dive: How did you integrate OpenSync in KitchenSync, viewed from the coding side?

Cornelius:

OpenSync provides a C interface. We wrapped this with a small C++ library and put KitchenSync on top. Due to the object oriented nature of the OpenSync interfaces this was quite easy.

Recently I also started to write a D-Bus frontend for OpenSync. This also is a nice way to integrate OpenSync which provides a wide variety of options regarding programming languages and system configurations.

And for the second, deeper dive:

Can you give us a quick outline of those inner workings of OpenSync, from the developers view, which make OpenSync especially viable for application in several different desktop environments?

Cornelius:

That’s really a question for Armin. For those who are interested I would recommend to have a look at the OpenSync website. There is a nice white paper about the internal structure and functionality of OpenSync.

Armin:

OpenSync consists of several parts:

First there is the plugin API which defines what functions a plugin has to implement so that OpenSync can dlopen() it. There are 2 types of plugins:

A sync plugin which can synchronize a certain device or application and which provides functions for the initialization, handling the connection to a device and reading and writing items. Then there is a format plugin which defines a format and how to convert, compare and detect it.

The next part is a set of helper functions which are provided to ease to programming of synchronization plugins. These helper functions include things like handling plugin config files, HashTables which can be used to detect changes in sets of items, functions to detect when a resync of devices is necessary etc.

The syncing logic itself resides in the sync engine, which is a separate part. The sync engine is responsible for deciding when to call the connect function of a plugin, when to read or write from it. The engine also takes care of invoking the format conversion functions so that each plugin gets the items in its required format.

If you want more information and details about the inner workings of OpenSync, you should really visit the opensync.org website or ask its developers.

To add some more spice for those of our readers, whose interest you just managed to spawn (or to skyrocket), please tell us where they can get more information on the OpenSync Framework, how they can best meet and help you and how they can help improving sync-support for KDE by helping OpenSync.

Cornelius:

Again, the OpenSync web site is the right source for information. Regarding the KDE side, the kde-pim@kde.org mailing list is probably the right address. At the moment the most important help would be everything which gets the OpenSync 1.0 release done.

[And even though] I already said it, it can’t be repeated too often: OpenSync will be the one unified syncing solution for the free desktop. Cross-device, cross-platform, cross-desktop.

It’s the first time I feel well when thinking about syncing 😉.

Armin:

Regarding OpenSync, the best places to ask would be the opensync mailing lists at sourceforge or the #opensync irc channel on the freenode.net servers.

There are always a lot of things where we could need a helping hand and where we would be really glad to get some help. So everyone who is interested in OpenSync is welcome to join.

Many thanks for your time!

Cornelius:

Thanks for doing the interview. It’s always fun to talk about OpenSync, because it’s really the right thing.

Armin:

Thank you for taking your time and doing this interview. I really appreciate your help!

Tobias:

Thanks for your work. Publication and marketing is something that is really missing in the open source community. We have nice software but nobody knows 😉

Further Information on OpenSync can be found on the OpenSync Website: www.opensync.org

This Interview was done by Arne Babenhauserheide in April 2006 via e-mail and KOffice on behalf of himself, the OpenSource Community, SpreadKDE.org and the Dot (dot.kde.org).It was first published on the Dot and is licensed under the cc-attribution-sharealike-license.A pdf-version with pictures can be found at opensync-interview.pdf (OpenDocument version: opensync-interview.odt)

Thursday, August 27, 2015

Austrian police today found an estimated 20–50 decomposing corpses in an apparently abandoned lorry.

Roadworkers who spotted the vehicle, which had been there since yesterday at least, alerted police. Responding officers found it full of corpses. The lorry is on the so-called “Eastern Motorway”, the A4, close to the Hungarian border. It was on the hard shoulder between Neusiedl and Parndorf, closer to Parndorf.

The victims are thought to have suffocated. Police are seeking the driver. The Krone published an image of a non-articulated food lorry on the hard shoulder, which they report is the vehicle in question. The photo shows a pool of dark liquid on the ground beside the vehicle.

Video from a passing motorist shows at least one helicopter on-scene. The truck, which has pictures of meat on the side, shows branding for Slovakian food firm Hyza. Earlier today the company’s website sported an apparent anti-immigration graphic, which has since been removed.

Wikinews got in touch with Hyza. “We are truly sorry about [the] tragedy” they told us in a statement. They said they have checked GPS trackers on their fleet and all their vehicles remain in Slovakia. The statement says the lorry in question was one of 21 Hyza vehicles sold on last year. It was then sold again and exported to Hungary, where it is now registered. Hyza told us the new owners have not changed the branding on the vehicle. According to the Bild newspaper, Agrofert — the parent company of Hyza — said in a statement the new owners were required to do so.

Hyza says they will “actively cooperate with Slovak police”, and “express [their] sincere condolences to the bereaved families.”

Interior Minister Johanna Mikl-Leitner called it “a dark day” and called for European Union-wide measures to protect immigrant refugees and tackle human traffickers. Neighbouring Hungary is constructing a border fence across its entire frontier with Serbia. Yesterday alone saw a record 3,241 attempts to enter Hungary illegally, according to authorities there.

Conflict in Syria and other parts of the world has led refugees to Europe. Once inside, they can move freely inside the Schengen Area, which covers most of the EU.

Austrian police earlier this week arrested three motorists suspected of people smuggling. One driver is accused of moving 34 people, ten of them children, into Austria from Serbia. The group were left by the roadside near Bruck an der Leitha and reported struggling to breathe in the van.