Talk:Formatting Objects Processor
It is of interest to the following WikiProjects:
|auto= parameter.
|auto= parameter.Fair use rationale for Image:Apache fop.jpg
[edit ]
Image:Apache fop.jpg is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in Wikipedia articles constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale.
If there is other other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.BetacommandBot 19:58, 31 May 2007 (UTC) [reply ]
Article name
[edit ]Why is the article name so awkward looking Apache FOP (Formatting Objects Processor) when it should simply be Apache FOP and have the full name of the acronym within the article itself? Jimj wpg (talk) 03:11, 20 July 2020 (UTC) [reply ]
- Note that I didn't name it FOP with that acronym or initialism in mind. It's like ISO. It's a reference to the English word "fop" but contains the "FO" of formatting objects. When I started FOP I think I thought of it more as FO to PDF. I don't think I ever thought of the P as meaning processor. So it's a backronym. Jktauber (talk) 20:33, 5 May 2023 (UTC) [reply ]
Move discussion in progress
[edit ]There is a move discussion in progress on Talk:AEC (Alashki Engineering Constructions) which affects this page. Please participate on that page and not in this talk page section. Thank you. —RMCD bot 23:18, 27 December 2022 (UTC) [reply ]