our intangible assets are amortized over their estimated useful lives of 1 to 13 years as shown in the table below . amortization is based on the pattern in which the economic benefits of the intangible asset will be consumed . weighted average useful life ( years ) .

========================================
Row 1: , weighted average useful life ( years )
Row 2: purchased technology, 4
Row 3: localization, 1
Row 4: trademarks, 5
Row 5: customer contracts and relationships, 6
Row 6: other intangibles, 3
========================================

software development costs capitalization of software development costs for software to be sold , leased , or otherwise marketed begins upon the establishment of technological feasibility , which is generally the completion of a working prototype that has been certified as having no critical bugs and is a release candidate . amortization begins once the software is ready for its intended use , generally based on the pattern in which the economic benefits will be consumed . to date , software development costs incurred between completion of a working prototype and general availability of the related product have not been material . revenue recognition our revenue is derived from the licensing of software products , consulting and maintenance and support . primarily , we recognize revenue pursuant to the requirements of aicpa statement of position 97-2 , 201csoftware revenue recognition 201d and any applicable amendments , when persuasive evidence of an arrangement exists , we have delivered the product or performed the service , the fee is fixed or determinable and collection is probable . multiple element arrangements we enter into multiple element revenue arrangements in which a customer may purchase a combination of software , upgrades , maintenance and support , and consulting ( multiple-element arrangements ) . when vsoe of fair value does not exist for all delivered elements , we allocate and defer revenue for the undelivered items based on vsoe of fair value of the undelivered elements and recognize the difference between the total arrangement fee and the amount deferred for the undelivered items as license revenue . vsoe of fair value for each element is based on the price for which the element is sold separately . we determine the vsoe of fair value of each element based on historical evidence of our stand-alone sales of these elements to third parties or from the stated renewal rate for the elements contained in the initial software license arrangement . when vsoe of fair value does not exist for any undelivered element , revenue is deferred until the earlier of the point at which such vsoe of fair value exists or until all elements of the arrangement have been delivered . the only exception to this guidance is when the only undelivered element is maintenance and support or other services , then the entire arrangement fee is recognized ratably over the performance period . product revenue we recognize our product revenue upon shipment , provided all other revenue recognition criteria have been met . our desktop application products 2019 revenue from distributors is subject to agreements allowing limited rights of return , rebates and price protection . our direct sales and oem sales are also subject to limited rights of return . accordingly , we reduce revenue recognized for estimated future returns , price protection and rebates at the time the related revenue is recorded . the estimates for returns are adjusted periodically based upon historical rates of returns , inventory levels in the distribution channel and other related factors . we record the estimated costs of providing free technical phone support to customers for our software products . we recognize oem licensing revenue , primarily royalties , when oem partners ship products incorporating our software , provided collection of such revenue is deemed probable . for certain oem customers , we must estimate royalty .

Question: is the weighted average useful life ( years ) for trademarks greater than customer contracts and relationships?
Program: greater(5, 6)
Answer: no