xh « source - lo/translations - LibreOffice 界面翻译代码仓库

Mode	Name	Size
d---------	accessibility	39	log plain
d---------	avmedia	39	log plain
d---------	basctl	39	log plain
d---------	basic	39	log plain
d---------	chart2	39	log plain
d---------	connectivity	74	log plain
d---------	cui	39	log plain
d---------	dbaccess	39	log plain
d---------	desktop	39	log plain
d---------	dictionaries	1998	log plain
d---------	editeng	39	log plain
d---------	extensions	72	log plain
d---------	extras / source	33	log plain
d---------	filter	72	log plain
d---------	forms	39	log plain
d---------	formula	39	log plain
d---------	fpicker	39	log plain
d---------	framework	39	log plain
d---------	instsetoo_native / inc_openoffice / windows	41	log plain
d---------	librelogo / source	33	log plain
d---------	mysqlc	70	log plain
d---------	nlpsolver	61	log plain
d---------	officecfg / registry / data / org	35	log plain
d---------	readlicense_oo	35	log plain
d---------	reportbuilder / java / org / libreoffice / report / function	31	log plain
d---------	reportdesign	39	log plain
d---------	sc	39	log plain
d---------	scaddins	39	log plain
d---------	sccomp	39	log plain
d---------	scp2 / source	33	log plain
d---------	sd	39	log plain
d---------	setup_native / source	33	log plain
d---------	sfx2	39	log plain
d---------	shell / source / win32 / shlxthandler	33	log plain
d---------	starmath	39	log plain
d---------	svl	39	log plain
d---------	svtools	39	log plain
d---------	svx	39	log plain
d---------	sw	39	log plain
d---------	swext / mediawiki	36	log plain
d---------	sysui / desktop	34	log plain
d---------	uui	39	log plain
d---------	vcl	39	log plain
d---------	wizards	72	log plain
d---------	writerperfect	39	log plain
d---------	xmlsecurity	39	log plain

Age	Commit message (Collapse)	Author
2023-08-08	wina11y: Drop AccObjectManagerAgent indirection	Michael Weghorn
	`AccObjectManagerAgent` was holding an `AccObjectWinManager` object and forwarding everything to that one and the event listeners were holding a pointer to the `AccObjectManagerAgent` object. Drop this `AccObjectManagerAgent` indirection and let all of the classes that were interacting with the `AccObjectManagerAgent` directly interact with the `AccObjectWinManager` instead. The idea of having the agent seems to have been to have an abstraction layer and implement different accessible object managers for all platforms, but the agent already has quite some Windows-/IAccessible-specific code/interface and by now, the Linux VCL plugins and macOS have their own a11y bridges, so the TODO do implement this here for Linux as well seems outdated to me. Even if implementing this for Linux and/or macOS in a similar way, I don't see the need for the agent layer, but one way might be to just have an abstract base class (e.g. `AccObjectManager`) that `AccObjectWinManager` and implementations for other platforms derive from, and have the SalInstance return the platform-specific implementation that the `AccTopWindowListener` would then retrieve and pass on. Given that `AccObjectManagerAgent` was forwarding all calls to `AccObjectWinManager` and the methods and params are mostly the same by now (s.a. the preparatory commits), this change is mostly straightforward. A few notes: * `AccObjectManagerAgent::InsertAccObj` had a default nullptr value for the HWND that `AccObjectWinManager:InsertAccObj` didn't have yet, so add that. * `AccObjectManagerAgent::GetIAccessibleFromResID` had an out param instead of a return value; call sites were adapted to fit `AccObjectWinManager:GetIAccessibleFromResID`. * The `UpdateValue` and `UpdateAccName` methods taking 2 params are called `SetValue` and `SetAccName` in `AccObjectWinManager` instead, so adapt call sites accordingly. * prewin.h and postwin.h includes had to be added around the windows.h include in AccObjectWinManager.hxx (build would otherwise fail) * A few `AccObjectWinManager` methods had to be made virtual to make linking work. Change-Id: I88741bf416d4db25d78e973c0db060a828f27926 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155440 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-12-10	Generally determine Rdb content from gb_*_set_componentfile calls	Stephan Bergmann
	...instead of by listing the content somewhat redundantly in the Rdb_.mk files, to avoid duplication of logic for components that are only built conditionally (and thus should only be included conditionally in the corresponding Rdb). To achieve that, add an "rdb" parameter to gb_ComponentTarget_ComponentTarget (and to the gb__set_componentfile macros that internally call gb_ComponentTarget_ComponentTarget), which is used to make the appropriate gb_Rdb_add_component call internally from within gb_ComponentTarget_ComponentTarget. (As a special case, gb_CppunitTest_set_componentfile shall not call gb_Rdb_add_component, as that has already been done by the corresponding gb_Library_set_componentfile call, so allow the gb_ComponentTarget_ComponentTarget "rdb" parameter to be empty to support that special case.) Most Rdb_*.mk files are thus mostly empty now. One exception is i18npool/Rdb_saxparser.mk, which duplicates some of the Rdb_services content as needed during the build in CustomTarget_i18npool/localedata. 1c9a40299d328c78c035ca63ccdf22c5c669a03b "gbuild: create services.rdb from built components" had already tried to do something similar (in addition to other things) under a new --enable-services-rdb-from-build option. However, that approach had four drawbacks that this approach here addresses (and which thus partly reverts 1c9a40299d328c78c035ca63ccdf22c5c669a03b): 1 Rdb_services shall not contain the component files of all libraries that are built. While that commit filtered out the component files that go into Rdb_ure/services (ure/Rdb_ure.mk), it failed to filter out the component files that go into others like Rdb_postgresql-sdbc (connectivity/Rdb_postgresql-sdbc.mk). 2 The code added by that commit to Makefile.gbuild codified the knowledge that there is an Rdb_services, which is brittle. 3 The code added by that commit to solenv/gbuild/Rdb.mk codified the knowledge (for gb_Rdb__URECOMPONENTS) that there is an Rdb_ure/services, which is brittle. 4 Introducing an --enable-services-rdb-from-build option needlessly provided two different ways how the content of Rdb_services is assembled. The changes done here would leave --enable-services-rdb-from-build as a misnomer, as it no longer controls how Rdb_services is assembled. I thus renamed it to --enable-customtarget-components, as that is apparently what it still does now. Change-Id: Ia5e8df4b640146c77421fcec6daa11a9cd260265 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126577 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>