-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Page Marker Flags #316
Comments
If page marker support is modified, please consider also supporting exchange of page LABEL flags, and using different prefixes, e.g., [Pg 123] for markers and [Pl 123] for labels (the latter is Papa Lima, not Papa One). |
Either that, or to reduce the number of additions, we could add the page label after a suitable separator, e.g. |
That would be fine. |
Bearing in mind the resistance to change because "That's the way it's done in GG1 and we don't want to upset the current users!", if |
I had the same thought, and didn't post it earlier, but since Sharon said it already... No-count seems like it's better to omit the Pg part? Just |
This issue may have been initiated as a result of a private message I sent to Nigel. I think we need a way to allow someone using GG2 to easily switch back to GG1 if an insurmountable problem is encountered. Preserving the page breaks, page labels, and possibly some other Information would make falling back much easier. Once the problem has been circumvented by using GG1, the user could switch back to GG2 if desired. This is only likely to be an issue in the early days following the release of GG2. |
Fixed by #330 |
At the moment, if you're switching between GG1 & GG2 or vice versa, the Page Marker Flags only cause updating of page break locations, not creation of page break locations. If they also created them, it would further improve the transfer process, because you could delete them in your secondary editor while you do the work there:
then optionally:
The text was updated successfully, but these errors were encountered: