<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.editors.lyx.devel">
    <title>gmane.editors.lyx.devel</title>
    <link>http://blog.gmane.org/gmane.editors.lyx.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109404"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109391"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109382"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109376"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109373"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109358"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109350"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109340"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109328"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109310"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109302"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109293"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109292"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109258"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109253"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109248"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109233"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109231"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109227"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.lyx.devel/109224"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109404">
    <title>Lipitor Market analysis and forecasts</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109404</link>
    <description>     
 
   
Lipitor Market analysis and forecasts Report, 2007-2012, 2017 &amp; 2023

-NEW REPORT- 

In 2006, Pfizer&amp;rsquo;s Lipitor (atorvastatin) generated global revenues of $13.6bn, making it the best selling drug in pharmaceutical history. The blockbuster medicine has single-handedly driven the overall revenue margins of the cardiovascular segment, as this area continues to dominate the pharmaceutical market. Despite the maturing status of Lipitor, the drug has repeatedly maintained steady growth over the past 5 years, crowding out the yearly revenues of other lipid-regulating blockbuster drugs: Merck&amp; Co&amp;rsquo;s Zocor and Zetia, Astrazeneca&amp;rsquo;s Crestor, Abbott&amp;rsquo;s Tricor and Bristol Myers Squibb&amp;rsquo;s Pravacol. 

However, as Lipitor&amp;rsquo;s blockbuster revenue is seriously threatened by imminent patent expiration in some of the drug&amp;rsquo;s largest markets such as the US, Japan and the UK, there is significant unrest between Pfizer&amp;rsquo;s key stakeholders about the future of the drug. Principally, amongst the heightened Lipitor topics are the imminent exposure of the $1 billion annual drug sales or more, as well as the fast expanding generic market in which India&amp;rsquo;s Ranbaxy is a dominant force. 

What questions does the report answer? 
&amp;bull; Has the success of Pfizer&amp;rsquo;s Lipitor been overstated?
&amp;bull;Did Pfizer create a monster in Lipitor?
&amp;bull;Have Lipitor sales redefined the bounds that pharmaceutical margins can now reach? 
&amp;bull;How imminent is Lipitor patent expiration?
&amp;bull;Which key markets will suffer the consequence of Lipitor expiry?
&amp;bull;Is Ranbaxy ready for generic Lipitor?
&amp;bull;Do the fast developing markets, CEE and the Latin America segment hold the key to future sales after Lipitor&amp;rsquo;s patent expiration?
&amp;bull;Is Lipitor a victim of the struggling Blockbuster Model?
&amp;bull;What is next for Lipitor? 
&amp;bull;Do the fast developing markets, CEE and Latin America segment hold the key to future sales after Lipitor&amp;rsquo;s patent expiration? 
&amp;bull;Is Lipitor, a victim of the struggling Blockbuster Model?
&amp;bull;What is next for Lipitor? 

As Pfizer&amp;rsquo;s Lipitor struggles to fend off the immediate entry of Ranbaxy&amp;rsquo;s generic Lipitor, in key markets, the legal challenges surrounding the number one drug have set a new benchmark for pharmaceutical companies protecting branded products. Industry observers including Visiongain predicts that Pfizer&amp;rsquo;s crises are far from over, as the high revenue streams of Lipitor will experience significant challenges before the commencement of the next decade. 

Moreover, Pfizer&amp;rsquo;s lack of success to replace Lipitor with Torcetrapib has escalated the company&amp;rsquo;s near-term battles besides the ever-tighter regulatory hurdles, reduced R&amp;D efficiency and increased competition, creating formidable therapeutic challenges as healthcare payers influence pricing. Nevertheless, there are strong drivers of growth including unmet therapeutic needs, the rising incidence of multiple diseases, ageing populations, the rising living standards and fast-developing geographical markets. The future of Lipitor is therefore vitally important to Pfizer, especially in this uncertain period of economic changes and pressures. 

This report includes detailed five-year forecasts over the period 2008-2013, and NOW features 10 and 15-year forecasts to help you understand the medium-term prospects for these markets. 

                  This unique in-depth management report examines the future prospects for Lipitor from 2008-2023. It delivers direct to you future sales forecasts for leading Lipitor in all seven major markets (7MM). This detailed report highlights the most compelling must know issues- Lipitor&amp;rsquo;s patent contention by Pfizer in both 7MM and other markets in order to block Ranbaxy&amp;rsquo;s immediate penetration of generic Lipitor. In light of healthcare drug bills increasing exponentially, generic Lipitor will be welcomed by managed care organisations (MCO) and further widen the generic revenue margins, visiongain concludes. This report also tackles Lipitor&amp;rsquo;s significant developments, potential opportunities on the market and important contemporary matters, especially commercial drivers and restraints. 

Unique benefits to you when you order this report:
- Primary research throughout: you will not find this information anywhere else
- Full searchable report when you buy the company or corporate editions
- Easily downloadable copies of the report available for offline reading
- The report is filled with detailed charts, analysis, figures, graphs and tables

 

- PRICING -

Departmental  copies (this entitles up to 5 individual users in your department) of this  report are available for only GBP&amp;pound;2999. This is not suitable for library usage. 


Allow  your whole company to have access to this information for only GBP&amp;pound;4999.  Company-wide License allows your whole company access and intranet use on CD  Rom and .pdf. Suitable for library storage and use.


Does your  company have over 2,500 employees? Have the whole company access this  information for a special rate of only GBP&amp;pound;6999-ORDERING-

Ordering is simple! All you need to do to order this report  is contact Justyna.You can either call me on
TEL: +44 (0)207 549 9946                 or email:justyna.drozdzal&lt; at &gt;visiongainglobal.com 

Please feel free to contact me should you have any  questions, or wish to purchase a copy, I look forward to hearing from you. 

Kind Regards,

Justyna Drozdzal
Visiongain - Ltd.  


TABLE OF  CONTENTS

            1 Executive Summary
1.1 Lipitor Was the World's Best Selling Drug In 2006
1.2Lipitor Will Face Strong Competition After Patent Expiration In Key Markets
1.3 Lipitor Is Embroiled In Patent Challenges With Ranbaxy 

2 Overview of Lipitor (Atorvastatin)
2.1 Lipitor (Atorvastatin) - The Cholesterol Reducing Drug
2.1.1 Pfizer Acquires Lipitor After Merging With Warner-Lambert
2.1.2 Dyslipidemia 
2.1.2.1 Classification of Dyslipidaemia
2.1.3 Dyslipidaemia - a Major Risk Factor In Developing Coronary Heart Disease In The Western Population
2.1.4Aetiology of Dyslipidaemia
2.1.4.1Primary Causes of Dyslipidemia
2.1.4.2Secondary Causes of Dyslipidaemia
2.1.4.3Diabetes A Leading Cause of Secondary Dyslipidaemia
2.2 Obesity Is a Major Environmental Factor Associated With Dyslipidaemia
2.2.1 Strong Link Between Diabetes And Obesity
2.2.2 Diet Remains An Important Component In Regulating Lipid levels 
2.2.3 Behaviour
2.2.4 Regular Physical Exercise
2.3 Symptoms and Signs of Dyslipidaemia
2.4 Diagnosis, Screening and Markers of Dyslipidaemia
2.4.1Direct Measurement of Total cholesterol, Triglycerides, And HDL
2.4.2 Estimation of Low-density Lipoprotein (LDL) And Very Low-Density Lipoprotein (VLDL)
2.4.3 Fasting Lipid Profile
2.4.4 Screening Patients Under 20 Years For Atherosclerotic Risk Factors
2.4.5 Screening For Lipoprotein(a) levels 

3 Treatment of Dyslipidaemia
3.1 Lipid Regulating Drugs Are Central To Treating Dyslipidaemia 
3.1.1 Statins are First Choice Lipid-Regulating Drugs 
3.1.2 Statin Drugs Are Significant Market for Leading Pharmaceutical Companies
3.1.3 Lipitor A Second-Generation 3-hydroxy-3-methygulutaryl coenzyme A (HMGCoA) Reductase Inhibitor Gold Standard Drug
3.2 Posology And Method of Administration of Lipitor
3.2.1 Primary Hypercholesterolaemia and Combined (Mixed) Hyperlipidaemia In Adults And Children aged 10-17 years
3.2.1.1 Heterozygous Familial Hypercholesterolaemia in Adults and Children aged 10-17 years
3.2.1.2 Homozygous Familial Hypercholesterolaemia in Adults and Children aged 10-17 years 
3.2.1.3 Lipitor Dosage in Patients With Renal Insufficiency 
3.2.1.4 Lipitor Dosage in Patients With Hepatic Dysfunction 
3.2.1.5 Lipitor Dosage in Geriatric 

4 Lipitor World Market Analysis
4.1 Lipid-regulating/ Anti-Atheroma Preparations Is The Largest In Cardiovascular System Market 
4.1.1 Pfizer Is The Leader In Cardiovascular Pharmaceuticals
4.1.2 Cholesterol And Triglycerides Reduction Drugs Generate Highest Individual Sales 
4.1.3 The US Market For Cholesterol and Triglyceride Drugs Sees The largest Sales
4.2 Lipitor (Atorvastatin) Revenue Dominates all Cholesterol &amp; Triglyceride Drugs
4.2.1 Lipitor Sales in North America, Europe, Africa, Asia &amp; Australasia and Latin America
4.2.1.1 Lipitor Sales are Most Significant In US 
4.2.1.2 Lipitor Drives Sales For Cholesterol &amp; Triglyceride Reducers In The EU Market
4.2.1.3 UK is Lipitor's Largest Market In Europe
4.2.1.4 Lipitor Sales Decline in France 
4.2.1.5 Lipitor Sales Grow By 10% In 2006
4.2.1.6 Lipitor Experiences Strong Market Growth In Italy
4.2.1.7 Lipitor Year-on-Year Sales Decline Continued In Germany 
4.2.1.8 Japan is Lipitor's Strongest Market  in Africa, Asia &amp; Australasia
4.3 Lipitor's Faces Competitions From Key Rivals In Major Markets
4.3.1 Lipitor's Prescription Volume Eroded Steeply Due To Generic Statins
4.3.2 AstraZeneca's Crestor, Merck &amp; Co and Schering Plough's Vytorin Dampens Lipitor's Market Share 
4.3.3Head-to-Head Clinical Study Proves Lipitor to Be More Potent Than Crestor
4.3.4 Vytorin A Strong Contender For Market Share With Lipitor During Near-Term
4.4 Pfizer's Lipitor Challenge With Ranbaxy Will Have Significant Implications On Future Sales
4.5 US WellPoint Demonstrates Generic Statins- Lovastatin, Simvastatin And Pravastatin To Elicit Cardiovascular Benefits 
4.6 Lipitor Global Sales Forecast 2008-2023
4.6.1 Lipitor's Five New Indications Will Be key To Sales Growth After Patent Expiration 
4.6.2 Lipitor Major Market Sales Forecast 2008-2023
4.6.3 US Lipitor Market Forecasts 2008-2023
4.6.4 Japan Lipitor Market Forecast 2008-2023
4.6.5 EU Lipitor Market Forecast 2008-2023
4.6.6 UK Lipitor Market Forecast 2008-2023
4.6.7 France Lipitor Market Forecast 2008-2023
4.6.8 Spain Lipitor Market Forecast 2008-2023
4.6.9 Italy Lipitor Market Forecast 2008-2023
4.6.10 Germany Lipitor Market Forecast 2008-2023
4.7 Lipitor Competes With Other Non-Statin Drugs
4.7.1 Bristol Myers Questran Is leading Anion Exchange Resin 
4.7.2MSD and Schering-Plough's Ezetrol An Adjunct Therapy for Inhibiting Absorption of Cholesterol 
4.7.3Fibrates Constitute A Significant Market
4.7.4 Niaspan Is Key Nicotinic Acid Competitor To Lipitor
4.7.5 Simcor- Niaspan And Generic Simivastatin Will Increase Lipitor Competition
4.7.6 US National Heart, Lung and Blood Institute Sponsors Niaspan And Simvastatin AIM-HIGH Study
4.7.7 Fish Oils Industry A Growing Market and A deterrent To Lipitor Growth
4.8 Pfizer Has Large Resources To Promo

5. Lipitor&amp;rsquo;s Key Patent Challenges
5.1 Patent Expiration is the Major Driver in All Generic Markets
5.2 The US Has The Largest Generics Market
5.3 The US and European Regulation of Generic Drugs
5.4 Pfizer&amp;rsquo;s Lipitor Patent Protection Sets Benchmark In Pharmaceutical Industry For Protecting Brands 
5.5 Pfizer Struggles To Block Early Generic Lipitor Market Entry
5.6 The Hatch-Waxman Act, Patent Expiration and the Promotion of Generic Drugs: Title I of the Act
5.6.1 Ranbaxy To Benefit From The Hatch-Waxman Title I
5.6.2 US First To Market 180-Day Exclusivity Period Incentive Will Be Key To Rambaxy&amp;rsquo;s Initial Sales Success of Generic Atorvastatin 
5.7 Ranbaxy Receives Favourable Lipitor Decisions in Key EU Markets 
5.7.1 Federal Patent Court of Germany Revokes Lipitor Patent
5.8 Lipitor Expanding Patent Contention
5.8.1 Pfizer Versus Teva Pharmaceuticals&amp;rsquo; ANDA For Generic Atorvastatin
5.8.2 Pfizer Versus Cobalt Pharmaceuticals For Atorvastatin Sodium A Potentially Marketable Product
5.8.3 Pfizer Vs Apotex Generic Atorvastatin In Canada
5.9 Ranbaxy Will Cover Cost of Legal Challenges From Sales of Atorvastatin in Key Markets

6 Lipitor- Product Life Cycle Management (PML)
6.1 Pfizer To Use Product Lifecycle Management to Drive Sales of Lipitor
6.2 Pfizer&amp;rsquo;s Prominent PLM Is Caduet- "uber-pill", a combination of Lipitor And Norvasc 
6.2.1 Caduet Sales Rises Significantly By 99% in 2006 
6.3 Pfizer&amp;rsquo;s Torcetrapib- The Lipitor Follow-Up Drug Fails To Deliver
6.4 Pfizer Lipitor and Peripheral Vascular Diseases
6.5 Pfizer's LEAD Trial investigates Lipitor in Combination with Aricept in AD patients 
6.6. Other Lipitor Significant Clinical Studies 
6.6.1 Lipitor Pre-Clinical Data 
6.6.1.1 Atorvastatin Proves to be More Liver Selective Than Pravastatin
6.6.2 Atorvastastin Clinical Data
6.6.2.1 Atorvastatin Was Tolerated in Healthy Volunteers 
6.7 Cardiovascular Disease 
6.7.1 Ten milligram (10 mg) of Atorvastatin Has Significant Effect Lipid-Lowering Ability 
6.7.2 Coronary Artery Disease-AVERT (Atorvastatin Versus Revascularization Treatment) 
6.7.3 Ten milligram (10 mg) Atorvastatin is Effective in Australian Atorvastatin Assessment Study
6.7.4 Myocardial Ischemia Reduction with Aggressive Cholesterol Lowering (MIRACL) Study
6.7.5 ASCOT trial Demonstrates Atorvastatin to Reduce Risk of Heart Attack Induced by Hypertension
6.7.6 Head-To-Head REVERSAL Trial Demonstrates that Highest Dose of Atorvastatin, Halted Atherosclerosis 
6.7.7 Post-Hoc Analysis in Treating New Targets (TNT ) Trial Demonstrates Atorvastatin 80 mg with Less Cardiovascular Events Than 10 mg dose
6.7.8 Atorvastatin - Incremental Decrease in Endpoints Through Aggressive Lipid Lowering (IDEAL) Trial Reveals Significantly Fewer Risk of Secondary Heart Attacks 
6.7.9 CARDS study (Collaborative AtoRvastatin Diabetes Study)-Shows Marked Reduction in Percentages Risk of Cardiovascular Events in Diabetes Patients 
6.7.10 SPARCL study (Stroke Prevention by Aggressive Reduction in Cholesterol Study)
6.7.11 Atorvastatin Lowers Cardiovascular Disease By a Significant Percentage 
6.8 Paediatric Studies Demonstrated Significant Therapeutic benefits of Lipitor
6.9 Lipitor Post Marketing Studies

7 Lipitor Competitor Studies &amp; Pipeline
7.1 Lipitor worldwide clinical studies 
7.2 Competitor Agents in Development
7.2.1 Abbott And AstraZeneca's Developmental Fibrate /Cholesterol reducing Agent Shows Significant Potential 
7.2.2 First Horizon's Fenofibrate (Triglide) And Aegerion's MTP Inhibitor (AEGR 733)

8 Lipitor SWOT Analysis
8.1 Lipitor First Drug of Choice For Cholesterol Treatment
8.2 Lipid Regulator Market Will Continue to Generate High Revenues
8.3 An Expanding Patient Population Constitutes the Principal Driver in the Statins Market
8.4 Changes to Treatment Guidelines in US and Europe Can Benefit Sales Of Lipitor
8.5 The US Market Will Continue To Be Key for Lipitor's Sales Growth 
8.6 Generic Rivals Will Drive The Erosion of Lipitor's Market Share 
8.6.1 The US has the Largest Generics Market
8.6.2 Generic Statins A Growing Presence In The US Market 
8.6.3 Rising Generic Uptake in Key EU Markets Will Impact On Lipitor Sales 
8.6.4 Generic Statins Potential Threat To Lipitor Growth As They Become Mainstay In Japan
8.7 Pfizer And Astellas Reach Lipitor Settlement In Japan 
8.8 US and EU Two -Year Statin Approval Timelines Increase Competitiveness 
8.9 Lipitor A Testimony of The Crumbling Blockbuster Business Model
8.10 Pfizer Will Need Strategies That Will Yield High ROI After Lipitor's Patent Expiration
8.11 New Reformulation Will be Significant To Drive Lipitor &amp;lsquo;s Long-Term Revenues
8.12 Liptor Still Has Significant Developmental Possibilities
8.13 Lipitor&amp;rsquo;s Prominent Indications For Diverse Cardiovascular and Metabolic Areas Will be Significant For Future Sales
8.14 Lipitor Significant Trial Results Will Drive Sales 
8.15 Is Pfizer&amp;rsquo;s Lipitor Success Repeatable?
8.16 US House of Democrats Investigate Lipitor's Director-To-Customer Advertisement Campaign 
8.17 OTC Simvastatin Adds To Lipitor&amp;rsquo;s Competition
8.18 Anti-Counterfeiting Initiatives Will Safeguard Lipitor in Emerging Markets 
8.19 Lipitor Will Face Pricing Competition From Generic Statins

9 Conclusion
9.1 Lipitor (Atorvastatin) - The Cholesterol Reducing Drug
9.2 Lipid-regulating Drugs Generate The Highest Revenues In Cardiovascular Market 
9.3 Statin Drugs Are Significant Market for Leading Pharmaceutical Companies
9.4 Lipitor (Atorvastatin) Is The World's Highest Selling Drug 
9.5 Lipitor Sales Are Most Significant In the US Market 
9.5.1 Lipitor Sales in other Key Markets 
9.5.2 Lipitor Global Sales Forecast 2008-2023
9.6 Lipitor's Faces Competition From Key Rivals
9.7 Non-Statin Drug Therapies Market Expands
9.8 Pfizer Using Product Lifecycle Management to Drive Sales of Lipitor
9.9 Caduet Positioned To Experience Strong Sales After Lipitor Expiration 
9.10 Ranbaxy&amp;rsquo;s Successsful Patent Lawsuits Against Pfizer In Key Markets Will Be Costly To Lipitor&amp;rsquo;s Future Sales 
9.11 Visiongain Concludes that Loyalty from Pfizer and Brand "Lipitor's" Key Stakeholders Will Confer Future Sales 

List of Tables
Table 2.1 Lipoprotein Patterns (Fredrickson Phenotypes)
Table 2.2 Genetic Variations In Dyslipidaemia
Table 2.3 Obese Population in Major Countries by Percentage (%)
Table 4.1 Sales Distribution of Cardiovascular Disease Market, 2006
Table 4.2Leading Companies in Cardiovascular Market, 2006
Table 4.3 Sales Distribution of Leading Anti-Atheroma Therapies, 2006
Table 4.4 Leading Markets In Cholesterol and Triglyceride Drugs
Table 4.5 Global Sales of  Top Ten Leading Statin Drugs, 2006
Table 4.6 Market Share of Lipitor in leading Markets, 2003-2006
Table 4.7 Lipitor Sales in Key EU Markets, 2003-2006
Table 4.8 Comparison of Effects on Cholesterol Levels
Table 4.9 Comparison of Dose Effects on LDL Cholesterol (LDL-C)
Table 4.10 Lipitor (Atorvastatin) Patents Expiration In Major Markets
Table 4.11 Lipitor Global Sales Forecast 2008-2023
Table 4.12 US Lipitor Global Sales Forecast 2008-2023
Table 4.13Japan Lipitor Global Sales Forecast 2008-2023
Table 4.14 UK Lipitor Global Sales Forecast 2008-2023
Table 4.15 France Lipitor Global Sales Forecast 2008-2023
Table 4.16 Spain Lipitor Market Forecasts 2008-2023
Table 4.17 Italy Lipitor Market Forecasts 2008-2023
Table 4.18 Lipitor Sales In Germany, 2003-2006
Table 4.19 Germany Lipitor Market Forecasts 2008-2023
Table 4.20 Leading Fibrate Drugs, 2006 
Table 4.21 Leading Anti-atheroma Preparations Of Natural Origin (Fish Oil Products), 2006 
Table 5.1 The Top Ten US Generic Drugs by Revenue ($m) and Units, 2006
Table 5.2 US Top Ten Generic Drugs as a Function of Combined Branded and Generic Drugs by Prescription Number (m) and Revenues ($m),2006 
Table.5.3 Prescription Number (m), 2004 Top 10 Generic Drugs, Dispensed by Prescriptions in the US, 2006
Table 5.4 Lipitor (Atorvastatin) Patents In Major Markets
Table 5.5 Ranbaxy /Pfizer (Atorvastatin) Patents Challenges In Other Markets
Table 6.1 Pfizer Post Marketing Lipitor Studies
Table 6.2 Pfizer&amp;rsquo;s Lipitor Phase III Studies
Table 7.1 Competitors Post Marketing Cardiovascular Agents Studies Including Lipitor
Table 7.2 Competitors Comparative Phase III Cardiovascular Agents Including Lipitor 
Table 7.3 Competitors Comparative Phase II Cardiovascular Agents Including Lipitor 
Table 7.4 Competitors Comparative Phase I Cardiovascular Agents Including Lipitor 
Table 7.5 Competitors Other Comparative Cardiovascular Agents Including Lipitor 
Table 8.1 Lipitor Market SWOT Analysis

List of Figures
Figure 1.1 Market Shares of Leading Statin Drugs, 2006
Figure 1.2 Lipitor Sales in key leading markets, 2003-2006
Figure 1.3 Lipitor Market Share in key leading markets, 2003-2006
Figure 4.1 Sales Distribution of Cardiovascular Disease Market, 2006
Figure 4.2 Leading Companies in Cardiovascular Market, 2006
Figure 4.3 Sales Distribution of Leading Anti-Atheroma Therapies, 2006
Figure 4.4 Leading Markets Share In Cholesterol and Triglyceride Drugs
Figure 4.5 Sales Distribution of Top Ten Leading Statin Drugs, 2006
Figure 4.6 Sales Distribution of Top Five Leading Statin Drugs, 2006
Figure 4.7 Market Share of Lipitor in leading Markets, 2006
Figure 4.8 Lipitor Sales in Key EU Market, 2006
Figure 4.9 Market Share of Lipitor in Key EU Market, 2006
Figure 4.10 Lipitor Global Sales Forecast 2008-2023
Figure 4.11 US Lipitor Market Forecasts 2008-2023
Figure 4.12 Japan Lipitor Market Forecasts 2008-2023
Figure 4.13 UK Lipitor Market Forecasts 2008-2023
Figure 4.14 France Lipitor Market Forecasts 2008-2023
Figure 4.15Spain Lipitor Market Forecasts 2008-2023
Figure 4.16 Italy Lipitor Market Forecasts 2008-2023
Figure 4.17 Lipitor Sales In Germany, 2003-2006
Figure 4.18Germany Lipitor Market Forecasts 2008-2023




 

 

If you do not wish to   receive future messages please reply to this message typing 'unsubscribe' in   the subject box of your email.
 Please allow 48hours to remove your email address.Thank you very much for your cooperation. 
</description>
    <dc:creator>Visiongain</dc:creator>
    <dc:date>2008-07-23T12:37:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109391">
    <title>I'm interested in the LyX 1.7.x XML format</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109391</link>
    <description>Hi all,

I'm Steve Litt, a regular on the user's list. Since 2001, all my books have 
been written in LyX.

I'm not a LyX developer. Believe me, you guys wouldn't want to work with my 
C++ code.

What brings me here is an interest, from a user point of view, in the upcoming 
XML native format. This interest comes from the fact that I regularly create 
LyX native format docs programmatically, and regularly edit LyX docs in Vim 
when I don't know how to accomplish it within LyX itself.

Because I strongly believe that XML is difficult to casually parse, I'd like 
to do the following:

1) Document your new XML format. Not only its specification, but the reasons 
and philosophies behind it. I think this will be of use to other LyX "power 
users" who, like myself, sometime create/change LyX content without the LyX 
front end.

2) During initial design, review the new XML format from a power user point of 
view, and point out areas where it makes the power user's job difficult. 
Redundancy would be one example. If the paragraphs were in one place, and the 
number of paragraphs were in another, changing one would require changing the 
other, and that's not obvious upon casual observation of the native format 
file.

3) Create LyX-XML to YAML and YAML to LyX-XML utilities, so that power users 
can do their parsing in easy to parse YAML and then convert it back to 
LyX-XML. This decouples the needs of the LyX developers from the needs of 
power users. I'll write these utilities first in Ruby for the oldest reason 
in the world -- it's easy. Later I can probably rewrite them in C or C++, 
depending on what XML parsers are available.

I'm the maintainer of the VimOutliner to LyX script, so it's important to me 
that the script continue to work after the transition to XML. Also, many 
times I find it a big timesaver to edit LyX with Vim to do my work. These are 
the reasons I'd like to do these three things.

Thanks

SteveT

Steve Litt
Recession Relief Package
http://www.recession-relief.US


</description>
    <dc:creator>Steve Litt</dc:creator>
    <dc:date>2008-07-23T17:04:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109382">
    <title>auxiliary calls with pdflatex or: pst-pdf</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109382</link>
    <description>Hello list,

i would like to use the pst-pdf package for including pstricks in
pdflatex outputs.
According to http://tug.org/PSTricks/main.cgi?file=pdf/pdfoutput the
pst-pdf package is the best solution for embedding ps code into pdf.

The pst-pdrf package documentation gives an example of how the package
works. It needs auxiliary calls to create the ps graphics.


PostScript graphics                                         bibliography
-------------------------------------------------------------------------------------------------------
pdflatex document.tex                                     pdflatex document.tex
---------------------------------------------------------------------------------------------------------
auxiliary calls

latex document.tex
dvips -o document-pics.ps document.dvi
ps2pdf document-pics.ps                                 bibtex document.aux
--------------------------------------------------------------------------------------------------------
pdflatex document.tex                                     pdflatex document.tex



The used analogy to the bibliography let me assume that is not
straightforward to use this package with LyX.
Does such auxiliary calls need to be implemented in LyX like the
bibliography is?

I don't think that the need for ps graphics in pdf is so common that
it justifies the implementation as a seperate topic inside of LyX.
However there might be the need in general for such auxiliary calls
during the output sequence.

Do i miss something? Is there already an easy way to use pst-pdf within LyX?

Thanks in advance
Christoph

</description>
    <dc:creator>Christoph Friederich</dc:creator>
    <dc:date>2008-07-23T11:16:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109376">
    <title>Documentation of LyX functions (aka LFUNs)</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109376</link>
    <description>Dear LyXers,

I'm proud to announce that the LFUNs documentation project has been finished.

If you are interested in mastering LyX this documentation could be useful for
your needs.

Some technical speech:

* All documentation is orginally written as doxygen comments in our source code, 
  so this should be the first place to check-up documentation bugs, improvements etc.
  You should be able to find most up-to-date version (but not much readable) here:

  http://www.lyx.org/trac/browser/lyx-devel/trunk/src/LyXAction.cpp


* The documentation is synchonized with the upcomming LyX 1.6. Many things
  could be used even for 1.5 series of LyX, but be careful (bug reports should
  be checked always against 1.6.)


* HTML documentation was produced via doxygen. The file could be found here:

  http://www.lyx.org/~sanda/doxygen/html/namespacelyx.html

  or you can go directly to the right section:

  http://www.lyx.org/~sanda/doxygen/html/namespacelyx.html#5ae63e8160e98b54ad28f142ed40c202


* .lyx version was produced by hand-crafted script and can be found here:

   http://www.lyx.org/~sanda/doxygen/lfuns.lyx

   or .pdf version respectively:

   http://www.lyx.org/~sanda/doxygen/lfuns.pdf


I would appreciate all bug reports (i.e. some lfun does not work in the way
its documented), typo in documentation etc.


Disclaimer: Please note that the conversion to HTML or .lyx is not at all
100% and is not intended to be typographical jewel...

Enjoy!
Pavel

</description>
    <dc:creator>Pavel Sanda</dc:creator>
    <dc:date>2008-07-23T02:47:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109373">
    <title>drop support for xymatrix?</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109373</link>
    <description>I just tried out our support for \xymatrix. The result is that you can't use it. The underlying 
LaTeX-package "xypic" is from 1999 and fails for all our documents because, we use babel and other 
standard packages.

When I test out some of the example files from here:
http://www.ctan.org/tex-archive/macros/generic/diagrams/xypic/xysamples/
They all fail as soon as I load babel, or hyperref, or fontenc, or inputenc, no matter at what 
position I load them.

So the support for xymatrix is unusable due to the broken package and I think it should therefore be 
removed and our program code be moved to SVN attic (in case that xypic becomes usable again).

Opinions or experiences with \xymatrix?

regards Uwe

</description>
    <dc:creator>Uwe Stöhr</dc:creator>
    <dc:date>2008-07-23T00:33:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109358">
    <title>Long start of lyx</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109358</link>
    <description>it happened for the third time in last 24 hours, i try load  document (all were very simple)
and lyx freeze for one minute, with 100% CPU load, then it continues
well.

i tried to attach the process with gdb and cought this backtrace (sorry no debug
symbols here):

0xb799da98 in QStyle::sliderPositionFromValue () from /usr/lib/qt4/libQtGui.so.4
(gdb) bt
#0  0xb799da98 in QStyle::sliderPositionFromValue () from /usr/lib/qt4/libQtGui.so.4
#1  0xb79f880c in QPlastiqueStyle::drawComplexControl () from /usr/lib/qt4/libQtGui.so.4
#2  0xb7af64e5 in QSlider::paintEvent () from /usr/lib/qt4/libQtGui.so.4
#3  0xb77a9c83 in QWidget::event () from /usr/lib/qt4/libQtGui.so.4
#4  0xb7a56734 in QAbstractSlider::event () from /usr/lib/qt4/libQtGui.so.4
#5  0xb7af5cfc in QSlider::event () from /usr/lib/qt4/libQtGui.so.4
#6  0xb775de4f in QApplicationPrivate::notify_helper () from /usr/lib/qt4/libQtGui.so.4
#7  0xb776009c in QApplication::notify () from /usr/lib/qt4/libQtGui.so.4
#8  0x08402765 in lyx::frontend::GuiApplication::notify ()
#9  0xb756d4ab in QCoreApplication::notifyInternal () from /usr/lib/qt4/libQtCore.so.4
#10 0xb77adcae in ?? () from /usr/lib/qt4/libQtGui.so.4
#11 0xb78cc980 in QWidgetPrivate::drawWidget () from /usr/lib/qt4/libQtGui.so.4
#12 0xb78cc258 in ?? () from /usr/lib/qt4/libQtGui.so.4
#13 0xb78cc4f5 in QWidgetPrivate::drawWidget () from /usr/lib/qt4/libQtGui.so.4
#14 0xb78cc258 in ?? () from /usr/lib/qt4/libQtGui.so.4
#15 0xb78cc4f5 in QWidgetPrivate::drawWidget () from /usr/lib/qt4/libQtGui.so.4
#16 0xb78cea1e in ?? () from /usr/lib/qt4/libQtGui.so.4
#17 0xb78cef6c in ?? () from /usr/lib/qt4/libQtGui.so.4
#18 0xb77a9a5d in QWidget::event () from /usr/lib/qt4/libQtGui.so.4
#19 0xb7a6fc8f in QComboBox::event () from /usr/lib/qt4/libQtGui.so.4
#20 0xb775de4f in QApplicationPrivate::notify_helper () from /usr/lib/qt4/libQtGui.so.4
#21 0xb776009c in QApplication::notify () from /usr/lib/qt4/libQtGui.so.4
#22 0x08402765 in lyx::frontend::GuiApplication::notify ()
#23 0xb756d4ab in QCoreApplication::notifyInternal () from /usr/lib/qt4/libQtCore.so.4
#24 0xb756e8b3 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/qt4/libQtCore.so.4
#25 0xb75937df in QEventDispatcherUNIX::processEvents () from /usr/lib/qt4/libQtCore.so.4
#26 0xb77dea16 in ?? () from /usr/lib/qt4/libQtGui.so.4
#27 0xb756c9e1 in QEventLoop::processEvents () from /usr/lib/qt4/libQtCore.so.4
#28 0xb756caea in QEventLoop::exec () from /usr/lib/qt4/libQtCore.so.4
#29 0xb756ec86 in QCoreApplication::exec () from /usr/lib/qt4/libQtCore.so.4
#30 0xb775d807 in QApplication::exec () from /usr/lib/qt4/libQtGui.so.4
#31 0x083fd572 in lyx::frontend::GuiApplication::exec ()
#32 0x081478bd in lyx::LyX::exec ()
#33 0x080713c7 in main ()

maybe somebody has idea whats going on...
i'm not able to reproduce it.
pavel

</description>
    <dc:creator>Pavel Sanda</dc:creator>
    <dc:date>2008-07-22T21:05:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109350">
    <title>Customizable toolbar menus ..</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109350</link>
    <description>Will it be possible in a near future to implement complete customization of
the math-type toolbars like in Firefox (with the drag and drop) ?
 By the way, thank you for all your great work. I'm using 1.6beta4 and I'm
impressed !
</description>
    <dc:creator>Danny Ferrin</dc:creator>
    <dc:date>2008-07-22T19:45:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109340">
    <title>Update Gettext in Branch ?</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109340</link>
    <description>Hi,

Jürgen cordially made a tar-ball for me of current 1.5.6svn so that I 
can try to hunt after the drawing-problems/crashes (build-problems?) on 
the Mac.

Currently in branch is gettext 0.14.6, which causes a problem on the mac 
since it erroneously includes the wrong header files for CoreFoundation 
[2]. The problem is that gettext sets a wrong -I compiler flag (pointing 
to the system files instead of the SDK) which is then used for 
_everything_, not just gettext. This was fixed in later gettext versions.

There was some discussion if gettext should be removed entirely (and 
become an external depedency) [1], but _I think_ finally Jean-Marc 
updated gettext in trunk.

Do you think gettext could be updated in branch, too?

Thanks a lot,
Konrad

[1] http://thread.gmane.org/gmane.editors.lyx.cvs/19226/focus=108346
[2] http://thread.gmane.org/gmane.editors.lyx.devel/108070/focus=108268

</description>
    <dc:creator>Konrad Hofbauer</dc:creator>
    <dc:date>2008-07-22T16:56:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109328">
    <title>How to touch statusbar?</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109328</link>
    <description>hello,
it seems to impossible to send some message to our status bar
from inside any lfun, because whatever you send is at the end
of lfun handling rewritten by name of lfun itself. do we have
any mechanism howto queue messages into statusbar?

pavel

</description>
    <dc:creator>Pavel Sanda</dc:creator>
    <dc:date>2008-07-22T14:41:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109310">
    <title>Minor LyX comments</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109310</link>
    <description>Hi,

I'm a LaTeX user that has to debug other people's LyX documents :) The  
work you guys do is great; every now and again I run into problems  
that perhaps could do with a fresh set of eyes, especially from the  
LaTeX side of the fence.

Anyway, if it weren't for LyX then I doubt I'd be able to get even 10%  
of the people I do using some sort of TeX variant.

I've been meaning to pass on a few comments that I've collected over  
the years, but have hardly ever found the time.
   &lt;http://willwont.blogspot.com/2008/07/problems-with-lyx-1.html&gt;

There's not much there, but I'm afraid that I'm unable put much effort  
in at this stage. I can't guarantee that I'll remained subscribed  
here, based on the traffic, but I'll do my best to stay in touch.

Best regards,
Will</description>
    <dc:creator>Will Robertson</dc:creator>
    <dc:date>2008-07-22T09:10:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109302">
    <title>hints on compilation</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109302</link>
    <description>I have compiled the lyx 1.6 development branch using svn. It took more than
12 hours to complete, on my centrino laptop, 1700 MHz. (the cpu policy was
set to 'dynamic', so compilation had been carried out at 800 MHz).
Is that normal for you?

After updating, just one day layer, 'svn update', then running 'make', it
took again more than 12 hours, as everything had been recompiòed.
I would have expected much shorter time.    

Any way to improve my procedure?

Thank you
--
Pol


</description>
    <dc:creator>Pol</dc:creator>
    <dc:date>2008-07-22T06:01:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109293">
    <title>image dialog question</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109293</link>
    <description>What is the image dialog option "Don't unzip on export" for?

thanks in advance
Uwe

</description>
    <dc:creator>Uwe Stöhr</dc:creator>
    <dc:date>2008-07-21T23:16:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109292">
    <title>congratulations for the Doxy finish</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109292</link>
    <description>Hello Pavel,

I just want to say that you've done a great job in stepping through all our LFuns cleaning them up 
and describing!

Many thanks for this and best regards
Uwe

</description>
    <dc:creator>Uwe Stöhr</dc:creator>
    <dc:date>2008-07-21T21:20:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109258">
    <title>ToC and editing speed</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109258</link>
    <description>hi,
i have opened Extended manual and ToC. moving with cursor is painfully 
slow. anybody can confirm?

pavel

</description>
    <dc:creator>Pavel Sanda</dc:creator>
    <dc:date>2008-07-21T12:07:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109253">
    <title>changeset 25759</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109253</link>
    <description>This is incorrect:

if sys.argv[1][:4] == 'pdf:' and major &gt;= 6 and minor &gt;= 2 and patch &gt;= 6:

So when I would have version 7.0.3 that has the new features, I could not use this as minor is not 
 &gt;= 2 and patch also not &gt;= 6

So the best would be to extract the numbers and form a real number out of them. So 6.2.6 gets 626 
and we check if the version is &gt;= 626

regards Uwe

</description>
    <dc:creator>Uwe Stöhr</dc:creator>
    <dc:date>2008-07-21T09:44:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109248">
    <title>compilation problem with trunk</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109248</link>
    <description>I nowadays get this compiler message:

D:\LyXSVN\lyx-devel\src\graphics\PreviewLoader.cpp(264) : warning C4355: 'this'
: used in base member initializer list
lib /nologo /OUT:release\libs\graphics.lib release\src\graphics\GraphicsCache.ob
j release\src\graphics\GraphicsCacheItem.obj release\src\graphics\GraphicsConver
ter.obj release\src\graphics\GraphicsImage.obj release\src\graphics\GraphicsLoad
er.obj release\src\graphics\GraphicsParams.obj release\src\graphics\GraphicsType
s.obj release\src\graphics\PreviewImage.obj release\src\graphics\PreviewLoader.o
bj release\src\graphics\Previews.obj
GraphicsTypes.obj : warning LNK4221: no public symbols found; archive member wil
l be inaccessible

I think the first warning can be ignored, but what is the second one?

regards Uwe

</description>
    <dc:creator>Uwe Stöhr</dc:creator>
    <dc:date>2008-07-20T23:17:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109233">
    <title>aussie is dead!</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109233</link>
    <description>I cannot even ssh into it...

abdel&lt; at &gt;PAVILION /c/devel/qt/4.4/bin
$ ssh aussie.lyx.org
ssh: connect to host aussie.lyx.org port 22: Bad file number

abdel&lt; at &gt;PAVILION /c/devel/qt/4.4/bin
$ ping aussie.lyx.org

Envoi d'une requête 'ping' sur aussie.lyx.org [62.70.27.115] avec 32 
octets de données :

Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.
Délai d'attente de la demande dépassé.

Statistiques Ping pour 62.70.27.115:
     Paquets : envoyés = 4, reçus = 0, perdus = 4 (perte 100%),

Abdel.


</description>
    <dc:creator>Abdelrazak Younes</dc:creator>
    <dc:date>2008-07-20T08:29:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109231">
    <title>cross reference no longer view by document in 1.6.0beta4</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109231</link>
    <description>I remember the insert cross reference window used to have a pull-down menus
to select which document reference I'd like to view.  In 1.6.0beta4, the
functionality seems gone, ending up a one big chuck of references of all the
child documents (if I'm not wrong).  Is there any option to sort them out by
document rather than having a long long list of hundreds of references when
handling bigger document set?

Or having an entry in the pull-down menus to show all references in all
child documents.... best of both worlds??
</description>
    <dc:creator>Abe Lau</dc:creator>
    <dc:date>2008-07-20T02:07:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109227">
    <title>bug due to r25666</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109227</link>
    <description>Hi!

By bisecting, I've determined the following bug is due to r25666 
(http://www.lyx.org/trac/changeset/25666).

This is the bug: the attached LyX file (r25666-bug.lyx), when opened in r25665, 
correctly produces the dvi output correct.dvi; when opened in r25666, however, 
the output is incorrect.dvi.

The thing is this: the file can initially be created also in r25666, and then it 
displays correctly. If you then save it, the saved file is identical to that 
created in r25665. But when you load it, the layout is no longer preserved 
inside the cell; and there is no option to change the layout: the layout box is 
now grayed out, and trying to set itemize with 'Alt-p i' produces the message 
'Command disabled' in the status bar.

Thanks!
Dov
</description>
    <dc:creator>Dov Feldstern</dc:creator>
    <dc:date>2008-07-19T21:55:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109224">
    <title>Dialog Update</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109224</link>
    <description>
Suppose the Citation dialog is open, and you open the BibTeX inset and 
change the bibfiles. The dialog should presumably update itself with the 
changes. How can I make this happen? I.e., how can I send a message to 
the dialog from Buffer::updateBibfilesCache() telling it to update itself?

rh


</description>
    <dc:creator>rgheck</dc:creator>
    <dc:date>2008-07-19T17:26:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.lyx.devel/109214">
    <title>[patch] proper encoding handling for listings</title>
    <link>http://comments.gmane.org/gmane.editors.lyx.devel/109214</link>
    <description>Following a recent discussion on lyx-users, I have implemented proper encoding 
handling for listings. Until now, we always embrace listings in

\begingroup
\inputencoding{latin1}
...
\endgroup

because LaTeX would bail out with an error in multibyte-encoded documents with 
listings that contains non-ASCII chars (the listings parser is not 
mulitbyte-compliant).

This brute-force switch is

a.) unnecessary for non-multibyte encodings
b.) leads to unwanted paragraph indendation (see the thread on lyx-users) due 
to the \endgroup tag
c.) produces LaTeX errors in documents that do not load inputenc
d.) produces still wrong output, since we do not switch the stream encoding, 
so "ü" comes out as "Ã1/4" in utf8-encoded documents
e.) is bad, bad, bad style

The attached patch does the right thing IMHO. It switches to latin1 _only_ if 
the listings inset is in a multibyte encoding context, and it switches it 
properly (on and off). The above errors are fixed, furthermore it also fixes 
the remainders of bug 4182.

However, encoding handling is a tricky business, so please have a look at the 
patch before I commit.

Jürgen
</description>
    <dc:creator>Jürgen Spitzmüller</dc:creator>
    <dc:date>2008-07-19T10:03:20</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.editors.lyx.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.editors.lyx.devel</link>
  </textinput>
</rdf:RDF>
