Now after uploading the file (transliteration module at the stage of changing the name of the file downloads) and the preservation node, the file name is changed again based on the pattern tokens. We need to work out transliteration module after applying the template file name.

Comments

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented

@ipto

Can you upload a empty/small text file with characters that need to be transliterated so that I can run some tests?

smk-ka’s picture

smk-ka commented

@Deciphered:
ipto's problems arose from using tokens to generate file and/or path names, while transliteration during upload should indeed work. I think you can reproduce it like this (untested):
1. Set the file name pattern to "[title-raw]-[filefield_paths-name].[filefield_paths-ext]", which will construct file names from the node title plus the uploaded file name.
2. Give both the node as well as the file to upload a title containing non-ASCII characters, for example:

  • Контакт
    Cyrillic, should transliterate to Kontakt
  • special-^°!§$%&()={[]}+~'#,;.áä_.txt
    Not sure what the outcome actually looks like :o)
    Probably first diacritics removed, then only characters from a-z kept.
deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented

@smk-ka

Thanks for that, will look into a solution.

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented

Integration has been implemented and will be available in the next dev build.

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented
Status: Active » Closed (fixed)

Committed to HEAD