Using Print Ranges on a Spreadsheet /text/scalc/guide/printranges.xhp exporting;cells printing; cells ranges;print ranges PDF export of print ranges cell ranges; printing cells; print ranges print ranges clearing, see also deleting/removing defining;print ranges extending print ranges deleting;print ranges mw deleted "adding;" and corrected two typos in "defining;" and "extending.." MW changed "clearing," Defining Print Ranges on a Sheet You can define which range of cells on a spreadsheet to print. The cells on the sheet that are not part of the defined print range are not printed or exported. Sheets without a defined print range are not printed and not exported to a PDF file, unless the document uses the Excel file format. For files opened in Excel format, all sheets that do not contain a defined print range are printed. The same behavior occurs when you export the Excel formatted spreadsheet to a PDF file.UFI: New, see spec "Calc Print Settings Sheet Property "Print Entire Sheet"" To Define a Print Range Select the cells that you want to print. Choose Format - Print Ranges - Define. To Add Cells to a Print Range Select the cells that you want to add to the existing print range. Choose Format - Print Ranges - Add. To Clear a Print Range Choose Format - Print Ranges - Clear. Using the Page Break Preview to Edit Print Ranges In the Page Break Preview, print ranges as well as page break regions are outlined by a blue border and contain a centered page number in gray. Nonprinting areas have a gray background. To define a new page break region, drag the border to a new location. When you define a new page break region, an automatic page break is replaced by a manual page break. To View and Edit Print Ranges Choose View - Page Break Preview. To change the default zoom factor of the Page Break Preview, double click the percentage value on the Status bar, and select a new zoom factor. Edit the print range. To change the size of a print range, drag a border of the range to a new location. To delete a manual page break that is contained in a print range, drag the border of the page break outside of the print range. To clear a print range, drag a border of the range onto the opposite border of the range. To exit the Page Break Preview, choose View - Normal.
Editing Print Ranges
ports LibreOffice 核心代码仓库文档基金会
summaryrefslogtreecommitdiff
path: root/sc/uiconfig/scalc/ui/optsortlists.ui
AgeCommit message (Collapse)Author
2018-11-19weld TreeViewCaolán McNamara
a) use GtkTreeStores for GtkTreeViews b) ironically can't store GtkTreeStore contents in .ui apparently c) set show_expanders for all non-trees and unconverted cases d) on-demand subtrees Change-Id: I3c1036a222daba2c129b1a22ffeb3fe35005ae31 Reviewed-on: https://gerrit.libreoffice.org/63336 Tested-by: Jenkins Reviewed-by: Caolán McNamara <caolanm@redhat.com> Tested-by: Caolán McNamara <caolanm@redhat.com>
2018-04-02drop the spurious invisible_char[_set] propertiesCaolán McNamara
Change-Id: I8264a4f6035fd19c7a892902c41127615eaf6dd3 Reviewed-on: https://gerrit.libreoffice.org/52265 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Caolán McNamara <caolanm@redhat.com> Tested-by: Caolán McNamara <caolanm@redhat.com>
2018-03-05Resolves: tdf#116188 set min version on all .ui files to 3.18Caolán McNamara
which is already the min for the runtime Change-Id: Ifebe099f1f94a36f65a31989689400327a823dcd Reviewed-on: https://gerrit.libreoffice.org/50776 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Caolán McNamara <caolanm@redhat.com> Tested-by: Caolán McNamara <caolanm@redhat.com>
2017-07-21migrate to boost::gettextCaolán McNamara
* all .ui files go from <interface> to <interface domain="MODULE"> e.g. vcl * all .src files go away and the english source strings folded into the .hrc as NC_("context", "source string") * ResMgr is dropped in favour of std::locale imbued by boost::locale::generator pointed at matching MODULE .mo files * UIConfig translations are folded into the module .mo, so e.g. UIConfig_cui goes from l10n target to normal one, so the res/lang.zips of UI files go away * translation via Translation::get(hrc-define-key, imbued-std::locale) * python can now be translated with its inbuilt gettext support (we keep the name strings.hrc there to keep finding the .hrc file uniform) so magic numbers can go away there * java and starbasic components can be translated via the pre-existing css.resource.StringResourceWithLocation mechanism * en-US res files go away, their strings are now the .hrc keys in the source code * remaining .res files are replaced by .mo files * in .res/.ui-lang-zip files, the old scheme missing translations of strings results in inserting the english original so something can be found, now the standard fallback of using the english original from the source key is used, so partial translations shrink dramatically in size * extract .hrc strings with hrcex which backs onto xgettext -C --add-comments --keyword=NC_:1c,2 --from-code=UTF-8 --no-wrap * extract .ui strings with uiex which backs onto xgettext --add-comments --no-wrap * qtz for gettext translations is generated at runtime as ascii-ified crc32 of content + "|" + msgid * [API CHANGE] remove deprecated binary .res resouce loader related uno apis com::sun::star::resource::OfficeResourceLoader com::sun::star::resource::XResourceBundleLoader com::sun::star::resource::XResourceBundle when translating strings via uno apis com.sun.star.resource.StringResourceWithLocation can continue to be used Change-Id: Ia2594a2672b7301d9c3421fdf31b6cfe7f3f8d0a
2014-09-02make sort list options page fill vertically and horizontallyCaolán McNamara
Change-Id: I495ab15fa9b658e54f039aede69a7a79b6296635