FindGettext: two more fixes for files with multiple dots
Another patch by Albert Astals Cid for dealing with translation files with multiple dots. Alex
This commit is contained in:
parent
e48fcfffa3
commit
65dde30ddd
|
@ -52,7 +52,8 @@ MACRO(GETTEXT_CREATE_TRANSLATIONS _potFile _firstPoFileArg)
|
||||||
SET(_firstPoFile "${_firstPoFileArg}")
|
SET(_firstPoFile "${_firstPoFileArg}")
|
||||||
|
|
||||||
SET(_gmoFiles)
|
SET(_gmoFiles)
|
||||||
GET_FILENAME_COMPONENT(_potBasename ${_potFile} NAME_WE)
|
GET_FILENAME_COMPONENT(_potName ${_potFile} NAME)
|
||||||
|
STRING(REGEX REPLACE "^(.+)(\\.[^.]+)$" "\\1" _potBasename ${_potName})
|
||||||
GET_FILENAME_COMPONENT(_absPotFile ${_potFile} ABSOLUTE)
|
GET_FILENAME_COMPONENT(_absPotFile ${_potFile} ABSOLUTE)
|
||||||
|
|
||||||
SET(_addToAll)
|
SET(_addToAll)
|
||||||
|
@ -92,7 +93,8 @@ FUNCTION(GETTEXT_PROCESS_POT_FILE _potFile)
|
||||||
|
|
||||||
CMAKE_PARSE_ARGUMENTS(_parsedArguments "${_options}" "${_oneValueArgs}" "${_multiValueArgs}" ${ARGN})
|
CMAKE_PARSE_ARGUMENTS(_parsedArguments "${_options}" "${_oneValueArgs}" "${_multiValueArgs}" ${ARGN})
|
||||||
|
|
||||||
GET_FILENAME_COMPONENT(_potBasename ${_potFile} NAME_WE)
|
GET_FILENAME_COMPONENT(_potName ${_potFile} NAME)
|
||||||
|
STRING(REGEX REPLACE "^(.+)(\\.[^.]+)$" "\\1" _potBasename ${_potName})
|
||||||
GET_FILENAME_COMPONENT(_absPotFile ${_potFile} ABSOLUTE)
|
GET_FILENAME_COMPONENT(_absPotFile ${_potFile} ABSOLUTE)
|
||||||
|
|
||||||
FOREACH (_lang ${_parsedArguments_LANGUAGES})
|
FOREACH (_lang ${_parsedArguments_LANGUAGES})
|
||||||
|
|
Loading…
Reference in New Issue