Page 1 of 3
UTF-8 (no BOM) format support?
Posted: Sat Apr 14, 2012 4:02 pm
by topsuccess
I'm using AkelPad to edit lua script for "LOVE2D" game engine, this engine recognize unicode string in UTF-8 (no BOM) format only, but AkelPad only saved as UTF-8 with BOM format. So my script encounted errors.
Could AkelPad support UTF-8 (no BOM) format?
Posted: Sat Apr 14, 2012 4:16 pm
by FeyFre
topsuccess, AkelPad DOES SUPPORT UTF8 W/O BOM. Search carefully, or read manuals.
Posted: Sat Apr 14, 2012 4:28 pm
by KDJ
topsuccess
Main menu -> File -> Save as -> Codepage,
or press hotkey Ctrl+Shift+S,
choose:
65001 (UTF-8)
and unselect:
BOM
Posted: Sun Apr 15, 2012 1:54 am
by topsuccess
I'm sorry, I did not notice this option.
Thank you very much, FeyFre and KDJ.
Posted: Tue Apr 24, 2012 9:43 pm
by ZoNi
What should I do? In Notepad text is ok, in AkelPad very often it is not - like here:

Posted: Tue Apr 24, 2012 10:52 pm
by FeyFre
ZoNi, try to Redetect codepage or set manually. Press F12 while in Akelpad - in poped menu click "Redetect" for automatic redetection. Or on the same menu select submenu "Open As" and select desired(guessed) codepage.
If no other codepage conforms you - that means you really have such content in text file and automatic detection was successful.
If you have managed to find right codepage and such problem persists for other files, then you probably forgot to configure autodetection: goto Options - Settings - Genetal tab - Codepage recognition. You also can play with codepage filter.
Posted: Wed Apr 25, 2012 4:52 pm
by ZoNi
FeyFre wrote:ZoNi, try to Redetect codepage or set manually. Press 12 while in Akelpad - in poped menu click "Redetect" for automatic redetection.
This helped! Thank you... Just for others, that may help about this: 12 = F12

Posted: Sun May 21, 2023 7:57 pm
by Diamen
KDJ wrote:topsuccess
Main menu -> File -> Save as -> Codepage,
or press hotkey Ctrl+Shift+S,
choose:
65001 (UTF-8)
and unselect:
BOM
When I exit after save and reload file in AkelPad, file return to Ansi instead of remain UTF.
Do it is possible to avoid and mantain it UTF without BOM.
In need it for PHP.
Re: UTF-8 (no BOM) format support?
Posted: Mon Jan 20, 2025 7:13 am
by Diamen
Do it is possibile to save to UTF-8 (without BOM) from status bar contextual menu or set it as default?
Re: UTF-8 (no BOM) format support?
Posted: Mon Jan 20, 2025 10:28 am
by ewild
Diamen
There's a switch to turn on/off BOM/No BOM saving mode.
You can make a button/menu entry of it:
Code: Select all
"No BOM" +Call("SaveFile::SaveNoBOM")
Re: UTF-8 (no BOM) format support?
Posted: Mon Jan 20, 2025 11:50 am
by Diamen
Call work but when I reload the file saved in UTF-8 no BOM Akelpad not recognize it and load as Ansi.
Re: UTF-8 (no BOM) format support?
Posted: Tue Jan 21, 2025 5:24 am
by Diamen
Codepage recognize not work when have few characters in a file.
f.e.:
this is utf-8 ò.
Not problem with notepad.exe with same file.
Re: UTF-8 (no BOM) format support?
Posted: Tue Jan 21, 2025 2:26 pm
by DV
Diamen, did you try to experiment with the codepage settings in the Options -> Settings -> General ?
Such as:
- set "Codepage recognition" to "Western European"
- set "Default codepage" to "65001"
- set "New file" to "65001" without BOM.
Re: UTF-8 (no BOM) format support?
Posted: Tue Jan 21, 2025 3:36 pm
by Diamen
When I use your setting with:
test òà.
I save it as 1251 Ansi
when I reopen Akelpad recognize as UTF- NO BOM and not display accented and point.
Display onlye
"test "
Re: UTF-8 (no BOM) format support?
Posted: Wed Jan 22, 2025 6:30 pm
by DV
Looks like there is some misunderstanding.
The topic says "UTF-8", so I proposed to specify the codepage "65001" that corresponds to "UTF-8".
The "UTF-8" encoding/codepage by its nature uses multiple bytes per each non-Latin character such as "òà" you mentioned.
But then you write "I save it as 1251 Ansi". The "1251" is an Ansi encoding/codepage that uses single byte per each character, including non-Latin characters. Which means each non-Latin character such as "ò" and "à" is truncated to a single byte, and this single byte can not be properly interpreted as a non-Latin character unless your system's Ansi encoding contains these characters. To be sure these "ò" and "à" characters are properly saved and then properly displayed on any system, you should save your file as "UTF-8".