It would be great if Adobe could make the investment to restore the ability to change fonts and indenting in forum messages, while keeping spam under control (as many other companies and forums manage to do at quite low cost).  I use the forums for detailed and careful communication on technical and product issues, and I, like most of the world, find fonts, indenting, and other forms of document formating quite useful for efficient communication. Some use cases: - If I quote from a technical spec, as I often do when solving issues about image metadata, it's helpful to indent the quotation, so that readers can easily identify the quotation. - The technical specs being quoted often themselves use fonts and indenting to communicate meaning, and deleting that formatting makes it harder to read. - Small code fragments intermixed with English words are easier to read when appearing in a different font. Multi-line code fragments copied from source code often are easier to read in a fixed-pitch font, since the traditional 4-space indenting can be hard to read in variable-pitch fonts in which a space is about half the width of a wider letter.  Also, most programmers author code in fixed-pitch fonts, so presenting such code in a fixed-pitch font will preserve the relative indenting. PS: I noticed the restriction immediately after it was introduced, but I initially wrote it off as an intermittent problem that would go away eventually (as I've been trained to do by Adobe's past responses to such issues).  Only after having the formatting on a number of post "disappear" (sometimes after 30 minutes of editing) did I come here to find out why. ... View more

There’s a minor gratuitous difference between LR 3.2 on Windows and Mac in how the view:static_text control formats integers assigned the “title” property.  For example, given: f:static_text {title = 32} Windows LR displays that as “32”, whereas Mac LR displays it as “32.00”.  This also happens if the title property is getting its value indirectly via a property table. Test program illustrating the bug: local LrBinding = import 'LrBinding' local LrDialogs = import 'LrDialogs' local LrFunctionContext = import 'LrFunctionContext' local LrView = import 'LrView' local f = LrView.osFactory() LrFunctionContext.callWithContext ("test", function (context)     local prop = LrBinding.makePropertyTable (context)     prop.title1 = 32     prop.title2 = tostring (32)     LrDialogs.presentModalDialog {title = "Test", contents = f:column {         bind_to_object = prop,         f:static_text {title = 32},         f:static_text {title = LrView.bind ("title1")},         f:static_text {title = LrView.bind ("title2")}}}     end) I’ve submitted this bug. ... View more

I've released the Any File plugin for beta use by a few users: http://www.johnrellis.com/lightroom/anyfile.htm Any File lets you import any type of file into a Lightroom 3 catalog and manage it just like a photo -- PDFs, documents, spreadsheets, audio, etc. Typical uses include managing releases, invoices, notes, scans of old documents, audio tracks for slide shows, and avoiding all of the LR 3 limitations on video formats and video metadata. Feedback greatly appreciated. ... View more