Treat quote as value if already in quote using another delimiter

[silvadiego]

Fixes the issue as described in #222.

[glensc]

@silvadiego is this same problem? can you cherry-pick testcase from there?

• Add test for #147 regression #224

[glensc]

2019 perhaps?

[silvadiego]

@silvadiego is this same problem? can you cherry-pick testcase from there?

• Add test for #147 regression #224

Yes, i will do that when i get home.

[glensc]

not sure, should #224 be added to changelog too? but at least include #222 in changelog!

[glensc]

@weierophinney can we get this merged?

as noted in #224, this is regression from changes from #147 resolution i.e from your 8aac5f7 commit

[glensc]

@Xerkus ping?

[glensc]

@silvadiego I don't know what's this project merge policy (hardly anybody accepts changes here), but good practice is to squash useless commits to one commit and git push -f (three commits altering changelogs could be squashed)

[weierophinney]

This repository has been closed and moved to laminas/laminas-mail; a new issue has been opened at laminas/laminas-mail#18.

[weierophinney]

This repository has been moved to laminas/laminas-mail. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

• Squash all commits in your branch (git rebase -i origin/{branch})
• Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
• Run the laminas/laminas-migration tool on the code.
• Clone laminas/laminas-mail to another directory.
• Copy the files from the second bullet point to the clone of laminas/laminas-mail.
• In your clone of laminas/laminas-mail, commit the files, push to your fork, and open the new PR.
  We will be providing tooling via laminas/laminas-migration soon to help automate the process.