Activity for Stéphane Aulery
-
Stéphane Aulery created a blog post
WIKINDX v6.11.0 Release Candidate 2
-
Add missing files in SVN
-
Release 6.11.0-rc2 (SVN History)
-
Release 6.11.0-rc2 (SVN)
-
Fix the date of files in release tarballs to the date of the release
-
Change the date of file to release date when packaged
-
Remove an extra space in folder name
-
Merge revision 5508 in stable
-
Release 6.11.0-rc1 (CUS)
-
WIKINDX v6.11.0 Release Candidate 1
-
Fix the detection on Unices of the PHP cli calling a PHP release script
-
Release 6.11.0-rc1 (SVN History)
-
Release 6.11.0-rc1 (SVN)
-
Fix calls to touch() in release script
-
Fix the detection of private hugo binaries
-
Release 6.11.0-rc1 (SVN History)
-
Release 6.11.0-rc1 (SVN)
-
Release 6.11.0-rc1 (SVN History)
-
Release 6.11.0-rc1 (SVN)
-
Merge code from revision 5460 with stable branch (prepare 6.11.0-rc1)
-
Update my release keys config
-
Update my release keys config
-
Merge code from revision 5460 with stable branch (prepare 6.11.0-rc1)
-
Sign components (prepare 6.11.0-rc1)
-
Merge code from revision 5460 with stable branch (prepare 6.11.0-rc1)
-
Prepare the website for 6.11.0 release
-
Update components for 6.11.0 release
-
DOCX Export : fix [Content_Types].xml inside the OCF container
-
DOCX Export : fix file writing in Zip archive
-
I guess the relevant section is this: "If double-quotes are used to enclose fields, then a double-quote appearing inside a field must be escaped by preceding it with another double quote." Yes. Please note, with a customizable quotation character, this is the character that must be repeated. I wonder if other software also uses a similar rule (only escape a double quote when the next character makes the double quote ambiguous). I don't know of any software that follows the rule you describe. CSV...
-
Improved record search
-
Using File > Clean > Project with structure editor can puzzle BeeBase
-
Cosmetic: add a space between field name and field type
-
Yes, the status bar is one way to display notifications. The title bar is reserved to application and document title.
-
How strong do you feel about this? Would it be better if clicking "Text" only creates the default text object and the user has to double click it for changing its contents? Much better. It would be more in line with what the editor actually does.
-
The gettext translation is not loaded according to the user env
-
Probably. I cannot find Preferences > User settings, but my current locale setting is followed.
-
Query export is not well escaped according to RFC4180
-
The change introduced to capitalize is working properly.
-
Queries are case sensitive
-
I could not find them anymore.
-
Queries are case sensitive
-
The 'syntax error' string is not always translated
-
Fix tested, OK.
-
Closing form the structure editor raise a loop of GUI compilation erreors
-
Fix tested, OK.
-
Query export should not count the header with records
-
Fix tested, OK.
-
The print preview cannot be resized in full screen
-
Fix tested, ok.
-
DOCX Export : protect the ZipArchive reference if the code is moved inside a namesapce
-
DOCX Export : force UTF-8 file path
-
DOCX Export : Office Open XML file format reference (ECMA-376, 5th ed.)
-
DOCX Export : set the date of files inside OCF container + comments
-
CX Export : create a fixed layout of folder in OCF container
-
DOCX Export : Inside a Zip file, the directory separator is always "/" (Windows requirement)
-
This might have been valid if the program was reset with an empty project after closing as one is initially opened.
-
I would be fine but maybe complicated for a small profit?
-
7 images in attachments show the loop.
-
Open BeeBase Menu File > Open project > annuaire.bee Menu File > Edit structure Menu File > Close Menu File > Quit
-
How to write a query with = operator?
-
Ok, double quotes is the right syntax.
-
Update Ukranian translation of readme file
-
Open BeeBase Menu File > Open project > annuaire.bee Menu File > Edit structure Menu File > Close Menu File > Edit structure
-
I created a project annuaire.bee, save and quit. After that I give the steps to reproduce when I open this project. Step 5 is File > Close.
-
I'll test again tonight then.
-
The print preview cannot be resized in full screen
-
Query export should not count the header with records
-
Query export counts the header with records
-
The 'syntax error' string is not always translated
-
How to write a query with = operator?
-
The 'syntax error' string is not always translated
-
The 'syntax error' string is not always translated
-
How to write a query with = operator?
-
Fix a typo in French manual
-
Fix a type in French manual
-
Fix a typo in French manual
-
Better French translation of "Advance on <Enter>?"
-
Closing form the structure editor raise a loop of GUI compilation erreors
-
Update French messages
-
Support Unicode 16.0
-
Support Unicode 16.0
-
update French translation of readme_fr [r4398]
-
Update French translation of acknowledgments.texi [r4393]
-
French translation of [r4391]
-
Forbid direct access to config.php file
-
Allow the admin to enable the Strict-Transport-Security Policy
-
Add a CORS Policy
-
Prevent session fixation and hijacking with httponly and only_cookies machanisms
-
Prevent session fixation and hijacking with httponly and only_cookies machanisms
-
Improve changelog
-
Fix browserTabID parameter passing to TinyMCE plugins during TinyMCE controls code generation.
-
Update messages catalogs
-
Update phpDocumentor (v3.5.2)
-
Update phpDocumentor (v3.5.1)
-
Refines the checkDevice() function and adds a warning about the reliability of the User-Agent header
-
Update Smarty (v5.3.1)
-
Merge trunk in stable
-
CSS menus for mobile devices
1 >