sd/source/core/ThemeColorChanger.cxx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 89e2f268771ecb07948d3e67d220e28b2ae82e20
Author: Andrea Gelmini <andrea.gelm...@gelma.net>
AuthorDate: Fri Sep 1 18:18:41 2023 +0200
Commit: Julien Nabet <serval2...@yahoo.fr>
CommitDate: Fri Sep 1 18:41:02 2023 +0200
Fix typo
Change-Id: If259a049d38f82210819a5adbf458eae1651cfaf
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156429
Tested-by: Julien Nabet <serval2...@yahoo.fr>
Reviewed-by: Julien Nabet <serval2...@yahoo.fr>
diff --git a/sd/source/core/ThemeColorChanger.cxx
b/sd/source/core/ThemeColorChanger.cxx
index 3a5c7804ae57..d187ee36c0a1 100644
--- a/sd/source/core/ThemeColorChanger.cxx
+++ b/sd/source/core/ThemeColorChanger.cxx
@@ -157,7 +157,7 @@ void
ThemeColorChanger::apply(std::shared_ptr<model::ColorSet> const& pColorSet)
// TODO - for now change all the objects regardless to which master
page it belongs to.
// Currently we don't have a concept of master slide with a group of
layouts as in MSO, but we always only
// have master pages, which aren't grouped together. In MSO the theme
is defined per master slide, so when
- // changing a theme, all the layouts get the new theme, as layouts are
synonomus to master pages in LibreOffise,
+ // changing a theme, all the layouts get the new theme, as layouts are
synonomus to master pages in LibreOffice,
// this is not possible to do and we would need to change the theme
for each master page separately, which
// is just annoying for the user.
